Connect AXO Voice
Bring completed call outcomes and mapped answers into Pipeline.
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 | Signing secret minted by AXO Voice when registering the endpoint. |
lookup_secret | Optional separate caller-lookup secret. |
answer_map | Optional question-key mappings to existing fields, contact.first_name, title.topic, task.callback, note, or fork. |
Connect
Open Integrations, find AXO Voice, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Open AXO Voice in Integrations and copy the receiving URL into the Voice workspace’s Integrations page.
- Copy its signing secret back to AXO and save.
- Map question keys to the intended Pipeline fields. Unmapped answers still appear verbatim in the activity timeline.
Verify the result
The connection check validates the secret and mapping; it does not make a call. Verify a controlled completed call in Pipeline activity.
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
Match question keys exactly and use existing funnel field keys. Keep a separately minted lookup secret distinct from the delivery secret.
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.