A training draft for a reviewer
This HBase lesson combines instructor footage with labels and diagrams. For a recurring training workflow, send the draft to an instructor who can check the technical details.
API-key video creation requires a paid plan and enough credits. Supported connected-app sign-ins have separate access rules.
Check integration accessInstall the ngram community node - verified by n8n - from the Nodes panel in self-hosted n8n or n8n Cloud. Create videos, check status, and react to the exact video.completed or video.failed webhook events in your workflow.
This HBase lesson combines instructor footage with labels and diagrams. For a recurring training workflow, send the draft to an instructor who can check the technical details.
This fictional quarterly update shows 100 completions followed by 120. An n8n workflow could read the approved totals, request the explanation and route the draft to the person who owns the report.
One customer needs help with an onboarding checklist. Use the ticket identifier to return a draft like this to the correct account owner, who can check the instructions before sharing it.
The illustrated workflow shows how a webhook can supply a prompt and retrieve status. Install the verified node, then test the success and failure paths before activating the workflow.
Every signed-in user can create a bearer key from Settings, then save it in the n8n credential form. Keep the key in n8n's credential store rather than a workflow field.
SetupClick + in the Nodes panel and search Ngram - it's a verified community node, so it's discoverable directly on self-hosted n8n and n8n Cloud. An instance owner approves it once; after that anyone on the instance can add it. See the docs for the full walkthrough.
ConfigureDrop a create, status, or terminal-event node onto the canvas, pick the ngram credential, and connect upstream and downstream nodes.
BuildHit Active. n8n calls our subscribe endpoint and registers the hook URL. Deactivate later and the subscription is torn down - no orphans across redeploys.
OpenThe node covers creation, status, and the two terminal event paths while running in n8n Cloud or your own n8n instance.
The package covers Create Video, Create From Text, Create From URL, Get Status, and the video.completed and video.failed terminal events.
Activation reuses existing hook subscriptions; deactivation tears them down. Redeploys don't pile up stale endpoints on the ngram side.
Use the verified node on your self-hosted n8n instance or n8n Cloud. Connect your ngram account to send video requests and receive the generated result.
The video.completed and video.failed events fire when a video reaches a terminal state, so the workflow can continue without a polling loop.
Hook destinations must resolve to a public address. RFC1918, localhost and link-local ranges are rejected at subscribe time.
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.
Chain the video.failed event into a Slack or PagerDuty node. The full error_code and error_message land in the payload, ready to route.
Choose the model, style, duration, aspect ratio, voice, narration language, energy, mood, Brand Kit and format on the Create node. Dropdowns load ngram's current options, Model shows each model's credits per second, Brand Kit reflects your account, and an expression can set any duration of at least 1 second.
Use n8n when your team owns conditional routing, retries or a self-hosted workflow. Send just the source fields the video needs. For a one-off draft, make the video directly in ngram.
Filter for the chosen stage before calling ngram. Keep the source record ID with the returned video ID so that the completed result reaches the correct account owner.
See the sales prospecting playbookCheck that a form contains the audience, action and approved source. Send incomplete submissions to an owner for clarification before spending credits.
See the customer onboarding playbookUse the completed event to notify the reviewer and the failed event to alert the workflow owner. Include the video ID in either message so the owner can investigate.
See the internal communication playbookStart with a scheduled check for approved changes to the training instructions. Skip the create step when the instructions are unchanged. Send a new draft to the person who teaches the task.
See the changelog video playbookThe 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.
Every render goes through the same ngram pipeline. Here is what runs inside it once Create Video hits the API.
Scene-matched graphics in 30+ styles, generated per render request from the input payload.
Explore featureA choice of voices in multiple languages, auto-synced to the script the workflow sends.
See featureScripts written from the source content the n8n node passes in - blog text, CRM notes, form answers.
See featurengram selects background music from its hosted library to match the video's tone and pacing. In Edit > Music, you can browse, swap, and adjust the track volume.
See featureAuto-animated text, transitions and charts. The workflow ships the data; ngram animates it.
See featureBurned-in or .srt captions, frame-accurate and editable. Toggle per render.
See featureChoose a Brand Kit on the Create node to apply its logo, colors and fonts to the video.
See featureShare workspace projects, assets, and conversations with teammates before the finished video moves through this integration.
See featureSet Narration Language on the Create node, and run one item per language when the same source needs several language versions.
See featuren8n webhooks, cron nodes and HTTP requests deliver source content in formats these converters already understand. Drop the field into the Create node and ship.
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 URLWebhook bodies, form submissions, internal updates - feed the text straight into a storyboarded video.
Convert textPass the document text your workflow is authorized to access into a request to hosted ngram. Include the audience and the explanation you want.
Convert docsAfter generation, open the result in ngram to make further edits. Use the documented API and node actions for the steps you want to automate.
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.
Keep orchestration in the n8n instance you already run. Connect the verified node to your ngram account for hosted video generation.
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.
Choose which source fields your workflow sends to ngram, and verify signed callbacks before continuing to downstream steps.
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.
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.
Pin 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 integrationThe managed-cloud counterpart. Wire ngram into 6,000+ apps when you don't want to host the workflow runner yourself.
Explore Zapier integrationMake.com is marked Coming Soon in Studio. Check its status before replacing this n8n workflow with a Make scenario.
See Make.com statusClaude, ChatGPT and other MCP-aware agents call the rendering tool directly inside a conversation - no workflow runner needed.
Explore MCP Server integrationCompose and publish a finished video to LinkedIn from its supported calendar workflow.
Explore LinkedIn integrationReview a finished video and its post copy before publishing it to X from the Social Publishing Beta.
Explore X (Twitter) integrationConnect YouTube to compose and publish a finished video from the content calendar.
Explore YouTube integrationn8n is the cloud-or-self-hosted workflow option. Zapier is managed automation, MCP serves agent clients, and the REST API serves application code.
ngram on n8n you are here | Zapier managed cloud | REST API for products | MCP Server agent clients | |
|---|---|---|---|---|
| Where the workflow connection runs | Your own container or n8n Cloud | Zapier's managed cloud | Inside your application code | Hosted MCP endpoint |
| Install path | Nodes panel - verified, one-click | Two-click connect in Zapier UI | Add the SDK to your codebase | Add the remote server in the MCP client |
| Lifecycle coverage | Create, Create From Text, Create From URL, On Ready, On Failed, Status | Create, On Ready, On Failed, Status | Full REST surface | Typed video, image, account, and catalog tools |
| Webhook signing | HMAC-SHA256, your secret | Zapier-managed signing | HMAC-SHA256, your secret | Authenticated tool requests |
| Orphan trigger cleanup | Auto-reconciled on (de)activate | Managed by Zapier | You manage subscriptions | Client manages the connection |
| Best for | Teams using n8n Cloud or their own workflow runner | Marketing and RevOps teams | Embedding ngram in your product | Agent-driven video workflows |
| Setup time | Depends on setup | Depends on the workflow | Depends on engineering | Depends on the MCP client |
FAQ
Still curious? Set up an editorial handoff
Add the verified ngram community node to self-hosted n8n or n8n Cloud and turn any workflow into a video pipeline - signed, reconciled, on your own terms.