Payload mapping
Tell the gateway where to find user_id and message in your webhook.
Last updated October 1, 2026
The gateway needs to know where, inside your webhook's JSON, the sender's identifier and the message text live. If you picked a known source channel at creation, these are pre-filled for you.
The two paths
| Field | Default | Details |
|---|---|---|
user_id_field_path | user_id | JSON path to the sender's identifier. Dot notation: payload.sender.id. Used for rate limiting and dedup per user. |
message_field_path | message | JSON path to the message text. Used for token counting, dedup hashing, keyword routing and language detection. |
Dot notation
Paths walk nested objects and arrays with dots. For WhatsApp Business payloads, the defaults are:
entry.0.changes.0.value.messages.0.from— the user identry.0.changes.0.value.messages.0.text.body— the message text
If extraction fails (a path points nowhere), the message is still delivered — the envelope's user_id or message will simply be null.