n8n IntegrationCreate integration

Generate videos inside your own n8n stack.

Install 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.

  • Verified, self-hosted-first install — add n8n-nodes-ngram from the Nodes panel - works on your own self-hosted n8n or n8n Cloud, no vendor in the path
  • Six capabilities cover the full lifecycle — Create Video, Create From Text, Create From URL, video.completed, video.failed and Get Status
  • HMAC-SHA256 signed callbacks — every push is signed with your account secret in the X-Ngram-Signature header
n8n hero preview
How it works

Four steps from install to first render.

Install the verified node from the Nodes panel - or from the n8n.io listing - on self-hosted n8n or n8n Cloud. Activate the workflow when you want its webhook subscription, then deactivate it when you are done.

01

Create an API key

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.

Setup
02

Install the community package

Click + 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.

Configure
03

Wire the node into a workflow

Drop a create, status, or terminal-event node onto the canvas, pick the ngram credential, and connect upstream and downstream nodes.

Build
04

Activate 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.

Open
What it can do

One community node, the full ngram lifecycle.

The node covers creation, status, and the two terminal event paths while running in n8n Cloud or your own n8n instance.

Cover the full render lifecycle

The package covers Create Video, Create From Text, Create From URL, Get Status, and the video.completed and video.failed terminal events.

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 - or n8n Cloud

Install n8n-nodes-ngram from the Nodes panel in self-hosted n8n, or use the same verified node on n8n Cloud. No vendor lock-in, no SaaS account hops required for self-hosted teams.

React to terminal events

The video.completed and video.failed events fire when a video reaches a terminal state, so the workflow can continue without a polling loop.

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 the video.failed event into a Slack or PagerDuty node. The full error_code and error_message land in the payload, ready to route.

Route one render downstream

Use a terminal event to branch into the downstream steps your team needs after a render completes.

Trigger sources

Eight 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.

HubSpot trigger
deal stage change
Salesforce trigger
record updated
Typeform / Tally
form submission
Generic webhook
any HTTPS event
Cron schedule
weekly digests
Slack trigger
slash command
Linear / Jira
issue closed
GitHub trigger
release published
Built for teams

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.

All solutions
How it compares

When the n8n node is the right tool, and when it isn't.

n8n 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 it runsYour own container or n8n CloudZapier's managed cloudInside your application codeHosted MCP endpoint
Install pathNodes panel - verified, one-clickTwo-click connect in Zapier UIAdd the SDK to your codebaseAdd the remote server in the MCP client
Lifecycle coverageCreate, Create From Text, Create From URL, On Ready, On Failed, StatusCreate, On Ready, On Failed, StatusFull REST surfaceTyped video, image, account, and catalog tools
Webhook signingHMAC-SHA256, your secretZapier-managed signingHMAC-SHA256, your secretAuthenticated tool requests
Orphan trigger cleanupAuto-reconciled on (de)activateManaged by ZapierYou manage subscriptionsClient manages the connection
Best forSelf-hosted, privacy-sensitive teamsMarketing and RevOps teamsEmbedding ngram in your productAgent-driven video workflows
Setup timeDepends on setupDepends on the workflowDepends on engineeringDepends on the MCP client

FAQ

Common questions about the n8n node

Click + in the Nodes panel and search Ngram. It's a verified community node, so it's discoverable directly on both self-hosted n8n and n8n Cloud - an instance owner approves it once, and anyone on the instance can use it after that. See the ngram docs for the full walkthrough.

Still curious? Still curious? Chat with us

n8n Integration

Install once. Render forever.

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.