Shotstack has apps for n8n, Make and Zapier, so a workflow can render video without code. Each app calls the same Edit
API: it renders an edit or a saved template, waits for the render and returns the finished file.

| Tool   | Get the app                                                                                                                    |
| :----- | :----------------------------------------------------------------------------------------------------------------------------- |
| n8n    | The community node [`@shotstack/n8n-nodes-shotstack`](https://github.com/shotstack/shotstack-n8n), from Settings → Community Nodes |
| Make   | [Shotstack on Make](https://www.make.com/en/integrations/shotstack)                                                             |
| Zapier | [Shotstack on Zapier](https://zapier.com/apps/shotstack/integrations)                                                           |

Connect each app with an API key from your [dashboard](/getting-started/request-api-keys). Use your `stage` key while you
build: those renders are free and carry a watermark.

## A video for every row

Most workflows render one saved template many times:

1. Save the video as a [template](/architecting-an-application/templates) with merge fields such as `{{ADDRESS}}`. You
   can design it in Studio, ask an [AI agent](/agents) or use the API.
2. Start the workflow from new data, such as a spreadsheet row, a form response or a CRM record.
3. Render the template with the app, mapping each field of your data to a merge field.
4. When the render is ready, send the file on: to storage, a social channel or an email.

Map every merge field on each render. The fields you send replace the template's saved values, so a field you leave out
renders as its raw placeholder. See [From draft to production](/agents/draft-to-production) for the whole pattern.

## With AI agents

In n8n, the Shotstack node also works as a tool for an AI Agent node. Point the agent at a template render rather than a
full edit: filling a few merge fields is more reliable than writing a whole timeline.

For each tool's own interface, such as building a workflow or mapping fields, see that tool's documentation.