A video brief for a customer Q&A
Two presenters answer a customer’s question about reusing a recording. A request form could supply the question and approved answer for this kind of draft.
Zapier IntegrationCreate integration
Wire ngram into 6,000+ Zapier apps.
Connect ngram in Zapier
API-key video creation requires a paid plan and enough credits. Supported connected-app sign-ins have separate access rules.
Check integration accessTrigger 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 actions to create a video from a prompt, text or URL, a Create Image action, and a Get Video Status search.
- 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
Finished videos you could request from a Zap
Explain a change in quarterly results
The sample uses approved counts of 100 and 120 completions. A reporting Zap could take two approved cells from a sheet, calculate the change and ask for a short update without sending the rest of the sheet.
Follow up on one resolved support call
The clip gives a customer two checklist items and names who will follow up on Friday. A Zap triggered by an approved support summary could pass those facts into a brief for the account owner to review.
How it works
Three steps from signup to a running Zap.
The illustrated Sheets example shows how a row can supply a brief. Test the trigger with an approved sample row, then check the resulting video before turning on the Zap.
01
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.
Setup02
Add 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.
Connect03
Build the Zap
Choose your trigger and map the approved brief into an ngram create action. Store the returned video ID and use a completion trigger or status lookup before routing the result.
BuildWhat it can do
6,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 Video 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.
Set the video in the step
Choose the model, style, duration, aspect ratio, voice, narration language, energy, mood, Brand Kit and format in the Create Video step. Model shows ngram-flash and Opus 5.5 with their credits per second, Brand Kit lists the kits on your ngram account, and blank fields let ngram choose.
Verify every delivery you receive
Each push carries an HMAC-SHA256 header keyed on your account secret. Validate the signature before trusting the body.
Where it fits
Four moments where a Zap quietly renders a video for you.
Use a Zap when an approved record should start the same steps each time. For a single brief that still needs discussion, make the video directly in ngram.
Start an introduction when a CRM record is ready
Use an approved-stage change as the trigger. Map the company, audience and approved summary into the video brief. Send the finished link to the account owner for review.
See the sales prospecting playbookTurn a form response into an onboarding draft
Have a request form collect the role, task and source page. Check that those fields are present, then send the video ID back to the same record so the draft can be found again.
See the customer onboarding playbookRoute an approved launch brief to its editor
Trigger on a row marked ready. Map the feature and customer impact into the prompt. Wait for completion before sending the link to the launch editor.
See the feature announcement playbookRoute unsuccessful runs to a person
Keep the source record and video ID together. On a failed result, notify the person responsible for the brief so they can inspect the job before retrying.
See the explainer video playbookSupported triggers
The 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.
HubSpot
CRM events
Salesforce
deal stage triggers
Pipedrive
pipeline movement
Typeform
form submissions
Jotform
form submissions
Google Forms
form submissions
Slack
messages, slash commands
Google Calendar
event start, event end
Gmail
new email, label added
Airtable
new record in view
Notion
new database row
Webhooks by Zapier
any inbound POST
The rest of ngram
Explore all features 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
A choice of voices in multiple 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
Pick a Brand Kit in the Create Video step to apply its logo, colors and fonts to the video.
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 featureConvert anything Zapier hands you
All converters Every 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 textMore ngram tools
All ngram tools Polish, 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.
Polish what the Zap rendersRun the output through the rest of post
If you don't want to recordAlternatives a Zap can call into
Built for teams
All solutions 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.
Product Marketing
Wire changelog updates and launch tags to Create Video, then route the finished MP4 to the downstream step your team chooses.
Sales Enablement
Trigger personalized intros from CRM stage changes. New deal at Demo Sent renders a tailored ngram clip back into the record.
Customer Success
Onboarding milestones in your CS tool fire a Zap that renders the right welcome or training video and emails it to the right contact.
Support Teams
New ticket tagged how-to in Zendesk or Intercom? Zapier fires Create Video and routes the rendered URL to the next support step.
Developer Relations
GitHub release tags become a Zap that renders a release walkthrough and routes it to your DevRel workflow for review - no manual recording.
Founders
Pipe weekly metrics from Mixpanel or Stripe into a Zap that renders an investor update video, ready before Monday standup.
Product Managers
Linear status changes fire Zaps that render a changelog video for every release without a single hand-off to design.
By industry
Other ways to trigger ngram
All integrations 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 integrationHow it compares
When 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
Open Zapier's app directory and search for ngram. Every signed-in ngram user can create a bearer key in Settings, connect it in Zapier, then add the Create Video action or an available status step.
Still curious? Still curious? Chat with us
Zapier Integration
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.