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
- Open the ngram app on Zapier at zapier.com/apps/ngram and add a ngram step to a Zap.
- When Zapier asks to connect, paste an API key from Settings → API keys — it starts with
ngs_. - Zapier stores the key as the connection and sends it as a bearer token on every action and trigger.
Actions and triggers
| Type | Name | What it does |
|---|---|---|
| Action | Create Video | Start a render from a prompt, with optional website, voice, style, aspect ratio and duration. |
| Action | Get Status | Fetch a video's status and finished MP4 URL by id. |
| Trigger | Video Ready | Fires when a render finishes, on the video.completed event. |
| Trigger | Video Failed | Fires 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:
- Trigger: New row in a Google Sheet.
- Action: Create Video in ngram, using the row's prompt and aspect ratio.
- Trigger: Video Ready fires when the render finishes.
- 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.