Add Automette as a step in a Zap. Whatever starts the Zap, a form, a deal, a payment, the document is made from your template and the file goes to the step after it.
| Step | Does | App |
|---|---|---|
| 1 | New form response | Typeform |
| 2 | Generate document | Automette |
| 3 | Send email with attachment | Gmail |
Automette is the step that turns whatever your Zap is carrying into a finished file.
Whatever app begins your Zap decides when a document is made. Automette does not need to know where the data came from.
Pick a template and map the fields of your trigger onto it, the way you map any other Zapier step.
The finished document's link comes back into the Zap, so the step after it can email, store or post the file.
The link to the finished file is a field like any other, ready for Gmail, Drive, Slack or whatever comes next.
A second event fires whenever a document finishes in Automette, however it was made, so a Zap can act on it.
Each document is listed in Automette with the template it used and the values it was made from.
Any of these can be filled from a Zap. Use one as it is, or change it to match your own.
Anything Zapier connects to, which is several thousand tools. Automette is one step in your Zap; the rest of the Zap is whatever you already use.
Not for Automette's sake. Whether you need one depends on the other apps in your Zap and how many tasks you run, which is between you and Zapier.
A link to the finished file, its format, the template that made it and the values it was made from.
The Zap waits for it rather than guessing. A step that takes seconds and one that takes minutes both finish properly.
No. Both connect to Automette directly, with no Zapier account in between.
Pick a template, map the fields from your trigger, and let the Zap do the rest. Free to start.