Connect Custom inbound webhook
Map signed events from another service into AXO Pipeline and profile traits.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
secret | Shared signing secret; at least 16 characters for the readiness check. |
signature_scheme | stripe, hex, or github. |
mapping | Payload path: contact.email, contact.phone, contact.name, field.KEY, trait.KEY, or note. |
event_id_path | Optional stable delivery-ID path; otherwise byte-identical bodies are deduplicated. |
on_flagged | quarantine (default), allow, or deny for new flagged records. |
Connect
Open Integrations, find Custom inbound webhook, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Select Custom Webhook under inbound sources. Configure at least one contact.email or contact.phone mapping and save.
- Copy the receiving URL shown after saving into the sending system. Sign the raw request using the selected scheme.
- Send a controlled delivery from that system, inspect captured fields, and refine the mapping. Quarantined records require review before replay releases them.
Verify the result
The AXO check validates local configuration only. A successful sender delivery should appear in the capture mapper and the intended Pipeline/profile record.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Check signature scheme, raw body, timestamp for Stripe-style signatures, contact matching, existing custom-field keys, and quarantine status.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.