Integration
Connect Wistia to Customer.io
When New media fires in Wistia, your agent runs List segments 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 Wistia 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)Wistia holds your videos and their engagement numbers; Customer.io holds the people you message. Joining them means a new upload or a new project in Wistia can set off work in both places: pull stats, tidy names or copy medias in Wistia, then read the segment list in Customer.io so you know which audience the video belongs in front of.
Example flows
What Wistia can start in Customer.io
When New media in Wistia
then List segments 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 Wistia and Customer.io
Triggers and actions 2 triggers · 16 actions
- New media
Triggers when a new media is uploaded to your Wistia account.
- New project
Triggers when a new project is created in your Wistia account.
- Copy media
Copy a media to a destination project.
- Copy project
Copy an existing project, including all of its medias.
- Create project
Create a new project in your Wistia account.
- Delete media
Delete a media by its hashed id.
- Delete project
Delete a project and all of its medias.
- Get account
Retrieve information about your Wistia account.
- Get media
Retrieve a single media by its hashed id.
- Get media customizations
Retrieve the player customizations (embed options) for a media.
- Get media stats
Retrieve aggregated engagement statistics for a media.
- Get project
Retrieve a single project by its hashed id, including its medias.
- List medias
List medias, optionally filtered by project, name, or type.
- List projects
List all projects in your Wistia account.
- Update media
Update a media's name or description.
- Update media customizations
Replace the player customizations (embed options) for a media. Provide a JSON object of customization keys.
- Update project
Update an existing project's attributes.
- List segments
List all manual and data-driven segments in the workspace.
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 Wistia
Wistia to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Wistia to PandaDocPandaDoc helps you build and deliver sales quotes and proposals and track presentations and close deals...
Wistia to AnthropicAnthropic builds Claude, a family of large language models.
Wistia to PushoverPushover sends real-time push notifications to your phone, tablet, desktop, and watch.
Wistia to IP2LocationIP geolocation and intelligence. Look up location, network, proxy, and security data for any IP address...
Wistia to WufooWufoo is an easy way to build and manage online HTML forms and collect entries.
More into Customer.io
HubSpot to Customer.ioHubSpot is your all-in-one stop for all of your marketing software needs.
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
Gmail to Customer.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Customer.ioGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Wistia and Customer.io, answered
Can a message sent in Customer.io start one of these runs?
No. Customer.io has no triggers on this connection, so every run begins in Wistia with a new media or a new project. Once it starts, the agent can read the segments in your Customer.io workspace as part of the run.
What can the agent do inside Wistia before it touches Customer.io?
It can get a media, read its stats or player customizations, update a name or description, copy medias between projects, and create or update projects. The agent tests every scenario you describe before it keeps the run going.
What can start an automation from Wistia?
Any of Wistia's 2 triggers in the catalog, including New media and New project. 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 Wistia?
Any of Customer.io's 1 action, including List segments. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Customer.io to Wistia?
Customer.io has no triggers in the catalog today, so automations start in Wistia. 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 Wistia 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 Wistia 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.