Skip to main content

Webhook Request Body Tab

JSON and XML schema configuration in the Webhook Request Body Tab

Chris Arenas avatar
Written by Chris Arenas
Updated over 2 weeks ago

Overview

The request body configuration is used for XML and JSON deliveries in webhook-based methods. This is where you input the schema defined in the client’s posting documentation. The system lets you substitute lead field values in the schema via dropdowns that insert delivery method tags, which auto-populate values when the lead is delivered.

If you're using an HTTP POST delivery with URL-encoded content type, this step can be skipped.

Key Functionality

  • Accepts XML or JSON schemas for defining the structure of lead payloads.

  • Provides a dropdown interface to insert delivery method tags (i.e. placeholders) that correspond to your lead fields.

  • Ensures that during delivery, the tags are replaced with the actual values from lead records.

  • Skippable when using URL-encoded content type for HTTP POST deliveries.

How to Use This Feature

  1. Navigate to the Request Body or Request tab within your webhook delivery method settings.

  2. Paste or type in the XML or JSON schema provided by your client.

  3. Within the schema, use the dropdown menus to replace schema placeholders with delivery method tags corresponding to your lead fields.

  4. The dropdown-selected tags will be converted into actual lead field values at runtime.

  5. If your delivery uses URL-encoded content type (instead of JSON/XML), you can skip using a schema in this tab.

  6. Save the configuration once complete.

Best Practices

  • Always refer to the client’s posting documentation to build the correct schema.

  • Use dropdown tag insertion rather than manual typing to reduce typos.

  • Keep schema structure clear and minimal; avoid unnecessary fields.

  • Test the request in a sandbox environment using sample lead data to validate correct mapping.

  • When skipping this step (URL-encoded), ensure the delivery method settings elsewhere (e.g. key-value mappings) are configured properly.

Troubleshooting

  • Payload rejected by endpoint
    → Confirm schema matches expected structure; check for missing or extra brackets, tags, or syntax errors.

  • Tags not replaced
    → Verify the tag names exactly correspond to your lead fields and that you’ve used the dropdown insertion.

  • Delivery fails when using XML/JSON
    → Try switching to URL-encoded or confirm content type settings in the endpoint configuration.

  • Incorrect values in payload
    → Double-check field mappings and ensure correct tags were used for each field.

Did this answer your question?