Integration
Connect Chaport to Flodesk
When Chat Stage Updated (instant) fires in Chaport, your agent runs Find a Subscriber by Email Address in Flodesk. 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 Flodesk 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 Flodesk
When Chat Stage Updated (instant) in Chaport
then Find a Subscriber by Email Address in Flodesk
When New Chat Started in Chaport
then Add custom field in Flodesk
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 Flodesk
Triggers and actions 8 triggers · 27 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 custom fieldCreates a new subscriber custom field in your Flodesk account with the label you choose.
Action
Add Existing Subscriber to SegmentAdds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.
Action
Add Existing Subscriber to WorkflowAdds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.
Action
Add segmentCreates a new segment in your Flodesk account and returns it.
Action
Create/Update SubscriberCreates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.
Action
Find a Subscriber by Email AddressLooks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.
Action
Get segmentReturns a single Flodesk segment, including its name, color, type and number of active subscribers.
Action
List campaignsReturns the email campaigns in your Flodesk account, optionally filtered by status or a search term.
Action
List custom fieldsReturns every subscriber custom field defined in your Flodesk account, with each field's key and display label.
Action
List segmentsReturns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.
Action
List subscribersReturns subscribers in your Flodesk account, optionally filtered by status or segment.
Action
List workflowsReturns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).
Action
Remove Existing Subscriber From SegmentRemoves an existing Flodesk subscriber from one or more segments and returns the updated subscriber.
Action
Remove Existing Subscriber From WorkflowRemoves an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.
Action
Unsubscribe SubscriberUnsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.
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 Flodesk
HubSpot to FlodeskHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to FlodeskSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to FlodeskSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to FlodeskGoogle Sheets
Gmail to FlodeskGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to FlodeskGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Chaport and Flodesk, 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 Flodesk when something happens in Chaport?
Any of Flodesk's 15 actions, including Create/Update Subscriber, Add custom field, Add Existing Subscriber to Segment and Add Existing Subscriber to Workflow. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Flodesk to Chaport?
Flodesk has no triggers in the catalog today, so automations start in Chaport. If you need the other direction, ask: your agent reads Flodesk's API documentation and adds it.
Do I have to build a connector for Chaport or Flodesk?
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 Flodesk 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.