Connect Automette with Zapier

You can connect Automette with Zapier using our official Zapier integration, and generate documents from the thousands of apps on the Zapier platform. The integration gives you two things:

• An action. Generate a document when something happens in another app, and pass the finished file on to the next step of your Zap.
• A trigger. Start a Zap whenever a new document is generated in your Automette account, whatever produced it.

Prerequisites

• An Automette template with fields for the values you want to fill in.
• A Zapier account.
• The Automette integration added to that Zapier account, which is the first step below.

1. Add Automette to your Zapier account

The integration is in private beta, so it is not in Zapier's directory yet. In Automette, go to Integrations and click Zapier under "Other ways to connect". Open the invite, accept it while signed in to the Zapier account you want it on, and Automette appears when you search for it in the Zap editor.

2. Connect your Automette account

The first time you add an Automette step, Zapier asks you to sign in.

1. In Automette, go to API Keys and create a key.
2. Paste it into Zapier and save.

The connection is listed under the team the key belongs to, so if you connect keys from two teams you can tell them apart.

3. Generate a document

Add an Automette step with the Generate Document event.

1. Choose a Template. The list is your team's templates.
2. Choose an Output Format if you want something other than the template's own, for example PNG instead of PDF.
3. Fill in the fields. Each field of the template appears as its own input, and you drag values from earlier steps into them. A field you leave blank is left out; see Blank values for what that prints.
4. Test the step.

Styling and other fields

A canvas template has colours as well as content. Show styling fields adds them to the form, one colour per layer. Finer typography, such as shadows and font choice, is set in the template rather than per run.

Under Optional at the bottom of the step:

• Additional fields takes any template field not listed above, as name and value.
• Render options takes settings for the render itself rather than values in the document: visibility (public for a permanent link, secure for one that expires in 24 hours), scale, formats, filename_pattern.

4. Start a Zap when a document is ready

The other direction: Document Generated is a trigger, so it goes at step 1 of its own Zap. It fires when a document finishes in Automette from a Zap, the API, a form, a Dynamic URL or an automation. Documents made on the Generate page, and bulk runs from a CSV file, do not fire it.

Choose one or more Templates to run only for those. Leave it empty and the Zap runs for every document your team produces, which on a busy account is a lot of Zapier tasks.

Each run carries the finished file's link, its format, the template that made it, and the values it was made from.

If a step does not run

• The Zap is off. Turning it on is what registers it with Automette.
• Nothing has happened yet. The trigger fires on the next document, not on past ones.
• The document failed. The step reports the reason, and History in Automette has the full run.

Without Zapier

Google Sheets and Airtable connect to Automette directly, with no Zapier account in between: see Save a document link in Google Sheets and Save a document to an Airtable record. To generate from your own code, use the API.

Last updated on