FlowRunner
PricingContact
Theme
Start Free

Atlas (AQX)

Voice & Telephony

Run AI voice and messaging campaigns through an Atlas (AQX) account, covering outbound, inbound, voice bubble, and Messages campaigns. Agents launch and monitor conversations at campaign scale and read results back into the flow.

4 triggers 107 actions API key available
An On Call Completed event fires for a campaign after a script version was published
Agent reads the conversation history and AI summary with Get Call Record Details
Agent compares Get Campaign Statistics against the pre-change baseline for connection rate and bookings
Agent pulls Get Campaign Version History to confirm which snapshot the current script came from
Agent posts the outcome shift alongside the diff between the live version and the previous one
The campaign owner picks a snapshot, and only then does the agent call Rollback Campaign

What This Integration Enables

Atlas (AQX) treats a campaign as a program rather than a call list. A campaign carries its own agent, voice, scripts, knowledge files, tools, phone numbers and calendar bindings, and it keeps a version history you can roll back to. That is unusual in this category, and it changes what an agent can safely do with it: instead of firing calls and hoping, a flow can publish a change, watch the statistics that follow, and reverse the change against a named snapshot when the numbers move the wrong way.

The connector reaches the whole surface. Agents create and configure campaigns across outbound phone, inbound phone, voice bubble and Messages channels, import contacts in bulk, upload or scrape knowledge files the campaign's agent answers from, generate Atlas Actions from an OpenAPI spec so the voice agent can call your systems mid conversation, and read back call records, transcripts, bookings and per-campaign statistics. It also reaches Set Human Handoff, which pauses the AI on one contact's thread and routes it to a live person. That last one is worth naming plainly: Atlas ships the switch, and FlowRunner is what decides when to flip it. An Orchestration as a Service layer earns its place precisely there, in the judgment about when a machine should stop talking.

Without FlowRunner

Script changes ship blind A prompt edit goes live and its effect only shows up in next week's numbers
Rollback is a memory exercise Restoring a working script means someone remembering what it used to say
Handoff is a fire drill A conversation that needs a person waits until someone notices the queue

With FlowRunner

Change tied to outcome Every published version is compared against the statistics that followed it
Rollback with evidence The owner chooses a named snapshot from version history with the numbers attached
Handoff is a step The flow sets human handoff on the contact and routes the live thread to a named person

Use Case Scenarios

Script regression caught and reversed

A campaign owner publishes a new opening line. Over the next two hours the On Call Completed trigger fires repeatedly, and the agent reads each conversation with Get Call Record Details. It watches Get Campaign Statistics for connection rate, completion percentage and bookings, and compares them to the window before the change. When the booking rate drops and the summaries start showing early hangups, the agent does not quietly revert. It pulls Get Campaign Version History, builds a diff between the live script and the previous snapshot, and posts both with the numbers. The owner picks the snapshot. The agent calls Rollback Campaign against that correlation ID and confirms the restore.

Inbound lead to booked meeting

A form submission lands. The agent creates the contact with Create Contacts, then calls Schedule Outbound Call so the campaign's agent dials while the lead is still at their desk. When the conversation ends, the agent reads Get Bookings by Call ID to see whether a calendar slot was actually taken, writes the summary and recording URL into HubSpot, and posts the booking into the rep's channel in Slack. Calls that ended without a booking are routed by their ended reason rather than lumped into one failed bucket.

A messaging thread that knows when to stop

An SMS conversation runs on a Messages campaign. The agent watches On Message Received, reads the thread with Get Chat Messages, and handles the routine turns automatically. When the contact says something the campaign was not built for, a pricing dispute or a cancellation threat, the agent calls Set Human Handoff to pause the AI on that thread, posts the full transcript to the account owner, and stands by. The owner replies through Send Human Agent Response, in the same thread, from the same number the customer has been texting. Nothing is restarted and nothing is lost.

Human-in-Loop Highlight

The gate is Rollback Campaign. A rollback replaces the live campaign, script and settings included, with an older snapshot. Every call and message placed after that moment uses the restored version, and the callers on the other end have no idea a version changed. Reverting to the wrong snapshot does not throw an error; it quietly reintroduces whatever was wrong with that version, and the cost shows up as conversations that went badly rather than as a failed job. So the agent builds the case and stops. It posts the campaign name, the live version's correlation ID and timestamp, the candidate snapshot, the recorded changes between them, and the connection rate, completion percentage and booking counts from Get Campaign Statistics for each window, then asks: "Bookings on Outbound Q3 dropped after version 2026-08-01T14:22. Roll back to the 07-28 snapshot, keep the current script, or hold the campaign while you review?" The owner decides which script the next thousand people hear. That is the digital andon cord in its literal form: the agent noticed, and it stopped the line.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

107 actions

Account

2
  • Get User Profile Retrieves the authenticated user's profile: display name, company, and profile picture URL.
  • Update User Profile Updates the authenticated user's profile information. Only the provided fields are changed.

API Keys

3
  • Get API Keys Lists the account's API keys with their creation date and active status.
  • Create API Key Creates the customer's API key. Only one active key per customer is allowed. Returns the new key value and its creation date.
  • Delete API Key Deletes the specified API key. Requests authenticated with a deleted key stop working immediately, so treat this as a live credential revocation rather than housekeeping.

Agents

6
  • Get All Agents Lists every AI agent on the account with its name, language, voice, provider, and script settings.
  • Get Agents by Campaign Lists the AI agents attached to a specific campaign.
  • Get Agent Retrieves a single AI agent by its ID, including name, language, voice settings, scripts, and speech tuning parameters.
  • Create Agent Creates a new AI agent for a campaign using server managed voice and agent type templates. With a template ID, scripts and settings resolve from the template; otherwise the agent type name, pre script and post script can be supplied inline.
  • Update Agent Updates an AI agent's name, language, voice, scripts, and speech tuning parameters. Pitch, region, volume, language boost, filler injection and text normalization are accepted on update but are not returned by read endpoints.
  • Delete Agent Deletes an AI agent from the campaign.

Bookings

2
  • Get Bookings Lists all calendar bookings made by the campaign's agent, including customer name, email, booking date, calendar, and status. Used to measure whether calls turned into meetings rather than just into minutes.
  • Get Bookings by Call ID Lists the calendar bookings made during a specific call, with customer details, booking date, and status.

Business Verification

3
  • Get Business Verification Profile Retrieves the current business verification profile, including the Twilio Secondary Customer Profile and Trust Product identifiers and their review statuses.
  • Upsert Business Verification Info Creates or updates the business verification profile and enqueues the background worker that provisions the Twilio Secondary Customer Profile.
  • Submit Business Verification for Review Submits the business verification profile to Twilio for review. The profile must exist first. Used to keep outbound identity compliant before a campaign scales.

Calendar Settings

4
  • Get Calendar Integrations Lists the account's Calendly or Cal.com integrations with their titles and settings.
  • Create Calendar Integration Creates a calendar integration for automated scheduling, with provider specific settings supplied as a JSON string.
  • Update Calendar Integration Updates an existing calendar integration's title, provider type, and settings.
  • Delete Calendar Integration Deletes a calendar integration from the account.

Calls

5
  • Schedule Outbound Call Queues an outbound call to a phone number using the agent configured on the campaign. With a scheduled date the call is placed at that time, otherwise it is queued immediately. Returns the queue sequence number.
  • Get Call Records Lists call records, optionally filtered by campaign, assistant, direction, campaign type, success result, date range or customer phone number. Each record includes duration, the reason the call ended, and customer details.
  • Get Call Record Details Retrieves the full details of a single call: the conversation message history, AI generated summary, status, and a public URL to the audio recording.
  • Delete Call Record Deletes a call record from the account.
  • Get Scheduled Calls Lists the calls queued for a campaign that have not been placed yet, with contact name, phone number, and scheduled date. Used to inspect what is about to go out before it does.

Call Forwarding

3
  • Get Call Forwarding Rules Lists the campaign's call forwarding rules with their destination, transfer message, and summary settings.
  • Create Call Forwarding Rule Creates a rule so the campaign's agent can transfer live calls to a phone number or SIP destination, optionally with an extension, a spoken transfer message, and a call summary. This is the live escalation path from the AI to a person mid conversation.
  • Delete Call Forwarding Rule Deletes a call forwarding rule from the campaign.

Campaigns

16
  • Get All Campaigns Lists every campaign on the account with its name, type, call direction, business name, first message, and active status.
  • Create Campaign Creates a campaign of one of four types: outbound phone, inbound phone, voice bubble on the web, or Messages and SMS. A campaign on its own is a shell; an agent is created for it next.
  • Get Campaign Retrieves a single campaign by ID with its configuration, linked phone number, and active status.
  • Update Campaign Updates a campaign's settings. Name, campaign type and template ID are required by the API on every update.
  • Delete Campaign Deletes a campaign from the account and returns the deleted campaign's data.
  • Set Campaign Status Enables or disables a campaign. Enabling starts real outbound activity against the campaign's contacts, so it belongs behind a condition a person set, not a default.
  • Update Campaign Chat Status Enables or disables outbound chat on a campaign.
  • Update Full Campaign Updates a campaign together with its agent in a single call, covering both the campaign body fields and the agent's language, voice, provider and tuning parameters.
  • Get Campaign Templates Lists the catalog of starter templates used to seed the template ID when creating a campaign, filterable by language.
  • Get Campaign Template Detail Retrieves a single starter template by ID with its title, description, channel type, and required fields.
  • Download Campaign Data Exports the campaign's data for archiving or analysis outside Atlas.
  • Get Campaign Version History Lists the campaign's saved version snapshots, each with a correlation ID, timestamp and the changes recorded. This is the evidence a rollback decision rests on.
  • Rollback Campaign Rolls the campaign back to a previous snapshot identified by its correlation ID. Every call and message after that point uses the restored version.
  • Test Caller Enrichment Tests caller enrichment for a specific provider, including Shopify, GoHighLevel, Monday.com and HubSpot, and returns the enrichment test result.
  • Get Campaign Calendars Lists the calendar integrations linked to the campaign.
  • Delete Campaign Calendar Unlinks a calendar integration from the campaign.

Campaign Chat

12
  • Get Chat Sessions Lists the campaign's chat sessions with contact identification, status, human handoff state and scheduled date. Used to find the threads that are waiting on a person.
  • Initiate Web Chat Starts a web chat session on the campaign by sending the first message for a given contact identifier.
  • Get Chat Messages Lists the messages of a chat session with role, content, delivery channel across iMessage, SMS, RCS or WhatsApp, and delivery status.
  • Get Chat Phone Numbers Lists the account's messaging phone numbers with their linked campaign, status, and RCS capability.
  • Link Chat Phone Number Links a messaging phone number to a campaign so the campaign sends and receives messages through it.
  • Unlink Chat Phone Number Unlinks a messaging phone number from its campaign.
  • Cancel Chat Phone Number Cancels a messaging phone number and removes it from the account.
  • Schedule SMS Session Schedules or immediately starts a Messages session with a contact, supporting a custom first message, attachment URLs for MMS, and a scheduled date.
  • Send Human Agent Response Sends a manual reply from a live agent into a chat session. The session must be the contact's current session and must already be in a human handoff state.
  • Upload Chat Media Uploads one or more media files into a chat session and returns their hosted URLs for use as message attachments.
  • Send Voice Message Sends a voice message into a chat session from base64 encoded MP3 or WAV audio.
  • Set Human Handoff Sets human handoff for a single contact. True pauses AI agent replies and routes the conversation to a live agent; false returns it to automated handling. This is the platform's own pause switch, and it is the natural landing point for a flow that has decided a person should take the next turn.

Contacts

11
  • Bulk Import Contacts Bulk imports a list of contacts into a campaign. Each contact requires a first name, last name, and an E.164 phone number with country code.
  • Create Contacts Adds one or more contacts without uploading a CSV, validating each independently and returning accepted and rejected records separately. With no campaign given, contacts are created as global contacts and will not be dialed.
  • Get Contacts by Campaign Lists the contacts attached to a campaign with their names and timezone information.
  • Get Contact Retrieves a single campaign contact by ID with name and timezone information.
  • Update Contact Updates a campaign contact's name, phone number, and timezone.
  • Delete Contact Deletes a contact from the campaign.
  • Get Global Contacts Lists all account level contacts with their names and timezone information.
  • Update Global Contact Updates a global contact's name, phone number, and timezone. This endpoint has upsert semantics, so an unknown ID is created rather than rejected.
  • Delete Global Contact Deletes a global contact from the account.
  • Get Contact Tokens Lists the contact field tokens available for use in the campaign's scripts.
  • Get Contact Count Returns the total number of contacts attached to the campaign. Used as a scale check before enabling a campaign.

Usage and Statistics

6
  • Get Quota Information Retrieves the account's quota: plan quota, purchased milliseconds, rollover milliseconds and total usage.
  • Get Monthly Minutes Usage Retrieves the account's custom monthly minutes usage records.
  • Get Dashboard Statistics Retrieves account wide totals split by direction: calls, duration, connection rate, successful calls, bookings made, transfers made and the last call date.
  • Get Deployment Statistics Retrieves deployment statistics split by direction, optionally limited to a date range.
  • Get All Campaigns Statistics Retrieves overview statistics across every campaign: totals, past week figures, connection rates, differences, bookings and transfers.
  • Get Campaign Statistics Retrieves statistics for a single campaign: total and past week calls, connection rates, completion percentages, successful calls, transfers and bookings. This is the measurement a rollback decision is argued from.

Webhooks

4
  • Get Sample Event Payload Returns an example payload for a given event, built from real data in the specified campaign, so a receiver can be built and tested before subscribing.
  • Create Webhook Subscription Registers a webhook so Atlas posts to a hook URL every time the chosen event fires for a campaign. Each subscription is one event for one campaign.
  • Delete Webhook Subscription Removes a previously registered webhook so Atlas stops delivering the event.
  • List Campaign Webhooks Lists every webhook currently registered for the campaign with its event name, hook URL and provider.

Knowledge Base

10
  • Get All Knowledge Files Lists every knowledge base file on the account with its name, collection tags and Atlas file identifier.
  • Upload Knowledge File Uploads a knowledge base file from a URL in PDF, DOCX, TXT or Markdown up to 10 MB. Files are chunked and embedded automatically and can be attached to a campaign at upload time.
  • Extract Knowledge from URL Scrapes a web page and converts it into a Markdown knowledge file. The scraper captures visible text, so JavaScript heavy pages may return limited content.
  • Delete Knowledge File Deletes a knowledge base file by filename, optionally scoped to a campaign.
  • Get Campaign Knowledge Files Lists the knowledge base files attached to a campaign with their names and sizes.
  • Attach Knowledge File to Campaign Attaches an existing knowledge base file to a campaign so its content is available to that campaign's agent.
  • Detach Knowledge File from Campaign Detaches a knowledge base file from a campaign without deleting the file.
  • Add Knowledge File to Collection Adds a knowledge base file to a named collection tag.
  • Remove Knowledge File from Collection Removes a knowledge base file from a named collection tag.
  • Get Knowledge File Linked Campaigns Lists the IDs of the campaigns a knowledge base file is attached to, so a change to one document can be traced to every campaign it will affect.

Phone Numbers

6
  • Get All Phone Numbers Lists the account's voice phone numbers with their provider, linked campaigns and call types.
  • Get Phone Number Retrieves a single voice phone number by ID with its provider, SIP details, linked campaigns and call types.
  • Integrate Phone Number Integrates a new voice phone number into a campaign, from a Twilio account or a SIP trunk.
  • Link Phone Number Links an existing voice phone number to a campaign.
  • Unlink Phone Number Unlinks a voice phone number from its campaign.
  • Delete Phone Number Deletes a voice phone number from the account.

Tools

10
  • Get All Tools Lists every Atlas Action on the account with its name, type, settings, template, categories and purpose.
  • Create Tool Creates an Atlas Action the agent can call during a conversation, including custom webhook tools, playable audio, one way SMS and SMS verification.
  • Update Tool Updates an Atlas Action's name, type, settings, template, categories, group and purpose.
  • Delete Tool Deletes an Atlas Action from the account.
  • Create Tool from Template Creates an Atlas Action from a prebuilt template, filling the template's placeholders with the provided values.
  • Get Tool Templates Lists the prebuilt tool templates with their categories, settings and required and optional placeholders.
  • Search Tool Templates Searches the tool template catalog by text query and category filters.
  • Get Tool Template Categories Lists the tool template categories with their names, descriptions and icons.
  • Get Tool Execution Metrics Lists tool execution records, optionally filtered by call, campaign, tool, date range or success flag. Used to find the tool call that is failing quietly inside otherwise normal conversations.
  • Generate Tools from OpenAPI Spec Auto generates one Atlas Action per endpoint from an OpenAPI definition supplied inline or by URL.

Voices

4
  • Get All Voices Lists the voices available on the account with their name, gender, language, provider, preview URL and provider settings.
  • Clone Voice Creates a custom cloned voice from audio sample files fetched from the provided URLs. Returns the created voice with its preview URL.
  • Delete Voice Deletes a voice from the account.
  • Get Pangram Sentences Returns pangram sentences for voice testing and cloning, sized by quantity or by target recording duration.

Triggers

4 triggers

Event Triggers

4
  • On Call Started Fires when a call begins on a campaign, with an optional campaign filter. Used to open a record, mark the contact as in progress, or hold competing outreach while a live conversation is underway.
  • On Call Completed Fires when a call finishes. Used to pull the transcript and summary, write the outcome to the CRM, and branch on the reason the call ended rather than treating every non booking the same way.
  • On Message Received Fires when a contact replies on a Messages campaign. Used to read the thread, decide whether the AI should keep going, and set human handoff when the answer needs a person.
  • On Message Sent Fires when the campaign sends a message. Used for delivery auditing and for keeping an external conversation log in step with what the campaign actually sent.

Frequently Asked Questions

What can FlowRunner do with Atlas (AQX)?

FlowRunner agents can run Get User Profile, Update User Profile, and Get API Keys in Atlas (AQX), plus 104 more actions.

Does connecting Atlas (AQX) to FlowRunner require OAuth?

No. Atlas (AQX) connects to FlowRunner with an API key, no OAuth flow required.

Can Atlas (AQX) trigger a FlowRunner workflow automatically?

Yes. Atlas (AQX) supports 4 triggers that can start a FlowRunner workflow automatically.

Start building with Atlas (AQX)

$100 in credits. No card required. Connect in minutes.