Integration
Connect Fluent Support to Support Board
When New Customer fires in Fluent Support, your agent runs Send Message in Support Board. 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 Support Board 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 Support Board
When New Customer in Fluent Support
then Send Message in Support Board
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 Support Board
Triggers and actions 2 triggers · 46 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 Conversation
Creates a new conversation.
- Add Note
Adds a new note to a conversation.
- Add User
Create a new user in Support Board.
- Delete Message
Deletes an existing message.
- Delete Note
Deletes a note from a conversation.
- Delete User
Deletes a user and all linked conversations and messages.
- Delete Users
Deletes multiple users and all linked conversations and messages.
- Direct Message
Sends a direct chat message.
- Get Agents in Conversation
Returns an array with all the agents with at least one message in the conversation.
- Get Conversation
Returns a conversation and the messages of the conversation.
- Get Conversations
Returns all the conversations. Each conversation includes the last message of the conversation.
- Get External Setting
Returns an external setting. External settings are saved on a dedicated database row.
- Get Last Agent in Conversation
Returns the last agent who answered a conversation.
- Get Last Message
Returns the last message in a conversation.
- Get Multi Setting
Returns a subsetting of another setting.
- Get New Conversations
Returns the conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation.
- Get New Messages
Returns the messages of a conversation created after the given date/ID.
- Get New User Conversations
Returns the user conversations created after the given date/ID or with a message created after the given date/ID. Each conversation includes the last message of the conversation.
- Get Notes
Returns the internal notes of a conversation.
- Get Setting
Returns a setting saved in the Settings area.
- Get Settings
Returns an array with all the settings.
- Get User
Returns one user's details (name, email, type, extra details) by user ID via api.php function=get-user; returns false when the user does not exist.
- Get User Conversations
Returns the conversations of a user. Each conversation includes the last message of the conversation.
- Google Translate
Translates multiple strings via Google Translate.
- Login
Logins a user or agent. A user can log in in two ways: via email and password, or via user ID and token. The last value of the response is the encrypted login data ready to be stored in the sb-login cookie. Use the function SBF.loginCookie(response[1]); to store it. Returns false if login is unsuccessful.
- Push Notification
Sends a Push notification to an agent, a group of agents, or all agents. Push notifications must be enabled in the settings area.
- Search Conversations
Returns the conversations matching the search.
- Search User Conversations
Returns the conversations of the given user ID that matches the search terms.
- Send Message
Adds a new message to an existing conversation.
- Telegram Send Message
Sends a message to Telegram.
- Update Conversation Agent
Assigns or update the agent assigned to a conversation.
- Update Conversation Department
Updates the department of a conversation.
- Update Conversation Status
Updates the status code of a conversation.
- Update Message
Updates an existing message.
- Update User
Updates the details of an existing user.
- WhatsApp Send Message
Sends a message to a WhatsApp number.
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 Support Board
Questions
Fluent Support and Support Board, 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 Support Board when something happens in Fluent Support?
Any of Support Board's 36 actions, including Send Message, Update Conversation Agent, Update Conversation Department and Update Conversation Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Support Board to Fluent Support?
Support Board has no triggers in the catalog today, so automations start in Fluent Support. If you need the other direction, ask: your agent reads Support Board's API documentation and adds it.
Do I have to build a connector for Fluent Support or Support Board?
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.