Outgoing webhooks

To send data out of NexaCloser, add a Custom Webhook step to an automation. It sends an HTTP request to your URL whenever the automation reaches it, for example on every new lead or every won deal.

Set it up

1. In an automation, add the Custom Webhook step.
2. Enter the URL, the method, the body (JSON, with {{variables}} from earlier steps) and any headers. Authorization can be a Bearer token or Basic auth.
3. Click Test webhook. Your endpoint must answer HTTP 200 with a response body.
4. Publish the automation.

The test is required. A Custom Webhook step that has not passed a test, or whose URL, body or headers changed since its last passing test, does not run: the automation stops at that step with Custom webhook must be tested successfully or re-test required. Re-test after every change.

What your endpoint gets

• The method you chose (POST by default) with the JSON body you built, variables filled in.
• The headers you set.

Rules

Rule	Value
Scheme	HTTPS only
Addresses	Public internet only. Private, local and internal addresses are refused, also after redirects or DNS changes.
Redirects	Not followed
Timeout	15 seconds by default (5 to 30)
Response size	Up to 1 MB; the first 1,000 characters are saved on the run

The step’s result (status_code and the saved part of response_body) is available to later steps and is shown on the automation run.

Make your endpoint reliable

• Answer fast (under a few seconds) and do slow work after you answer.
• Answer 200 with a short body such as {"ok":true}.
• Check a secret header you configured on the step, so only NexaCloser can call your endpoint.