Skip to content
NexaCloserNexaCloser Docs

Send data to an inbound webhook

POST
/{slug}
curl --request POST \
  --url https://hook.nexacloser.com/example \
  --header 'Content-Type: application/json' \
  --header 'X-Webhook-Token: <X-Webhook-Token>' \
  --data '{ "full_name": "Dana Levi", "email": "[email protected]", "phone": "+972501234567", "form_name": "Contact us" }'

Create the webhook in the app under Automations → Webhooks; it gets a URL like https://hook.nexacloser.com/<slug> and a secret token. Send any JSON or form fields to it.

  • Every automation whose trigger is this webhook runs, with your fields available as variables in its steps.
  • If the webhook has CRM Integration turned on (auto-create a lead each time), the phone / email / full_name (or name) fields, after the webhook’s field mapping, become a CRM contact and a lead in the chosen pipeline.
  • The same body sent twice within 2 minutes is accepted once: the repeat returns the first execution_id with deduped: true and starts nothing.

Bodies up to 1 MB. application/json, application/x-www-form-urlencoded and multipart/form-data are read; any other body is read as JSON, or kept as raw text.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
slug
required
string

The webhook’s slug, from its URL.

Request Body

Section titled “Request Body”
object
key
additional properties
any

Example 

{
  "full_name": "Dana Levi",
  "email": "[email protected]",
  "phone": "+972501234567",
  "form_name": "Contact us"
}

Responses

Section titled “Responses”

200

Section titled “200”

Accepted.

Media typeapplication/json
object
success
required
boolean
execution_id
required

The stored execution, visible on the webhook in the app.

string | null
automations_triggered
required

How many automations were started.

integer
deduped

true when this was a repeat of a body sent in the last 2 minutes.

boolean

Examples

{
  "success": true,
  "execution_id": "whx_8plFFIhUWR",
  "automations_triggered": 1
}

401

Section titled “401”

The webhook has a secret and the X-Webhook-Token header is missing or wrong.

Media typeapplication/json

Older endpoints return a short English message instead of a code.

object
error
required
string

Example 

{
  "error": "Unauthorized"
}

404

Section titled “404”

No active webhook with this slug.

Media typeapplication/json

Older endpoints return a short English message instead of a code.

object
error
required
string

Example 

{
  "error": "Webhook not found"
}

413

Section titled “413”

The body is larger than 1 MB.

Media typeapplication/json
object
error
required

A stable, machine-readable code.

string

Example 

{
  "error": "payload_too_large"
}

429

Section titled “429”

Too many requests. Wait Retry-After seconds.

Media typeapplication/json
object
error
string
Allowed value: rate_limited
message
string
retry_after

Seconds to wait.

integer

Example 

{
  "error": "rate_limited",
  "message": "Too many requests",
  "retry_after": 7
}

Headers

Section titled “Headers”
Retry-After
integer

Seconds to wait before retrying.