Integration
Connect Callers and Coro
When Call Ended fires in Callers, your agent runs Add Ticket Comment in Coro, or New Audit Log Entry in Coro to Add Contact Memory in Callers. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Callers and Coro to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Callers and Coro can do together
From Callers to Coro
When Call Ended in Callers
then Add Ticket Comment in Coro
When Call Ended in Callers
then Perform Ticket Action in Coro
From Coro to Callers
When New Audit Log Entry in Coro
then Add Contact Memory in Callers
When New Device in Coro
then Update contact memory in Callers
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Callers and Coro
Triggers and actions 5 triggers · 37 actions
Trigger
Call EndedTriggers when an agent's call finishes.
Action
Add Contact MemorySaves a fact that agents remember about a contact in later conversations.
Action
Delete agentDeletes (archives) an agent and stops its active workflows. The agent's data and related records are kept.
Action
Delete All Contacts From CampaignArchives every contact of an agent.
Action
Delete ContactArchives one of an agent's contacts so it is no longer called.
Action
Delete contact memoryDeletes a memory saved on a contact, marking it as deleted.
Action
Delete Contact With Phone NumberArchives an agent's contact found by phone number.
Action
Get Account InformationReturns the Callers account (organization) the API key belongs to.
Action
Get AgentReturns one Callers agent by its ID.
Action
Get agent reportReturns a report of an agent's contacts grouped by status, including the total call count.
Action
Get Calls for ContactReturns the calls an agent made to one contact.
Action
Get Campaign ContactsReturns the contacts of an agent.
Action
Get ContactReturns one of an agent's contacts by its ID.
Action
Get Contact MemoriesReturns the facts agents remember about a contact.
Action
Get Recording UrlReturns a URL for the recording of a call.
Action
List AgentsReturns the agents in a Callers account.
Action
List callsReturns the calls made or received by a Callers agent, including status, duration, transcript and recording link.
Action
List VoicesReturns the voices available in the account.
Action
Start AgentStarts an agent so it begins calling its contacts.
Action
Stop AgentStops an agent from calling its contacts.
Action
Update agentUpdates an agent's name, assigned phone numbers or webhooks. Only the fields you fill in are changed.
Action
Update contact memoryUpdates the text of an existing contact memory. Callers keeps the old version as outdated and returns the new version.
Trigger
New Audit Log EntryTriggers when a new audit log entry is recorded in the workspace.
Trigger
New DeviceTriggers when a new device is enrolled in the workspace.
Trigger
New Protected UserTriggers when a new user appears in the workspace.
Trigger
New TicketTriggers when a new security ticket is created in the workspace.
Action
Add Portal UserInvites a user to the Coro end-user portal.
Action
Add Ticket CommentAdds a comment to a security ticket.
Action
Get Portal UserReturns one end-user portal user by ID.
Action
Get TicketReturns one security ticket by ID.
Action
Get UserReturns one user by ID.
Action
Get WorkspaceReturns the details of the connected Coro workspace.
Action
List DevicesReturns the protected devices in the workspace.
Action
List Portal UsersReturns the users of the Coro end-user portal.
Action
List Ticket ActionsReturns the actions that can be taken on a security ticket.
Action
List Ticket CommentsReturns the comments on a security ticket.
Action
List TicketsReturns security tickets in the workspace, optionally filtered by processed state and time range.
Action
List UsersReturns the users in the workspace, optionally filtered by email or name.
Action
Perform Ticket ActionRuns an action on a security ticket, such as marking it processed.
Action
Search Audit LogsReturns audit log entries for the workspace within an optional time range.
Action
Search WorkspacesReturns the child workspaces the connected workspace can access, optionally filtered by a search term.
Action
Update User ProtectionTurns Coro protection on or off for a user, identified by email.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Callers
Callers to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Callers to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Callers to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Callers to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Callers to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Callers to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Coro
ActiveCampaign to CoroActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CoroOrganize anything with Airtable, a modern database created for everyone.
Asana to CoroAsana is a collaborative information manager for workspace.
ClickUp to CoroClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to CoroBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CoroCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
Callers and Coro, answered
What can start an automation from Callers?
Any of Callers's 1 trigger in the catalog, including Call Ended. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Coro when something happens in Callers?
Any of Coro's 16 actions, including Update User Protection, Add Portal User, Add Ticket Comment and Get Portal User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Coro to Callers?
Yes. When something happens in Coro, your agent can act in Callers too. This page covers both directions: Coro's triggers and Callers's actions are listed here as well.
Do I have to build a connector for Callers or Coro?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Callers and Coro without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.