Wire ngram into 6,000+ Zapier apps.
Trigger a render from a connected Zapier app, then receive the exact video.completed or video.failed result and look up status in the workflow. The public ngram app ships with a Create action and a Get Status search step.
- Add the public ngram app — search Zapier's directory, connect with a self-service ngram API key, start building Zaps
- Trigger from any Zap — one Create Video action step, six-thousand-plus possible sources
- Push terminal results — video.completed and video.failed arrive when a render finishes or fails
Three steps from signup to a running Zap.
The ngram app is publicly listed in Zapier. Create a bearer key in ngram Settings, connect it in Zapier, then build the Zap the same way you build any other.
Create an API key
Every signed-in user can create a bearer key from Settings. Store it in Zapier's connection flow rather than a Zap field.
SetupAdd the ngram app to Zapier
Search ngram in Zapier's app directory and connect with the bearer key from ngram Settings. The app is publicly listed and needs no private Zapier invite.
ConnectBuild the Zap
Pick any of Zapier's 6,000-plus apps as the trigger, drop in Create Video, then route the finished video anywhere Zapier connects to.
Build6,000+ apps, one rendering engine inside every Zap.
The ngram render pipeline runs from Zapier's app surface. Trigger, look up, and route the result through steps your team already knows how to wire.
Fire a render from any Zap
Drop the Create Video action into a Zap. ngram returns a vid_ id that the next step can use for downstream branching.
Receive terminal results
ngram pushes video.completed or video.failed to Zapier when a render reaches a terminal state.
Look up any render mid-flow
The Get Status search returns status, progress and the final URL. Drop it anywhere in a Zap to gate downstream actions.
Branch on every failure
The video.failed event carries the failed render result so you can route it to the downstream step you choose.
Use account settings
Use the voice and style values available to your ngram account when configuring the Zap action.
Verify every delivery you receive
Each push carries an HMAC-SHA256 header keyed on your account secret. Validate the signature before trusting the body.
Four moments where a Zap quietly renders a video for you.
If Zapier listens to it, ngram renders from it. These are the patterns ops teams build most often.
CRM events to personalized intro video.
A HubSpot or Salesforce deal hits Demo Sent. Zapier fires Create Video with the contact's name and use case, then writes the rendered URL back to the deal record - all before the rep refreshes their pipeline.
See the sales prospecting playbookForm submissions to onboarding clip.
A new Typeform or Jotform submission lands. Zapier reads the requester's inputs, renders a tailored ngram welcome video, and emails it back inside the auto-responder thread.
See the customer onboarding playbookProduct launches to multi-channel video.
A new release lands in your changelog tool. Zapier picks it up, fires Create Video, then routes the finished MP4 to the downstream step your team chooses.
See the feature announcement playbookInbound webhooks to rendered explainer.
Catch any inbound webhook in Zapier - app event, scheduler tick, internal trigger - render a ngram explainer, and pipe the finished link back to whoever needs it next.
See the explainer video playbookThe Zap surface area ngram lives inside.
These are the most common Zapier app categories teams wire into ngram. Anything Zapier can listen to - that is 6,000+ apps - works as a trigger upstream of the Create Video step.
What ngram does inside every Zap-triggered render.
Every Create Video step runs through the same ngram pipeline. Here is what runs inside it.
AI Visuals
Scene-matched graphics in 30+ styles, generated from the Zap payload.
Explore featureAI Voiceover
40+ voices in 20 languages, auto-synced to the timeline.
See featureScript Generation
Scripts written from the structured fields the Zap passes in.
See featureVideo Editing
ngram 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 featureMotion Graphics
Auto-animated text, transitions and charts - no timeline needed.
See featureCaptions
Burned-in or .srt captions, frame-accurate and editable later.
See featureBrand Kit
Logo, colors, fonts and intros applied on every Zap-driven export.
See featureCollaboration
Anchored comments, version history and async review on every render.
See featureTranslation
Translate scripts, captions, on-screen text, and voiceover before the finished video moves through this integration.
See featureEvery Zap payload is a source the converter accepts.
Most Zapier triggers ship a URL, doc, page, or form payload. These converters absorb them as-is - point the Render Video action at the field and ngram does the rest.
URL to Video
Most Zaps pass a URL field - product page, release note, landing page. Pipe it straight into Render Video.
Convert from URLBlog to Video
When a new post hits your CMS Zapier trigger, send the URL to Blog to Video for a social cut.
Convert a blogText to Video
Form submissions, deal notes, internal updates - pipe the text field straight into a storyboarded render.
Convert textPolish, translate or re-cut what your Zap renders.
After the Zap hands off, every ngram tool can run on the output without leaving the editor.
Who wires Zapier into ngram.
Anyone who already runs Zaps for the rest of the business plugs ngram in next to them. Same tooling, one extra step.
Wire changelog updates and launch tags to Create Video, then route the finished MP4 to the downstream step your team chooses.
Trigger personalized intros from CRM stage changes. New deal at Demo Sent renders a tailored ngram clip back into the record.
Onboarding milestones in your CS tool fire a Zap that renders the right welcome or training video and emails it to the right contact.
New ticket tagged how-to in Zendesk or Intercom? Zapier fires Create Video and routes the rendered URL to the next support step.
GitHub release tags become a Zap that renders a release walkthrough and routes it to your DevRel workflow for review - no manual recording.
Pipe weekly metrics from Mixpanel or Stripe into a Zap that renders an investor update video, ready before Monday standup.
Linear status changes fire Zaps that render a changelog video for every release without a single hand-off to design.
Zapier is one trigger. Here are the others.
ngram is the same rendering engine behind every integration. Pick the trigger that fits the moment - a click, a webhook, a scenario branch, or an agent tool call.
Chrome ExtensioncreatePin ngram to your toolbar. Click the icon on any blog, doc or release note and get a publish-ready video without leaving the tab.
Explore Chrome Extension integration
n8ncreateSelf-hosted workflows that stay inside your network. Only the render API call leaves the container - the rest of the orchestration is yours.
Explore n8n integration
Make.comcreateMake.com is marked Coming Soon in Studio. Keep the Zap live until Make.com exposes an active setup action.
See Make.com status
MCP ServercreateClaude, ChatGPT and other MCP-aware agents call the rendering tool directly inside a conversation - no Zap required.
Explore MCP Server integration
LinkedInpublishCompose and publish a finished video to LinkedIn from its supported calendar workflow.
Explore LinkedIn integration
X (Twitter)publishCompose and publish a finished video to X from its supported calendar workflow.
Explore X (Twitter) integration
YouTubepublishConnect YouTube to compose and publish a finished video from the content calendar.
Explore YouTube integrationWhen Zapier is the right trigger, and when it isn't.
ngram + Zapier you are here | Chrome Ext. human click | n8n cloud or self-hosted | REST API for products | |
|---|---|---|---|---|
| Who triggers it | An automated event in any app | A human looking at a page | An automated n8n workflow | Your application code |
| App breadth | 6,000+ Zapier apps | Any HTTPS page | Built-in nodes plus HTTP | Whatever you wire up |
| Setup time | Depends on the Zap | Depends on the browser | Depends on the n8n deployment | Depends on the application |
| Best for | Always-on cross-app automation | Ad-hoc renders from web pages | Self-hosted or code-friendly workflows | Shipping ngram inside your product |
| Trigger latency | Terminal event webhook | Render starts on click; completion varies by video complexity | Workflow trigger and node execution | Whatever your backend codes |
| Typical output | Video status and output routed downstream | Publish-ready MP4 in a new tab | Publish-ready MP4 routed downstream | Publish-ready MP4 returned in JSON |
FAQ
Common questions about the Zapier integration
Still curious? Still curious? Chat with us
Wire ngram into the rest of your stack.
Open the public ngram app in Zapier, connect with a bearer key from ngram Settings, and add Create Video to the workflow that should start each render.