Integration
Connect Vitally to Flodesk
When Customer Created fires in Vitally, 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 Vitally 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 Vitally can start in Flodesk
When Customer Created in Vitally
then Find a Subscriber by Email Address 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 Vitally and Flodesk
Triggers and actions 8 triggers ยท 34 actions
- Customer Created
Triggers when a new account (customer) is created in Vitally.
- Custom Object Instance Created
Triggers when a new instance of a custom object is created.
- Custom Object Instance Updated
Triggers when an instance of a custom object is created or updated.
- Note Created
Triggers when a new note is created in Vitally.
- NPS Response Created
Triggers when a new NPS response is recorded in Vitally.
- Organization Created
Triggers when a new organization is created in Vitally.
- Project Created
Triggers when a new project is created in Vitally.
- Task Created
Triggers when a new task is created in Vitally.
- Create Account
Creates an account (customer) in Vitally, identified by your own external ID.
- Create Note
Creates a note on an account or organization in Vitally.
- Create NPS Response
Records an NPS survey response from a user in Vitally.
- Create Organization
Creates an organization in Vitally, identified by your own external ID.
- Create Project From Template
Creates a project for an account or organization from a project template.
- Create Task
Creates a task on an account or organization in Vitally.
- Find a Customer
Returns a account by its Vitally ID or external ID.
- Find a Custom Object Instance
Finds a custom object instance by ID, external ID, linked account or a custom field value.
- Find a Note
Returns a note by its Vitally ID or external ID.
- Find a Organization
Returns a organization by its Vitally ID or external ID.
- Find a Task
Returns a task by its Vitally ID or external ID.
- Find a Teammate
Finds a Vitally team member by email address.
- Find a User
Finds a user by email address, external ID or email domain.
- Get Account Health Scores
Returns an account's health score and its breakdown.
- Update Customer Traits
Updates the name or traits of a account in Vitally; traits are merged with existing ones.
- Update Organization Traits
Updates the name or traits of a organization in Vitally; traits are merged with existing ones.
- Update Project Status
Changes a project's status in Vitally.
- Update Task
Updates a task in Vitally, for example to reassign or complete it.
- Update User Traits
Updates the name or traits of a user in Vitally; traits are merged with existing ones.
- Add custom field
Creates a new subscriber custom field in your Flodesk account with the label you choose.
- Add Existing Subscriber to Segment
Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.
- Add Existing Subscriber to Workflow
Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.
- Add segment
Creates a new segment in your Flodesk account and returns it.
- Create/Update Subscriber
Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.
- Find a Subscriber by Email Address
Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.
- Get segment
Returns a single Flodesk segment, including its name, color, type and number of active subscribers.
- List campaigns
Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term.
- List custom fields
Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label.
- List segments
Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.
- List subscribers
Returns subscribers in your Flodesk account, optionally filtered by status or segment.
- List workflows
Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).
- Remove Existing Subscriber From Segment
Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber.
- Remove Existing Subscriber From Workflow
Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.
- Unsubscribe Subscriber
Unsubscribes 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 Vitally
Vitally to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Vitally to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Vitally to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Vitally to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Vitally to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Vitally to AnthropicAnthropic builds Claude, a family of large language models.
More into Flodesk
CampaignHQ to FlodeskCampaignHQ is your affordable email marketing partner. Email marketing done right.
EasyCSV to FlodeskEasyCSV enables your users or team members to import CSV files and Google Sheets into your app or any public...
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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Questions
Vitally and Flodesk, answered
What can start an automation from Vitally?
Any of Vitally's 8 triggers in the catalog, including Customer Created, Custom Object Instance Created, Custom Object Instance Updated and Note Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Flodesk when something happens in Vitally?
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 Vitally?
Flodesk has no triggers in the catalog today, so automations start in Vitally. 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 Vitally 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 Vitally 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.