Wire ngram into 6,000+ Zapier apps.
Trigger a render from any Zap. Every one of Zapier's 6,000+ apps becomes a video source - no glue code, no polling, no engineer required. The public ngram app ships with a Create action, instant Video Ready and Video Failed triggers, and a Get Status search step.
- Add the public ngram app — search Zapier's directory, connect your API key, start building Zaps
- Trigger from any Zap — one Create Video action step, six-thousand-plus possible sources
- Instant push, no polling — Video Ready and Video Failed fire the second a render lands or breaks
Three steps from signup to a running Zap.
Public Zapier app, no invite link, no waitlist. Generate a key, connect, build the Zap the same way you build any other.
Create your ngram key
Open Settings then API Keys in ngram and generate a new key that starts with ngs_. One key per environment is the norm.
30 secAdd the ngram app to Zapier
Search ngram in Zapier's app directory and connect with your API key. Public listing - no invite link, no private beta.
1 minBuild 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.
3 min6,000+ apps, one rendering engine inside every Zap.
The full ngram render pipeline lives inside Zapier's app surface. Trigger, branch, look up and retry - all from steps your ops 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 right away so the next step can branch on it without waiting.
Never wait on a poll cycle
ngram pushes to Zapier the second a render lands. The Video Ready trigger fires instantly, no schedule delay, no interval to tune.
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 right away
The Video Failed trigger pushes the instant a render breaks. Wire it to Slack alerts, retry Zaps or on-call SMS in one step.
Pick voices and styles from your account
Voice, style, aspect ratio and duration dropdowns hydrate live from your ngram account on every Zap edit. No hardcoded IDs.
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 fans the finished MP4 out to Slack, LinkedIn and your marketing CMS in the same run.
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 featureMusic
Licensed tracks, auto-ducked under the voiceover.
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 featureMulti-format Export
Every platform ratio out of one render. Pick at Zap config time.
See featureEnterprise Integrations
MCP, Make, n8n, LinkedIn, X and YouTube alongside Zapier.
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 same-day 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 fan the finished MP4 out to LinkedIn and your CMS in the same Zap.
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, attaches the rendered URL to the ticket, and tags it answered.
GitHub release tags become a Zap that renders a release walkthrough and posts it to your DevRel channels - 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.comcreateVisual scenario builder. Reach for it when a Zap needs deeper branching, loops, filters and error paths around the render call.
Explore Make.com integration
MCP ServercreateClaude, ChatGPT and other MCP-aware agents call the rendering tool directly inside a conversation - no Zap required.
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 whatever upstream event triggered the render.
Explore YouTube integrationWhen Zapier is the right trigger, and when it isn't.
ngram + Zapier you are here | Chrome Ext. human click | Make.com scenarios | REST API for products | |
|---|---|---|---|---|
| Who triggers it | An automated event in any app | A human looking at a page | An automated scenario branch | Your application code |
| App breadth | 6,000+ Zapier apps | Any HTTPS page | About 2,000 Make modules | Whatever you wire up |
| Setup time | About 5 minutes per Zap | About 30 seconds to pin | About 10 minutes per scenario | About 1 hour of engineering |
| Best for | Always-on cross-app automation | Ad-hoc renders from web pages | Branchy, conditional workflows | Shipping ngram inside your product |
| Trigger latency | Instant webhook on Zap event | Render starts on click; MP4 returns in under a minute | Instant webhook on scenario event | Whatever your backend codes |
| Typical output | Publish-ready MP4 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.
Add the public ngram app to Zapier, drop Create Video into any Zap, and turn every CRM event, form submission or webhook into a rendered video.