Integration
Connect Wistia and Clerk
When New media fires in Wistia, your agent runs Create User in Clerk, or New User in Clerk to Create project in Wistia. 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 Clerk 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 Wistia and Clerk can do together
From Wistia to Clerk
When New media in Wistia
then Create User in Clerk
When New project in Wistia
then Update User in Clerk
From Clerk to Wistia
When New User in Clerk
then Create project in Wistia
When New User in Clerk
then Update project in Wistia
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 Clerk
Triggers and actions 3 triggers ยท 21 actions
Trigger
New mediaTriggers when a new media is uploaded to your Wistia account.
Trigger
New projectTriggers when a new project is created in your Wistia account.
Action
Copy mediaCopy a media to a destination project.
Action
Copy projectCopy an existing project, including all of its medias.
Action
Create projectCreate a new project in your Wistia account.
Action
Delete mediaDelete a media by its hashed id.
Action
Delete projectDelete a project and all of its medias.
Action
Get accountRetrieve information about your Wistia account.
Action
Get mediaRetrieve a single media by its hashed id.
Action
Get media customizationsRetrieve the player customizations (embed options) for a media.
Action
Get media statsRetrieve aggregated engagement statistics for a media.
Action
Get projectRetrieve a single project by its hashed id, including its medias.
Action
List mediasList medias, optionally filtered by project, name, or type.
Action
List projectsList all projects in your Wistia account.
Action
Update mediaUpdate a media's name or description.
Action
Update media customizationsReplace the player customizations (embed options) for a media. Provide a JSON object of customization keys.
Action
Update projectUpdate an existing project's attributes.
Trigger
New UserTriggers when a new user is created in Clerk.
Action
Ban UserBan a user, preventing them from signing in.
Action
Create InvitationInvite a new user to the Clerk instance by email; they receive a sign-up link.
Action
Create UserCreates a new user in Clerk.
Action
Delete UserDeletes a user from Clerk.
Action
Unban UserRemove a ban on a user, restoring their ability to sign in.
Action
Update UserUpdates an existing user in Clerk.
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 Customer.ioWith Customer.io you can send email, SMS, and push based on what people do or don't do in your app.
Wistia to IP2LocationIP geolocation and intelligence. Look up location, network, proxy, and security data for any IP address...
More into Clerk
Brevo to ClerkBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Instagram to ClerkInstagram is a social media platform for sharing photos, videos, and stories.
Kit to ClerkKit is an email marketing platform for professional bloggers.
Postman to ClerkPostman is a platform for building and testing APIs.
Telegram to ClerkTelegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.
HubSpot to ClerkHubSpot is your all-in-one stop for all of your marketing software needs.
Questions
Wistia and Clerk, answered
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 Clerk when something happens in Wistia?
Any of Clerk's 6 actions, including Create Invitation, Create User, Update User and Ban User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Clerk to Wistia?
Yes. When something happens in Clerk, your agent can act in Wistia too. This page covers both directions: Clerk's triggers and Wistia's actions are listed here as well.
Do I have to build a connector for Wistia or Clerk?
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 Clerk 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.