Integration
Connect Chaport to DocsBot AI
When Chat Stage Updated (instant) fires in Chaport, your agent runs Chat Agent Message (Recommended) in DocsBot AI. 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 Chaport and DocsBot AI 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)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 Chaport can start in DocsBot AI
When Chat Stage Updated (instant) in Chaport
then Chat Agent Message (Recommended) in DocsBot AI
When New Chat Started in Chaport
then Add lead in DocsBot AI
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 Chaport and DocsBot AI
Triggers and actions 8 triggers · 25 actions
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
Action
Add botCreates a new DocsBot bot in a team, optionally copying sources from an existing bot.
Action
Add leadCaptures or updates a lead for a DocsBot conversation, merging the supplied contact details (email, name, company and so on) into the lead record.
Action
Add sourceCreates a new training source (URL, sitemap, document, Q&A and more) on a DocsBot bot.
Action
Ask Question (Legacy)Asks a DocsBot bot a question using the legacy Chat API and returns the answer, its sources and the updated chat history.
Action
Chat Agent Message (Recommended)Sends a message to a DocsBot bot in a stateful conversation and returns the agent's answer, sources and conversation history.
Action
Create Web SourceAdds a web-based training source (a page URL, sitemap, RSS feed or YouTube video) to a DocsBot bot and returns the created source.
Action
Delete botPermanently deletes a bot from a DocsBot team.
Action
Delete leadDeletes one captured lead record from a DocsBot bot.
Action
Delete sourceDeletes a training source from a DocsBot bot. The source may still appear in chat answers for a few minutes afterwards.
Action
Get botReturns one DocsBot bot with its settings, model, status and source counts.
Action
List botsReturns the bots in a DocsBot team, optionally filtered by text or privacy and sorted.
Action
Semantic SearchSearches a bot's trained content and returns the most relevant source chunks for a natural-language query.
Action
Update botUpdates the settings of an existing DocsBot bot, such as its name, description, prompt, model, privacy and widget appearance. 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 Chaport
Chaport to StripeStripe is a payment processing platform for online businesses.
Chaport to ChatraceOmnichannel chatbot platform for automating customer support and sales via WhatsApp, SMS, Messenger...
Chaport to keycdn IP Location FinderGet the IP geolocation data through the simple REST API. All the responses are JSON encoded
Chaport to ProxiedMailProxiedMail provides creating email addresses, forwarding and receiving emails with full context.
Chaport to PublicaWith Publica, you can sell, share and consume all kinds of digital content directly through a reliable and...
Chaport to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into DocsBot AI
HubSpot to DocsBot AIHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to DocsBot AISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to DocsBot AISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to DocsBot AIGoogle Sheets
Gmail to DocsBot AIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to DocsBot AIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Chaport and DocsBot AI, answered
What can start an automation from Chaport?
Any of Chaport's 8 triggers in the catalog, including Chat Stage Updated (instant), New Chat Started, New Message Sent (instant) and New Visitor (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in DocsBot AI when something happens in Chaport?
Any of DocsBot AI's 13 actions, including Create Web Source, Update bot, Add bot and Add lead. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DocsBot AI to Chaport?
DocsBot AI has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads DocsBot AI's API documentation and adds it.
Do I have to build a connector for Chaport or DocsBot AI?
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 Chaport and DocsBot AI 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.