Connect Segment
Send trigger events to a Segment HTTP source.
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 |
|---|---|
api_key | Write key from the Segment source. |
Connect
Open Integrations, find Segment, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create a trigger, select this integration as its destination, and render the provider’s expected payload in its template. Selecting Events to forward alone does not invoke this native trigger adapter.
Verify the result
The check sends AXO Connection Test for user axo_connection_test. Downstream Segment destinations may receive it.
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
Verify the source’s debugger and destination filters. A source ingest success does not prove every downstream destination delivered.
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.