Zapier
The Automette Zapier app connects document generation to the rest of your stack. When something happens in another tool (a form is submitted, a row is added, a deal changes stage), a Zap can generate a document from one of your templates and pass the file URL to the next step.
Private beta. The Automette Zapier app is not yet listed in the public Zapier directory. Contact us for an invite link to add it to your Zapier account.
What the app provides
| Type | Name | What it does |
|---|---|---|
| Action | Generate Document | Renders a document from a template with the data you map in, and returns the file URL |
| Trigger | Document Generated | Fires whenever a document finishes generating in Automette, from any source |
Connect your account
- In the Zap editor, add an Automette step and click Sign in.
- Paste your API key. You can create one in the Automette dashboard under Developers → API Keys.
- Zapier verifies the key and saves the connection for reuse across Zaps.
The key is scoped to a team, so the connection sees that team's templates and renders.
Use the Generate Document action
- Pick any app as your Zap trigger (a form tool, a spreadsheet, a CRM).
- Add an Automette step with the Generate Document event.
- Choose a Template. The dropdown lists your team's templates.
- Choose an Output Format if you want something other than the template default. The options match what the template's engine supports, for example PDF, PNG, or JPG.
- Map your trigger data into the template fields. Each field of the template appears as its own input. Image fields expect a URL to the image file.
- Test the step. The output includes
url(the generated file),id,status,format, andtemplate_name, ready to use in later steps.
Slow renders
The action waits up to 25 seconds for the document to finish, which covers typical renders comfortably. If a render takes longer, the step errors with the render ID and the document keeps generating in the background. For consistently heavy templates, generate with the action in one Zap and act on the finished file with the Document Generated trigger in another.
Use the Document Generated trigger
The trigger fires on every completed render for your team, whether it came from a Zap, the API, a bulk CSV job, or another automation. Use it to send the finished file somewhere: attach it to an email, save it to cloud storage, or post it in chat.
Each event includes:
| Field | Description |
|---|---|
id | The render ID |
url | Link to the generated file |
format | File format, for example pdf or png |
template_id, template_name | The template that produced the document |
data | The input values the document was generated with |
source | Where the render came from, for example api or automation |
created_at | When the render was created |
Alternatives
If you only need Google Sheets, the built-in Google Sheets automation needs no Zapier account. For full control from your own code, use the API.
Last updated on