Your lead workflow doesn't have to end inside Zorcha. Send HTTP Request calls an external endpoint so a supported flow can pass available details to another service, such as a system your team uses to handle enquiries.
Get the receiving service's requirements
You need its HTTPS endpoint, request method, authentication headers, and expected request body. A webhook isn't automatically compatible with every app; use the format the receiver actually accepts.
Keep API keys and private contact data out of public examples and screenshots.
Configure the request
Add Send HTTP Request and give it a clear request identifier.
Select the method and enter the receiving endpoint.
Add the required headers and JSON body.
Use the variable controls for values that should come from the contact or form. A fixed example value doesn't automatically include a form answer.
If you import cURL, review the imported URL, headers, and body before continuing.
Run Validate and resolve the reported settings problems.
Illustrative request settings only. Replace the example endpoint and fixed values with your receiver's requirements and field mappings.
Verify the request at the receiver
The reviewed editor's Test Request panel displays a sample response. It doesn't prove your endpoint received a request.
When ready for a controlled automation run, perform the trigger and inspect the receiver's request log. Check the field names, values, and saved record. An HTTP success status doesn't necessarily mean the receiver stored the data as intended.
For errors, check authentication, the expected method, and the JSON format. For an end-to-end form example, see Build a form-to-webhook flow.