Make it in n8n. It still can’t post.
Your own workflows, on your own machine, making real videos. The node is open and so is the API behind it.
It makes. It does not post.
No node 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 node 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 node
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.
A format finishes a post
Everything it made for that post, 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.
Make from a format
Name a format you built, and it makes a post from it into your library. Nothing posts until you schedule it.
Add a picture from a link
A new product photo in Drive becomes a reference the next generation paints from.
Three things to build with it
| When | Then |
|---|---|
| A form is submitted | Mutator makes the clip, and the workflow waits for it before posting the link back. |
| A format finishes a post | Everything it made is written to your own database, with the format it came from. |
| A new blog post goes live | Its title becomes a prompt, and the clip waits in your library until you schedule it. |
Today
The node is written and not on npm yet. Everything above works now through n8n’s own HTTP and webhook blocks, against the same API. It is about ten minutes of setup.
The HTTP Request node
Generic credential, Header Auth, Authorization: Bearer your key. Everything the node will do, it does by calling the same endpoints.
The Webhook node
If your n8n is reachable, subscribe its production URL and get deliveries the moment they happen rather than on a schedule.
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 n8n, and endpoint by endpoint in the API documentation. Connecting an agent instead? There is an MCP server.
Try it before you wire it up.
Make a video in Mutator first, free. The API key your n8n steps need comes with any paid plan.