Integrations

Connect third-party services to enhance your agents' capabilities. Integrations allow your AI agents to take real-world actions during conversations: booking meetings, looking up contact records, taking card payments, and syncing data with the tools your team already uses. Cloudax Connect currently supports Calendly for scheduling, HubSpot for CRM, and Cloudax Payments for in-call card collection. It also connects to your own infrastructure: save a Twilio account to reuse across number imports, and stream call telemetry to any OpenTelemetry backend for observability.

Calendly

Overview

The Calendly integration lets your agents automatically schedule meetings during live conversations. When a caller or chatbot visitor expresses interest in booking, the agent checks your real-time availability and creates the event on your behalf (no manual back-and-forth required).

Connecting Calendly

Syncing Event Types

After connecting your Calendly account, click Sync Event Types to pull in your available event types (e.g. "30-Minute Discovery Call", "Product Demo"). The agent uses these event types to understand what kinds of meetings it can offer to callers.

If you add or modify event types in Calendly later, return to the Integrations page and re-sync to keep everything up to date.

Using in Agents

Once Calendly is connected and your event types are synced, open the agent you want to enable scheduling for. In the editor sidebar, go to the Integrations tab and toggle Calendly on. Your agent will now be able to check availability and book meetings during conversations.

HubSpot

Overview

The HubSpot integration connects your CRM to Cloudax Connect so that call outcomes flow straight into HubSpot. After each call, the platform finds the matching contact by phone number or email (creating one if none exists), updates it with the details captured on the call, and can log the interaction against contacts, deals, and activities (no manual data entry required).

Connecting HubSpot

Syncing Data

After connecting, click Sync Contacts and Sync Deals to pull your CRM data into Cloudax Connect, so contact and deal records are visible alongside your call data.

Data syncs can be triggered manually at any time. Each integration card shows the timestamp of the last successful sync so you always know how current your data is.

Using in Agents

With HubSpot connected, open the agent you want to enable CRM sync for. In the editor sidebar, navigate to the Integrations tab and toggle HubSpot on. Calls handled by that agent are then synced to HubSpot automatically after they end; contacts are created or updated and interaction outcomes are logged. Use the field mapper to control exactly which call fields (including AI-extracted values) map to which HubSpot properties.

Cloudax Payments

Overview

Cloudax Payments lets your voice agents collect card payments mid-call by sending the caller a one-time secure link over SMS. The caller pays from their handset, the agent confirms when the transaction completes, and the result is recorded against the call and any related ticket or order. PAN, CVV, and expiry data never touch your agent or our systems; Cloudax Payments is powered by an underlying PCI-compliant provider, and the agent only ever sees the outcome.

Connecting Cloudax Payments

From the Integrations page, click Connect on the Cloudax Payments card. You'll be asked for a small set of credentials supplied by your Cloudax onboarding contact:

• Display name: A friendly label (e.g. “Production Pay”).
• Client ID and Client Secret: Your provider credentials.
• Base URL and OAuth Token URL: Pre-filled with the sensible defaults for our hosted environment; override only if you've been told to.
• Return URL: Where the caller's browser lands after they pay.
• SMS Alpha Tag: The short sender name shown when the payment link SMS arrives.

After saving, click Test connection to verify the credentials, then Copy webhook URL and configure it inside your payment provider's portal so payment outcomes flow back to Cloudax Connect. You can rotate the webhook secret at any time from the same panel without re-entering your OAuth credentials.

Using in Agents

Once connected, open the agent you want to enable payments for and switch on the Payments option in the agent editor. If your workspace has more than one payment provider configured you can pick which one this agent uses. The agent can then ask for and confirm payment amounts during a call; it sends the SMS link, stays on the line to talk the caller through it, and reads back the result once the callback comes in.

Tracking Payments

Once any agent has Cloudax Payments enabled, a Payments entry appears in the sidebar. The Payments page is a real-time table of every link the platform has issued: status (sent / processing / paid / failed), amount, customer mobile, the agent and call that initiated it, and a deep-link straight into the originating call log. Status updates stream over the same realtime channel as the calls dashboard, so a payment flips from processing to paid on screen the moment the webhook lands (no refresh required).

The sidebar entry only appears once you have at least one payments provider connected, so workspaces that don't use Cloudax Payments never see it.

Twilio Accounts

Overview

Connect one or more Twilio accounts to your workspace so their credentials are entered once and reused every time you import, buy, or manage a phone number (no more pasting an Account SID and Auth Token into every import). Accounts belong to the whole workspace, so any team member with the right permission can use a saved account without ever seeing the secret token.

Connecting a Twilio account

Managing accounts

Each account row shows its friendly name, masked SID, region, and how many numbers were imported through it. You can re-verify credentials, update details, or disconnect an account you no longer use. Disconnecting is a soft action; numbers already imported keep working, so removing an account never breaks live routing.

OpenTelemetry Traces

Overview

Export a full trace of every completed call to your observability stack. When a call ends, Cloudax turns it into an OpenTelemetry (OTLP) trace: a root cloudax.conversation span with a child span per conversation turn (cloudax.recv.user_transcript, cloudax.recv.agent_response) and per tool call (cloudax.tool.*), annotated with latency, token, and cost attributes. Use it to monitor agent performance, debug slow turns, and keep a durable record of conversations in the tools you already run.

Connecting a backend

Post-call export

With Post-call export enabled, Cloudax automatically ships a trace to your backend after each call ends. Delivery is best-effort so observability never interferes with call handling; if your collector is briefly unreachable, the call itself is unaffected and you can always re-fetch the trace on demand (below). Toggle this off from the dialog if you only want on-demand exports.

On-demand export via the API

You can fetch any call's trace at any time from the public API by adding ?format=opentelemetry to the call-log endpoint. The response includes an otlp_traces object alongside the normal call data:

GET /api/v1/call-logs/{id}?format=opentelemetry

This uses the same call-logs:read API-key scope as the rest of the call-logs API and is the reliable path for backfilling or re-processing historical calls. See the Developers reference for API keys and scopes.

Managing Integrations

Each integration card on the Integrations page displays key information at a glance:

• Connection status: a green badge for connected, grey for disconnected.
• Authorised user: the name and email of the account that authorised the connection.
• Last sync time: when data was last pulled from the third-party service.

Disconnecting an Integration

To disconnect a service, click the Disconnect button on its card. This revokes the OAuth token and removes the connection. Any agents that had the integration enabled will no longer be able to use its features; make sure to update those agents or disable the integration toggle in their settings first.

Refreshing Tokens

OAuth tokens are refreshed automatically behind the scenes. If a token expires unexpectedly (for example, if you revoke access from the third-party service directly), the integration card will show a warning status. Simply click Reconnect to re-authorise and restore the connection.