Overview
Webhook delivery methods enable seamless lead transmission to external systems using standardized formats:
JSON: Ideal for modern APIs and web applications
XML: Compatible with legacy enterprise systems
HTTP Requests: Universal integration for any HTTP-enabled platform
This article will provide step by step instructions for creating a HTTP Webhook delivery method, the examples shown are for a JSON webhook delivery method.
Step-by-Step Setup
How to Create a Webhook Delivery Method
Navigate to Delivery Methods → Click Create
Configure your webhook's basic settings:
Field | Description | Observations |
Description | Identify your webhook, for example: "CRM Webhook" |
|
Delivery Type | Select Webhook | Critical for proper setup |
Lead Type | Choose the associated lead type | Keep in mind this cannot be changed later |
Environment | Production/Testing | Use "Testing" if your client provides a testing URL endpoint while setting up |
3. Click Create → Proceed to the URL Endpoint tab for configuration
Key Considerations
Format Commitment: Lead type selection is permanent after creation
Testing Protocol: Always validate with test endpoints before production use to prevent faulty deliveries
Data Mapping: Ensure field structure matches your recipient's posting requirements. This is key in preventing faulty deliveries and/or missing information
Best Practices
Naming Convention:
Try to nclude the format you're using or the recipient's platform for clarity (e.g., "CRM JSON Webhook")Validation:
Test with sample leads before going live. Some buyers may provide a sandbox URL endpoint to validate proper reception of incoming leadsSecurity:
You may use HTTPS endpoints and authentication tokens to ensure secure lead delivery
Troubleshooting
Failed deliveries:
Verify the endpoint URL, server status, and format, ensuring that you're sending all the fields required by your buyer.Format errors:
Check the JSON/XML structure against your buyers' specs.Authentication failures:
Validate API Keys or tokens that may be missing or incorrect.
Next article: URL Endpoint Tab >