Integration
Connect Fluent Support to DocsBot AI
When New Customer fires in Fluent Support, your agent runs Add lead 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 Fluent Support and DocsBot AI to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Fluent Support can start in DocsBot AI
When New Customer in Fluent Support
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 Fluent Support and DocsBot AI
Triggers and actions 2 triggers · 23 actions
- New Customer
Triggers when a new customer is added in Fluent Support.
- New Ticket
Triggers when a new support ticket is created in Fluent Support.
- Add Tag to Ticket
Adds an existing tag to a Fluent Support ticket.
- Close Ticket
Closes a Fluent Support ticket.
- Create Customer
Creates a new customer in Fluent Support with their name, email, contact details and an optional note.
- Create Ticket
Creates a new support ticket in Fluent Support for an existing customer.
- Get Ticket
Returns a Fluent Support ticket with its customer, responses and details.
- List Customers
Returns the customers in your Fluent Support help desk, optionally filtered by a search term.
- List Tickets
Returns support tickets from Fluent Support, optionally matching a search term.
- Reopen Ticket
Reopens a closed Fluent Support ticket.
- Reply to Ticket
Adds an agent reply or internal note to a Fluent Support ticket, optionally closing the ticket.
- Update Ticket
Updates one property of a ticket — its priority, customer priority, assigned agent or product.
- Add bot
Creates a new DocsBot bot in a team, optionally copying sources from an existing bot.
- Add lead
Captures or updates a lead for a DocsBot conversation, merging the supplied contact details (email, name, company and so on) into the lead record.
- Add source
Creates a new training source (URL, sitemap, document, Q&A and more) on a DocsBot bot.
- 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.
- 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.
- Create Web Source
Adds a web-based training source (a page URL, sitemap, RSS feed or YouTube video) to a DocsBot bot and returns the created source.
- Delete bot
Permanently deletes a bot from a DocsBot team.
- Delete lead
Deletes one captured lead record from a DocsBot bot.
- Delete source
Deletes a training source from a DocsBot bot. The source may still appear in chat answers for a few minutes afterwards.
- Get bot
Returns one DocsBot bot with its settings, model, status and source counts.
- List bots
Returns the bots in a DocsBot team, optionally filtered by text or privacy and sorted.
- Semantic Search
Searches a bot's trained content and returns the most relevant source chunks for a natural-language query.
- Update bot
Updates 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 Fluent Support
Fluent Support to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Fluent Support to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Fluent Support to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Fluent Support to Google SheetsGoogle Sheets
Fluent Support to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Fluent Support to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into DocsBot AI
Questions
Fluent Support and DocsBot AI, answered
What can start an automation from Fluent Support?
Any of Fluent Support's 2 triggers in the catalog, including New Customer and New Ticket. 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 Fluent Support?
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 Fluent Support?
DocsBot AI has no triggers in the catalog today, so automations start in Fluent Support. 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 Fluent Support 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.
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.