Zapier

Automate ngram with Zapier

Connect ngram to thousands of apps without writing code. Trigger a render when a row is added, a form is submitted or a deal closes — then send the finished video wherever your team already works.

Overview

The ngram Zapier app turns any event in your stack into a video. Zaps run on ngram's public API under the hood, so the same bearer key and the same three-concurrent-job limit apply — you just never touch the endpoints directly.

Connect your account

  1. Open the ngram app on Zapier at zapier.com/apps/ngram and add a ngram step to a Zap.
  2. When Zapier asks to connect, paste an API key from Settings → API keys — it starts with ngs_.
  3. Zapier stores the key as the connection and sends it as a bearer token on every action and trigger.

Actions and triggers

TypeNameWhat it does
ActionCreate VideoStart a render from a prompt, with optional website, voice, style, aspect ratio and duration.
ActionGet StatusFetch a video's status and finished MP4 URL by id.
TriggerVideo ReadyFires when a render finishes, on the video.completed event.
TriggerVideo FailedFires when a render fails, on the video.failed event.

Example Zap

A common pattern turns a spreadsheet into a batch of videos and posts each one back to your team:

  1. Trigger: New row in a Google Sheet.
  2. Action: Create Video in ngram, using the row's prompt and aspect ratio.
  3. Trigger: Video Ready fires when the render finishes.
  4. Action: Send the MP4 URL to a Slack channel.

Auth and limits

Every action and trigger uses the bearer key you connected. Because Zaps run on the public API, the same limit of three concurrent video jobs applies — if you queue a large batch, space the Create Video steps out or add a delay so renders clear before the next one starts.

Zapier FAQ

Ready to build?

Create a key in Settings and make your first call in minutes. The same key works across the REST API, MCP, Zapier, and n8n.