Integration
Connect MySQL and Wistia
When New or Updated Row fires in MySQL, your agent runs Create project in Wistia, or New media in Wistia to Add Row in MySQL. 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 MySQL and Wistia 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)Connecting Wistia and MySQL lets your video library and your database describe the same thing. New uploads and projects in Wistia can be written into MySQL tables, and rows you add or change in MySQL can create projects or rename media in Wistia. The agent builds the whole flow, tests every scenario and keeps it running.
Example flows
What MySQL and Wistia can do together
From MySQL to Wistia
When New or Updated Row in MySQL
then Create project in Wistia
From Wistia to MySQL
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 MySQL and Wistia
Triggers and actions 6 triggers · 21 actions
- New or Updated Row
Triggers when a new row is added or modified.
- New or Updated Row (Custom Query)
Fires for each new or changed row returned by a SELECT statement you write against the connected MySQL database.
- New Row
Triggers when you add a new row.
- New Table
Fires when a new table appears in the connected MySQL database.
- Add Row
Adds a new row.
- Delete Row
Delete the rows in a table whose chosen column equals a value.
- Find Row
Finds a row in a table via a lookup column.
- Find Rows via Custom Query
Run an author-written SELECT against the connected MySQL database and return every row it produced. Mirrors PostgreSQL 715ae2ac, SQL Server 8e0bbb5d and Oracle 2c308e4d; MySQL placeholder style is ?.
- Find Row via Custom Query
Runs a SELECT statement you write against the connected MySQL database and returns the first row it matches.
- Update Row
Updates an existing row.
- 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.
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 MySQL
MySQL to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MySQL to MailchimpMailchimp marketing automation and email platform.
MySQL to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
MySQL to ActiveCampaignActiveCampaign is a marketing automation, email marketing, and CRM platform.
MySQL to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
MySQL to SendGridSendGrid by Twilio — email delivery and marketing platform.
More into Wistia
Stripe to WistiaStripe is a payment processing platform for online businesses.
Shopify to WistiaShopify is a commerce platform for online stores and retail point-of-sale.
Pipedrive to WistiaPipedrive is a sales CRM and pipeline management tool.
Questions
MySQL and Wistia, answered
Can I store Wistia engagement numbers in my own database?
Yes. When a new media is uploaded, the agent can retrieve that media's aggregated stats from Wistia and add or update a row in the MySQL table you choose. You pick which columns hold the media name, hashed id and stat fields.
What if the MySQL row a Wistia media belongs to is missing?
The agent can run a lookup in MySQL first, using Find Row or a SELECT you write, and only continue when a matching row comes back. It tests every scenario, including the one where nothing matches, before the automation goes live.
What can start an automation from MySQL?
Any of MySQL's 4 triggers in the catalog, including New or Updated Row, New or Updated Row (Custom Query), New Row and New Table. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wistia when something happens in MySQL?
Any of Wistia's 15 actions, including Create project, Get media stats, Update media and Update media customizations. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wistia to MySQL?
Yes. When something happens in Wistia, your agent can act in MySQL too. This page covers both directions: Wistia's triggers and MySQL's actions are listed here as well.
Do I have to build a connector for MySQL or Wistia?
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 MySQL and Wistia 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.