Generate videos inside your own n8n stack.
Install the ngram community node via one docker exec. Drop Create Video, On Video Ready, On Video Failed and Get Status into any workflow. Renders run against ngram - everything else stays in your container.
- Self-hosted-first install — one docker exec from npm into your own n8n container - no vendor in the path
- Four nodes cover the full lifecycle — Create Video, On Video Ready, On Video Failed and Get Status - parity with the Zapier and Make modules
- HMAC-SHA256 signed callbacks — every push is signed with your account secret in the X-Ngram-Signature header
Four steps from npm install to first render.
The node ships as an npm package you install into your own n8n container. Activation registers the hook subscription; deactivation tears it down. No manual webhook plumbing.
Create your ngram key
Open Settings then API Keys in ngram and create a new key. It starts with ngs_. Paste it into n8n credentials, set the auth header to Bearer.
30 secInstall the community package
Run docker exec against your n8n container: cd /home/node/.n8n/nodes && npm install --ignore-scripts n8n-nodes-ngram@beta. Restart n8n. Once promoted, install via Settings then Community Nodes.
2 minWire the node into a workflow
Drop Create Video or On Video Ready onto the canvas, pick the ngram credential, and connect upstream and downstream nodes. n8n handles the rest.
1 minActivate and watch it reconcile
Hit Active. n8n calls our subscribe endpoint and registers the hook URL. Deactivate later and the subscription is torn down - no orphans across redeploys.
1 clickOne community node, the full ngram lifecycle.
The same surface area as the Zapier and Make modules - just running inside your own infrastructure.
Cover the full render lifecycle
Four nodes - Create Video, On Video Ready, On Video Failed, Get Status - cover trigger, success, failure and polling paths in one community package.
Never leak orphan triggers
Activation reuses existing hook subscriptions; deactivation tears them down. Redeploys don't pile up stale endpoints on the ngram side.
Run it in your own container
One docker-exec install from npm into your self-hosted n8n. No vendor lock-in, no SaaS account hops. Works on n8n Cloud after Creator Portal verification.
React the instant a render lands
On Video Ready and On Video Failed fire the moment a video reaches a terminal state. No polling loops, no cron scheduling, no wasted compute.
Block hostile hook targets
Hook destinations must resolve to a public address. RFC1918, localhost and link-local ranges are rejected at subscribe time.
Verify every push you receive
Each delivery includes an HMAC-SHA256 header keyed on your secret. The trigger preserves the raw request body in _raw so you can recompute and verify.
Wire failures into Slack or PagerDuty
Chain On Video Failed straight into a Slack or PagerDuty node. The full error_code and error_message land in the payload, ready to route.
Fan out one render to many channels
On Video Ready, branch into LinkedIn, X, YouTube, Notion and your CMS in one workflow. One render, every channel, no glue scripts.
Four workflows that get easier with the community node.
CRM-triggered videos. Per record, per stage.
Watch new HubSpot or Salesforce records in n8n, fire Create Video, and write the rendered URL back onto the contact or deal. The whole loop runs without a human in the path.
See the sales prospecting playbookForm submissions become personalized videos.
Pipe Typeform, Tally or any form webhook into n8n. Render a personalized clip per submission using the requester's inputs and ship it back via email or DM.
See the customer onboarding playbookSlack alerts on every successful render.
Chain On Video Ready and On Video Failed into Slack nodes. The right channel hears about completed renders and failures the instant they happen, no polling.
See the internal communication playbookScheduled weekly report videos.
Use n8n's cron node to render a weekly metrics video on a fixed schedule, then route it to email or shared drives. The team gets a watchable update without anyone editing one.
See the changelog video playbookEight upstream nodes the ngram node loves to sit downstream of.
The ngram node is happiest at the end of an n8n chain. Anything n8n can watch - CRM events, form webhooks, cron, queues, databases - can fire a render. These are the upstream patterns we see most.
What ngram does when the n8n node fires.
Every render goes through the same ngram pipeline. Here is what runs inside it once Create Video hits the API.
AI Visuals
Scene-matched graphics in 30+ styles, generated per render request from the input payload.
Explore featureAI Voiceover
40+ voices in 20 languages, auto-synced to the script the workflow sends.
See featureScript Generation
Scripts written from the source content the n8n node passes in - blog text, CRM notes, form answers.
See featureMusic
Licensed tracks, auto-ducked under voice. Selectable from the node config.
See featureMotion Graphics
Auto-animated text, transitions and charts. The workflow ships the data; ngram animates it.
See featureCaptions
Burned-in or .srt captions, frame-accurate and editable. Toggle per render.
See featureBrand Kit
Logo, colors, fonts and intros applied on every export, scoped per workspace.
See featureMulti-format Export
Every platform ratio from one render call - 16:9, 9:16, 1:1, 4:5.
See featureTranslation
Render the same source in multiple languages by passing a locale array to the node.
See featureEnterprise Integrations
n8n is one of many triggers - Zapier, Make, MCP, LinkedIn, X and YouTube ship in the same workspace.
See featureEvery n8n trigger is a converter input.
n8n webhooks, cron nodes and HTTP requests deliver source content in formats these converters already understand. Drop the field into the Create node and ship.
URL to Video
The most common n8n payload is a URL - product page, release note, landing page. Hand it to the converter that powers the extension.
Convert from URLText to Video
Webhook bodies, form submissions, internal updates - feed the text straight into a storyboarded video.
Convert textDocs to Video
Internal doc sites, Confluence, Notion - pipe the structured doc through the docs converter for an on-prem walkthrough.
Convert docsPolish, translate or re-cut what n8n renders.
After the workflow hands off, every ngram tool can run on the output - either from the editor or via further API calls from inside the same n8n graph.
Who runs ngram through n8n.
Teams that already host their own n8n graph reach for the community node first. It keeps the automation surface they trust and adds video rendering to it.
Already running n8n on your own infra. Install the ngram node and keep video creation under your roof - no new SaaS account, no new vendor.
Trigger a render when a release lands or a doc updates. The community node sits alongside the GitHub and Linear triggers your team already wires.
Wire ngram into the same n8n graph that runs your other internal automations. One canvas for forms, CRM events, scheduled jobs and now video.
Trigger ngram from your product backend via n8n. No new pipeline to maintain - reuse the queue, retry and observability you already trust.
Stay on-prem. ngram pushes events to your hook URL with HMAC-SHA256 signatures; the rest of the workflow never leaves your infrastructure.
Watch HubSpot deal-stage changes, render a personalized clip and write the URL back onto the deal - all on the n8n graph your RevOps team already maintains.
The n8n node is one trigger. Here are the others.
Same rendering engine, different triggers. Pick the one that fits your stack - a click, a managed Zap, a visual scenario, an agent tool call or a publish destination.
Chrome ExtensioncreatePin ngram to your Chrome toolbar. Click the icon on any blog, release note or doc and get a publish-ready video back in the same tab.
Explore Chrome Extension integration
ZapiercreateThe managed-cloud counterpart. Wire ngram into 6,000+ apps when you don't want to host the workflow runner yourself.
Explore Zapier integration
Make.comcreateVisual scenario builder for branching workflows with loops, filters and error paths around every render call. Managed cloud, no container.
Explore Make.com integration
MCP ServercreateClaude, ChatGPT and other MCP-aware agents call the rendering tool directly inside a conversation - no workflow runner needed.
Explore MCP Server integration
LinkedInpublishSchedule the finished video straight to a company or personal LinkedIn page from inside the ngram editor.
Explore LinkedIn integration
X (Twitter)publishPost finished videos to X with copy, captions and the right aspect ratio attached for the platform.
Explore X (Twitter) integration
YouTubepublishUpload with title, description, chapters and tags pre-filled from the source content that triggered the render.
Explore YouTube integrationWhen the n8n node is the right tool, and when it isn't.
n8n is the self-hosted-first option. Zapier and Make are managed clouds. The REST API is the lowest level. Same render engine underneath.
ngram on n8n you are here | Zapier managed cloud | REST API for products | Make managed cloud | |
|---|---|---|---|---|
| Where it runs | Your own container, on-prem | Zapier's managed cloud | Inside your application code | Make's managed cloud |
| Install path | One docker exec from npm | Two-click connect in Zapier UI | Add the SDK to your codebase | Two-click connect in Make UI |
| Lifecycle coverage | Create, On Ready, On Failed, Status | Create, On Ready, On Failed, Status | Full REST surface | Create, On Ready, On Failed, Status |
| Webhook signing | HMAC-SHA256, your secret | Zapier-managed signing | HMAC-SHA256, your secret | Make-managed signing |
| Orphan trigger cleanup | Auto-reconciled on (de)activate | Managed by Zapier | You manage subscriptions | Managed by Make |
| Best for | Self-hosted, privacy-sensitive teams | Marketing and RevOps teams | Embedding ngram in your product | Visual branching workflows |
| Setup time | About 5 minutes | About 5 minutes per Zap | About 1 hour engineering | About 5 minutes per scenario |
FAQ
Common questions about the n8n node
Still curious? Still curious? Chat with us
Install once. Render forever.
Add the ngram community node to your self-hosted n8n and turn any workflow into a video pipeline - signed, reconciled, on your own infrastructure.