Receive leads by webhook
Choose and test Nexor’s per-door webhook or generic Public API webhook for inbound leads.
Choose the right endpoint
Per-door webhook
Create and manage this door from Custom connection. Its field map uses incoming paths as keys and Nexor fields as values:first_name is mapped but last_name is not, Nexor splits a multi-word mapped name after the first word.
After mapping, the payload must contain at least one of first_name, last_name, email, or phone.
Validate without creating a lead
200, dry_run: true, and the translated lead. It does not create a lead. Remove dry_run=true only after checking the translated identity and destination agent.
The endpoint allows 120 requests per IP address per minute. A disabled door returns 403; an invalid token returns 404; a payload without an identity field returns 400. A new lead returns 201. When door deduplication is enabled, Nexor checks email when present, otherwise phone, and an existing lead returns 200 with duplicate: true.
Generic Public API webhook
The generic route uses the same single-lead processing asPOST /leads. A workflow_id in the JSON body takes precedence over the query parameter.
?token= and send X-API-Key instead. With no intake map on the key, the body must already use Nexor’s canonical field names. With a per-key intake map, Nexor resolves configured aliases and can carry unconsumed fields into lead metadata.
POST /api/public/leads/odoo remains an identical compatibility alias. It is not the native Odoo API-key integration and should not be used as the name of a new custom connection.
Authorizations
API key passed in the query string for webhook senders that cannot set headers. Prefer X-API-Key when the sender supports custom headers.
Query Parameters
API key for senders that cannot set X-API-Key. Do not place it in logs or screenshots.
Optional agent assignment. A workflow_id in the JSON body overrides this value.
Body
Inbound lead payload. If the API key has an intake field map, provider-specific keys are translated first and unrecognized fields may be preserved in metadata. Without a map, use the canonical fields below.
Lead's first name
Lead's last name
Lead's email address
Lead's phone number
Lead identifier in the source system
Source label. Defaults to api.
Agent assignment. This body value overrides the query parameter.
Create or update the lead without starting outreach