How do I connect ngram to Zapier?

Add a ngram step to a Zap, then paste a key created in ngram under Settings → API Keys. Zapier stores that connection and reuses it for every ngram step.

What actions and triggers are available?

Two actions — Create Video and Get Status — and two triggers — Video Ready and Video Failed — which fire on the video.completed and video.failed events.

Do I need to write any code?

No. Zapier maps each action's fields to a form, so you configure the prompt and options visually. Create the required ngram credential yourself under Settings → API Keys.

How is the connection authenticated?

With the ngram API key you create in Settings, sent as a bearer token on every request. Rotate or revoke the key from API Keys, then reconnect the Zap without rebuilding its steps.

What happens if I hit the job limit?

ngram allows three video jobs processing per account at once. If a Create Video step exceeds that, add a delay or stagger the Zap so earlier renders finish before the next begins.

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.

Open ngram All docs

Read before this

Read these direct prerequisites in order. Each guide lists any earlier context it assumes.

1Integration accessUnderstand current connection surfaces, authentication paths, and coming-soon states.
2API keysCreate, copy, rotate, and revoke a self-service API key in Settings.

Before you start

Sign in to ngram, create an API key in Settings, and make sure you can create a connection in Zapier. Start with non-sensitive test data, keep the key in Zapier's connection store, and confirm the account that should own generated projects before enabling a live Zap.

Overview

The ngram Zapier app turns an event in your stack into a video. Zaps run on ngram's public API under the hood, using the bearer credential you create in Settings and the same three-concurrent-job limit.

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 created from Settings → API Keys. Keys start 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.

Zapier FAQ

Keep going

Getting started

Learn the create → poll → webhook lifecycle after creating your self-service API key.

Zapier integration overview

The product story behind the ngram Zapier app.

n8n

Build self-hosted workflows around the ngram render API.

Continue in ngram

Open the workspace and put this guide into practice with your own project.

Open ngram