Connect Outbound webhook
Send subscribed AXO events to your HTTPS receiver.
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 |
|---|---|
url | Public HTTPS receiver URL. |
secret | Set a long private signing secret even though the drawer marks it optional. |
Connect
Open Integrations, find Outbound webhook, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Build a receiver for the integration webhook envelope and X-VibeTag-Signature.
- Select events in Events to forward. Save the receiver URL and secret.
- Verify a signed intended event using the ingestion reference.
Verify the result
Send test event POSTs an unsigned test_ping with a different body. A signature-enforcing receiver should reject it; this test cannot prove signed event processing.
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
Never weaken production signature verification to pass the unsigned ping. Check an actual signed delivery and the Health log. Pulse subscriptions use a separate protocol.
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.