Make it in a scenario. It still can’t post.
Scenarios that make things. A trigger on one side, a real video on the other, and a person still choosing what goes out.
It makes. It does not post.
No module 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 module that writes takes an idempotency key, so a retry after a timeout is the same request rather than a second video.
What starts a instant 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 |
|---|---|
| An Airtable record is marked ready | Mutator makes the video and the record gets the link. |
| Mutator finishes a picture | It goes to the client's folder, and the scenario tells them it is there. |
| A shop adds a product | Its photo becomes a reference, and the first shot is waiting for you. |
Today
The Mutator app is written and not published yet. Everything above works now through Make’s own HTTP and webhook blocks, against the same API. It is about ten minutes of setup.
The Custom webhook module
It gives you a URL. Subscribe it once with the command below, and the scenario starts the moment Mutator finishes something.
The HTTP module
Make a request, POST, your key in the Authorization header. The documentation has every endpoint and what it answers.
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 Make, and endpoint by endpoint in the API documentation. Connecting an agent instead? There is an MCP server.