Integration
Connect Vitally to Customer.io
When Customer Created fires in Vitally, your agent runs Send transactional email in Customer.io. 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 Customer.io 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 Customer.io
When Customer Created in Vitally
then Send transactional email in Customer.io
When Custom Object Instance Created in Vitally
then Create Anonymous Event in Customer.io
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 Customer.io
Triggers and actions 8 triggers · 29 actions
Trigger
Customer CreatedTriggers when a new account (customer) is created in Vitally.
Trigger
Custom Object Instance CreatedTriggers when a new instance of a custom object is created.
Trigger
Custom Object Instance UpdatedTriggers when an instance of a custom object is created or updated.
Trigger
Note CreatedTriggers when a new note is created in Vitally.
Trigger
NPS Response CreatedTriggers when a new NPS response is recorded in Vitally.
Trigger
Organization CreatedTriggers when a new organization is created in Vitally.
Trigger
Project CreatedTriggers when a new project is created in Vitally.
Trigger
Task CreatedTriggers when a new task is created in Vitally.
Action
Create AccountCreates an account (customer) in Vitally, identified by your own external ID.
Action
Create NoteCreates a note on an account or organization in Vitally.
Action
Create NPS ResponseRecords an NPS survey response from a user in Vitally.
Action
Create OrganizationCreates an organization in Vitally, identified by your own external ID.
Action
Create Project From TemplateCreates a project for an account or organization from a project template.
Action
Create TaskCreates a task on an account or organization in Vitally.
Action
Find a CustomerReturns a account by its Vitally ID or external ID.
Action
Find a Custom Object InstanceFinds a custom object instance by ID, external ID, linked account or a custom field value.
Action
Find a NoteReturns a note by its Vitally ID or external ID.
Action
Find a OrganizationReturns a organization by its Vitally ID or external ID.
Action
Find a TaskReturns a task by its Vitally ID or external ID.
Action
Find a TeammateFinds a Vitally team member by email address.
Action
Find a UserFinds a user by email address, external ID or email domain.
Action
Get Account Health ScoresReturns an account's health score and its breakdown.
Action
Update Customer TraitsUpdates the name or traits of a account in Vitally; traits are merged with existing ones.
Action
Update Organization TraitsUpdates the name or traits of a organization in Vitally; traits are merged with existing ones.
Action
Update Project StatusChanges a project's status in Vitally.
Action
Update TaskUpdates a task in Vitally, for example to reassign or complete it.
Action
Update User TraitsUpdates the name or traits of a user in Vitally; traits are merged with existing ones.
Action
Create Anonymous EventRecords an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later.
Action
Create EventRecords an event for a person in Customer.io, which can trigger campaigns or update segments.
Action
Delete personDeletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
Action
Get personLook up a customer's attributes by customer_id.
Action
List segmentsList all manual and data-driven segments in the workspace.
Action
Merge peopleMerges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted.
Action
Remove people from segmentRemoves people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
Action
Send API-triggered broadcastTrigger an API-triggered broadcast campaign to send immediately.
Action
Send transactional emailSend a one-off transactional email via a transactional message template.
Action
Suppress personDeletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted.
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 Customer.io
HubSpot to Customer.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Wistia to Customer.ioWistia makes it easy to host, track, and measure video engagement online.
Salesforce to Customer.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Customer.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Customer.ioGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Customer.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Vitally and Customer.io, 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 Customer.io when something happens in Vitally?
Any of Customer.io's 10 actions, including Create Anonymous Event, Create Event, Send API-triggered broadcast and Send transactional email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Customer.io to Vitally?
Customer.io has no triggers in the catalog today, so automations start in Vitally. If you need the other direction, ask: your agent reads Customer.io's API documentation and adds it.
Do I have to build a connector for Vitally or Customer.io?
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 Customer.io 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.