Make it in Zapier. It still can’t post.
A row in a sheet becomes a video. The video lands wherever you keep videos. Nothing goes out until you say so.
It makes. It does not post.
No action here publishes anything, and that is not a permission you can grant: there is no endpoint behind one. A post exists once you have put a file in an account’s schedule, in Mutator, and your name is on that.
It costs credits, and says so first
Asking for a video spends what a video costs. Every action that writes takes an idempotency key, so a retry after a timeout is the same request rather than a second video.
What starts a trigger
A video or picture is made
Mutator finishes something and it passes the content check. Put it in Drive, a sheet, a channel, a client folder.
An automation run finishes
Everything that run made, in one go, whether it worked or not.
A generation finishes
The thing you asked for is ready, or it failed and says why.
What it can do
Ask for a video or picture
A row, a form, a message becomes a prompt. It answers at once with an id and the work happens on the queue.
Start an automation
Run one you already built. It makes what the automation says.
Add a picture from a link
A new product photo in Drive becomes a reference the next generation paints from.
Three people already do this
| When | Then |
|---|---|
| A row is added to a sheet | Mutator makes the video, and a link to it goes back in the row. |
| Mutator finishes a video | It lands in the client's Drive folder and Slack says so. |
| A product photo is added to Drive | It becomes a reference in Mutator, ready for the next shot. |
Today
The Mutator app is written and not in the directory yet. Everything above works now through Zapier’s own HTTP and webhook blocks, against the same API. It is about ten minutes of setup.
Webhooks by Zapier, as the trigger
Catch Hook gives you a URL. Subscribe it once with the command below and Mutator posts to it the moment something is made.
Webhooks by Zapier, as the action
Custom Request, POST, your key in the Authorization header. Every endpoint is in the documentation.
curl -X POST https://mutator.app/api/v1/hooks
-H "Authorization: Bearer loop_sk_..."
-H "content-type: application/json"
-d '{"event": "media.created", "targetUrl": "YOUR_WEBHOOK_URL"}'Your key is in Mutator under Settings, API keys, and comes with any paid plan. The whole surface is written up for Zapier, and endpoint by endpoint in the API documentation. Connecting an agent instead? There is an MCP server.