Integration
Connect Coro to Chatbase
When New Audit Log Entry fires in Coro, your agent runs Add ticket message in Chatbase. 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 Coro and Chatbase 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 Coro can start in Chatbase
When New Audit Log Entry in Coro
then Add ticket message in Chatbase
When New Device in Coro
then Update ticket in Chatbase
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 Coro and Chatbase
Triggers and actions 4 triggers · 33 actions
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.
Action
Add agentCreates a new Chatbase agent (chatbot), optionally trained on supplied text.
Action
Add sourceAdds a training source (text, Q&A, or website link) to a Chatbase agent. The source starts training immediately.
Action
Add ticket messagePosts a customer-visible reply to a Chatbase helpdesk ticket on behalf of a team member. Delivery to the customer happens asynchronously.
Action
Delete agentPermanently deletes a Chatbase agent and all of its associated data.
Action
Delete conversationDeletes a conversation from an agent, whatever channel it came from. It no longer appears in chat logs.
Action
Delete sourceDeletes a source from a Chatbase agent, removing its knowledge from the agent. Returns the source in its final state.
Action
Find conversations by textSearches an agent's conversations by free text and optional filters, returning matching conversations with highlighted snippets.
Action
Get agentReturns a single Chatbase agent with its instructions, model, visibility, styles and training status.
Action
Get conversationReturns a conversation's details and its most recent messages. Only conversations created through the API are returned.
Action
List agentsReturns all agents (chatbots) in your Chatbase account, with each agent's name, model, training status and settings.
Action
List conversationsReturns the conversations created through the API for a Chatbase agent, optionally limited to a creation date window.
Action
List sourcesReturns the training sources (links, files, Q&A, Notion pages, text) of a Chatbase agent, optionally filtered by type or name.
Action
List ticketsReturns the helpdesk tickets for a Chatbase agent, optionally filtered by status, channel, assignee, team, priority and creation date.
Action
Send PromptSends a message to a Chatbase agent and returns the agent's reply, starting a new conversation or continuing an existing one.
Action
Update agentUpdates an existing Chatbase agent's name, instructions, model and other settings. Only the fields you fill in are changed.
Action
Update sourceUpdates an existing text, Q&A or link source on a Chatbase agent. Changing content retrains the source.
Action
Update ticketUpdates a Chatbase helpdesk ticket's status, assignee, team or priority. Only the fields you fill in are changed.
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 Coro
Coro to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coro to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coro to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coro to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Chatbase
HubSpot to ChatbaseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ChatbaseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ChatbaseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to ChatbaseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ChatbaseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ChatbaseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Coro and Chatbase, answered
What can start an automation from Coro?
Any of Coro's 4 triggers in the catalog, including New Audit Log Entry, New Device, New Protected User and New Ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Chatbase when something happens in Coro?
Any of Chatbase's 17 actions, including Send Prompt, Update agent, Update source and Update ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Chatbase to Coro?
Chatbase has no triggers in the catalog today, so automations start in Coro. If you need the other direction, ask: your agent reads Chatbase's API documentation and adds it.
Do I have to build a connector for Coro or Chatbase?
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 Coro and Chatbase 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.