The video makes itself.
The flow sends it on.
Wire Reigniter into the tools your business already runs. A video finishes and posts itself, a spreadsheet row starts a render, a credit alert pages someone before a campaign stalls — built in the flow editor inside your dashboard, or driven from Zapier, n8n, Make or your own code.
Every flow ends somewhere concrete — a rendered video, a published post, a message in the channel your team reads.
Trigger, flow, done
Three steps between an event and a job nobody had to remember to do.
Pick a trigger
Something in Reigniter — a video finished, credits ran low, a new customer joined — or something outside it: a schedule, a form, a new row in your CRM.
Draw the flow
In the builder inside your dashboard, drag the steps between the two ends: filter, transform, call another app, start a render. It looks the way the flow actually runs.
Let it run
The flow keeps working when you are not: a finished video posts itself, a report mails itself, a render starts the moment your spreadsheet gains a row.
The two directions
The render tells the business it is done
The moment a video finishes — or fails — a signed webhook fires carrying the file. Post it to the social accounts you connected, drop it in the team Drive, ping Slack, update the campaign sheet. The event is the truth, retried if your endpoint stumbles.
A trigger starts the render
A scheduled flow, a new row, a form submission — any of them can call the render API with a key you hold. The brief goes in, the finished MP4 comes back into the same flow, and nobody opened the app at all.
Built like infrastructure, not a demo
Signed and retried
Every outbound event carries a signature and a stable delivery id — your side verifies it is really us and de-dupes retries. Four hundred-series answers stop resends; real failures retry with backoff.
Your accounts, your rules
Posting destinations are accounts you connected yourself — a flow can only go where you already can. Revoke a connection and every flow that used it stops cleanly.
No vendor lock-in
Webhooks and an API key are the whole contract. The built-in builder is the convenient path, not the only one — the same events feed any automation tool or a plain endpoint of your own.
Was zuerst gefragt wird
Two directions. Reigniter tells your tools when something happens — a render finished (with its URL), failed, or an account event fired. Or the reverse: a trigger in your stack calls our API and starts a render, with the finished file handed back when it is done.
No. The signed webhooks and the render API are plain HTTP — they drive Zapier, n8n, Make or your own endpoint exactly the same. The built-in builder is just the fastest way to draw the flow without leaving the app.
Connect your social accounts once under Publish, and a flow can take a finished render straight to them — or route it through your scheduler, your Drive, your Slack. The connections are yours; the flow just uses them.
Every event we send carries a signature your side can verify, retries are bounded, and inbound calls need an API key you can revoke. Failed deliveries give up rather than hammering your endpoint forever.
Put the pipeline on rails
Connect once, draw the flow, and let the renders run themselves. Free to start.
Kostenlos starten