Branching video workflows. Visually built in Make.
Drop the ngram modules into any scenario. Routers split the path. Filters gate the render. Loops fan out across rows. Error routes catch failures the moment they happen - and Make pushes you the finished video the instant it lands.
- Render from any scenario trigger — 1,500+ apps in Make - any one of them can kick off an ngram render
- Routers, filters and loops — branch on prompt length, customer tier, or any field in the payload
- Instant webhook on completion — Watch a Video Ready fires the second the render lands - no polling
Four steps. A working scenario in under ten minutes.
Make's visual canvas does the orchestration. ngram does the rendering. The two connect through a signed key and an instant push - no polling, no custom code.
Create your ngram key
Open Settings then API Keys in ngram. Generate a key starting with ngs_. Rotate any time without breaking active scenarios.
30 secConnect ngram in Make
Add the NGram API Key connection in Make. Paste the key. During the private-app phase, use the invite link shared with you.
1 minBuild the scenario
Drop in the Create a Video action. Wire it to any trigger module. Pair it with Watch a Video Ready for an instant push when the render completes.
5 minAdd routers and error paths
Route by prompt length, customer tier, or any field. Catch failures with Watch a Video Failed and branch into a Slack alert or retry loop.
3 minThe whole render lifecycle, exposed to Make's canvas.
Create a Video from any trigger
Drop the Create a Video action into a scenario. ngram returns an ID immediately so the next module can run without waiting.
Instant push when a render lands
Watch a Video Ready uses Make's attached webhook. ngram pushes the moment a video hits a terminal state. No polling, no schedule delay.
Route, filter and loop
Make routers split the path on any field. Filters gate the render. Iterators fan out across Sheets, Airtable or HTTP responses.
Look up any render mid-flow
Get Status search returns progress, state and the final URL for any vid_ id. Drop it anywhere in a scenario to inspect or branch.
SSRF-validated callbacks
Hook URLs are validated at subscription time. Private ranges and link-local addresses are rejected before the scenario can save.
Backoff retries on failed pushes
Failed deliveries retry on a 1m, 2m, 5m, 15m, 30m schedule. Up to six attempts before the scenario surfaces the failure.
Dropdowns from your account
Voice, style, aspect ratio, duration and animation dropdowns hydrate live from your ngram catalog every time you edit the scenario.
HMAC-signed webhook bodies
Every push is signed with HMAC-SHA256 using your account secret. Make verifies the signature before delivering to your modules.
Three scenarios teams ship in their first week.
Auto-render a launch video the day a release ships.
Trigger on the changelog entry. Route by release type. Render the explainer with ngram, post to Slack on success, alert the PMM channel on failure - all in one scenario.
See the feature announcement playbookBulk render personalized intros for an outbound campaign.
Iterate a Google Sheet of prospect rows. Branch on company size. Render a 30-second intro per row. Write the finished URL back to the sheet and send the next email.
See the sales prospecting playbookAirtable record to publish-ready video, no human in the loop.
Watch a status field flip to Approved. Pull the brief, fire Create a Video, watch the ready event, post the finished URL back to the same record. Filter out drafts up front.
See the changelog video playbookTwelve app categories where Make scenarios start.
Make connects to 1,500+ apps. These are the categories teams most often wire into the Create a Video module. Anything else with an HTTP webhook works too.
What ngram does when a Make scenario fires Create a Video.
Every render goes through the same ngram pipeline. Here is what runs inside it.
AI Visuals
Scene-matched graphics in 30+ styles, generated to fit the scenario payload.
Explore featureAI Voiceover
40+ voices in 20 languages, auto-synced to the timeline.
See featureScript Generation
Scripts written from the prompt or structured fields you pass in.
See featureMusic
Licensed tracks, auto-ducked under voice.
See featureMotion Graphics
Auto-animated text, transitions and charts. No timeline required.
See featureCaptions
Burned-in or .srt captions, frame-accurate and editable.
See featureBrand Kit
Logo, colors, fonts and intros on every export.
See featureCollaboration
Anchored comments, version history, async review.
See featureMulti-format Export
Every platform ratio, one render.
See featureEnterprise Integrations
Make, Zapier, n8n, MCP, LinkedIn, X, YouTube and more.
See featureEvery Make module output is a source the converter accepts.
Make scenarios route URLs, docs, text and files through routers and filters. Hand the final field to the Render Video module and the right converter takes over.
URL to Video
Branching scenarios that produce a URL - pipe it into URL to Video for a storyboarded draft.
Convert from URLText to Video
Form fields, deal notes, AI module outputs - any text payload turns into a narrated video.
Convert textBlog to Video
CMS triggers route new posts through Make, then ship them as social-ready video on the same day.
Convert a blogPolish, translate or re-cut what Make renders.
After the scenario returns a video URL, every ngram tool can run on the output without leaving the editor.
Who runs ngram inside Make scenarios.
Anyone with a no-code workflow practice can wire ngram into their existing scenarios without writing backend.
Already running automations in Make. Add video to your scenario library without changing the platform you've standardized on.
Wire ngram into experiment loops, A/B campaigns and lifecycle flows without spinning up custom backend services.
Auto-render explainers when a release ships. Branch by audience, push to channels in parallel, alert the team on any failure.
Bulk-render prospect-tailored intros from a CRM or sheet. Loop over rows, render in parallel, write URLs back, send the next email.
Trigger personalized renewal or onboarding videos on lifecycle events. Branch by tier or health score, attach to the next outreach.
Route incoming tickets through a scenario that renders a short answer video from the linked help article and replies in-thread.
Build the whole content engine in Make. Trigger on a publish event, render the social cut with ngram, schedule it to LinkedIn and X.
Make is one trigger. Here are the others.
ngram is the same rendering engine behind every integration. Pick the trigger that fits the team - a visual canvas, a Zap, a node graph, a CRM event or an agent tool call.
Chrome ExtensioncreatePin ngram to your toolbar. Click the icon on any page and get back a publish-ready video, without ever leaving the tab.
Explore Chrome Extension integration
ZapiercreateSimpler than Make when you just need a linear A-to-B flow. Wire ngram into 6,000+ apps with one Zap per workflow.
Explore Zapier integration
n8ncreateSelf-hosted workflow node. The video render API is the only thing that leaves your infrastructure - everything else stays in your container.
Explore n8n integration
MCP ServercreateClaude, ChatGPT and other MCP-aware agents call the rendering tool directly inside a conversation. No scenario needed.
Explore MCP Server integration
LinkedInpublishSchedule a Make-rendered video straight to a company or personal LinkedIn page from inside the ngram editor.
Explore LinkedIn integration
X (Twitter)publishWhen a Make scenario finishes a render, route the output through the X publish module and post the clip with copy in the same flow.
Explore X (Twitter) integration
YouTubepublishUpload with title, description, chapters and tags pre-filled from the source fields the scenario passed in.
Explore YouTube integrationWhen Make is the right canvas, and when it isn't.
ngram + Make you are here | Zapier simpler flows | n8n self-hosted | REST API for products | |
|---|---|---|---|---|
| Workflow shape | Visual canvas with routers, filters, loops | Linear A-to-B Zaps | Node graph, code if you want it | Whatever your application code shapes |
| Branching | Native routers and filters on every module | Paths and filters, simpler model | If/Switch nodes, code-level control | Whatever you write |
| Hosting | Make-hosted, EU and US regions | Zapier-hosted, US-only by default | Self-hosted in your infrastructure | Wherever your app runs |
| Triggers | 1,500+ apps in Make | 6,000+ apps in Zapier | 400+ nodes plus arbitrary HTTP | Whatever you call from |
| Error handling | Watch a Video Failed route per scenario | Path module on failure | Error workflow per node | Try-catch in your code |
| Best for | Branching workflows beyond simple A-to-B | Quick automations with one trigger and one action | Teams that need self-hosting or full code escape | Shipping ngram inside your own product |
| Setup time | About 10 minutes for a scenario | About 5 minutes per Zap | About 30 minutes if self-hosting | About 1 hour engineering |
FAQ
Common questions about the Make integration
Still curious? Still curious? Chat with us
Branch, loop and route your video workflows.
Wire ngram into any Make scenario. Routers, filters, loops and error paths around every render - no code, no polling, no waiting.