Zapier empowers apps to do together what they can’t on their own. With a bit of inspiration and creativity, your users can pull dozens of apps together into unique workflows to get more done with your app in far less time.
Expected time to create a Zap Template: 10 minutes.
Note: Only Zapier integrations that have been launched publicly can be used in Zap templates. Integrations in private
status cannot be used in a Zap template.
Choose the app’s trigger from the dropdown that starts your Zap.
Test
pane. If certain fields aren’t available, it’s because the integration developer didn’t include them in the integration’s sample data. While you can still use the method in the Zap template, you might not be able to pre-map fields for users in subsequent action step(s).
If there are input fields to customize the trigger, you may assign a default value or leave the input fields empty. Users will be able to input their own information when setting up the Zap. Once done, click Continue to proceed to the next step.
Note: Only Zapier integrations that have been launched publicly can be used in Zap templates. Integrations in private
status cannot be used in a Zap template.
Choose the app’s action from the dropdown that you want to follow the trigger. Same as the trigger, the Zap template editor will load the sample data available for the selected action.
Note: If you add a search action following the trigger, you will need to add another action step following the search. This is because Zaps cannot end with a search method (unless it’s a dyanmic find or create
action).
Now for the most crucial part of your Zap template: Where appropriate, map the output fields from the trigger to the input fields in the action. The action step will show input fields that are statically available. Dynamic input fields that populate based on the input of another field will not be available. For the best Zap template experience, add field mapping to as many input fields as possible to help users set up Zaps quickly. For example, you might map Gmail’s Attachment
field to File
field for Google Drive, as well as Attachments Filename
to the File Name
field.
Note: Custom fields from apps (i.e. fields added by users) will not be available. This is because the Zap template editor is not authenticated with an app account to fetch that data. When users create a Zap from your template, they’ll be able to leverage dynamic and custom fields.
Tip: Use Zapier’s date and time syntax to modify dates and times in action form fields.Most dropdown menus are used to select folders, projects, and other user-generated data, and should be left blank by default. You can, however, select options for dropdowns for boolean yes/no fields if you’re certain which option is best for all users of this Zap template. Zap template action forms include
required
(denoted with a red asterix) and optional
fields. When users set up your Zap template, they are required to complete required
fields before turning on the Zap. If you know the best data to map to those fields, add them to make sure your users’ Zaps include as much detail as possible.
Note: Do not enter a value into an input field unless every user of the Zap Template would want that value included in the action.Zapier then shows a
Test
pane, similar to what users see when setting up Zaps. You won’t be able to test your action steps when building a Zap template. The Test
pane will call this out, and default to showing a successful test.
+
button where you want to insert the additional step. Then repeat step 2 and set up the additional action.
For example, you could add a filter between the trigger and action step to have the action step only run when specific criteria is met. Learn more about filters. You can define a filter in the Zap template, or leave it blank and let users customize the filter to their needs.
Note: Most Zap templates don’t need filters, and most filters should be added by users later if required. However, including a filter in a Zap template can be useful if your Zap Template is only useful with a filter to remove extraneous data.
Note: Paths by Zapier, Code by Zapier, Webhooks by Zapier, Looping by Zapier, and Formatter by Zapier action steps are currently not allowed in Zap templates.
Submit
in the top-right corner or at the bottom of the Test
in the last step of your Zap template.
Submit
, you will be prompted to provide a title and description for the Zap template.
Add new Gmail emails to Google Sheets as rows
. The title mentions what happens in the trigger app followed by what Zapier does in the action app. Some examples of good titles:
Create Trello cards for new Wufoo form entries
Get Slack notifications for new Google Drive files in a folder
Subscribe new Gumroad customers to a MailChimp list
Save new liked SoundCloud tracks to Google Drive
Tip: Use your discretion whether to mention the action or trigger app first. The trigger app works best first in most cases, but sometimes it sounds awkward — if so, go with the action app first.Follow these rules in your Zap template titles:
Create
, Add
, Make
, Insert
, Update
, Subscribe
, or Get
. Use unique verbs when possible, and use the most appropriate verb for the action Zapier performs with the app.
Create Trello cards for new Wufoo form entries
Create Trello Cards For New Wufoo Form Entries
Get Slack notifications for new Google Drive files
Slack will notify you when a new Google Drive file is saved
Google Sheets rows
or Mailchimp subscribers
.
sync
or automatic
in titles. All Zaps run automatically, and can’t sync data bidirectionally. Avoid these terms in titles; sync is misleading, and automatic is redundant.
you
, we
, or I
in Zap Template titles unless the trigger or action items specifically include those words.
Find yourself spending too much time adding event attendees to your CRM by hand? Now with the help of Zapier, the tedious work is done for you. This integration will add every new Eventbrite attendee to Zoho CRM as a new contact, saving you time for more important work.
After someone fills out a form on your site, you’ll want to hear about it or send them a follow-up email. This Zapier automation handles both gracefully, sending an email via Gmail to you or the form respondent whenever you get a new Typeform entry. You’ll never have to send the same message over and over again.
Expedient order processing makes for happy customers. Make sure you act on every new delivery with this Zapier automation. It will capture every new order placed on your Shopify store after being set up, creating a delivery task for it on Onfleet so your team can fulfill it without delay.Keep these guidelines in mind:
integration
or automation
, that are universally understood.
Note:
, and format the entire note in italics with Markdown formatting. For example: *Note: Add the tag you want to the Zap's Filter step.*
Note: Always write unique descriptions for each Zap template — Zap templates that use the same descriptions but only replace app names, or those that duplicate the Zap template title, will be rejected.
Save Draft
.
Now try using the Zap template to make sure it works as expected. Open your Zap Template dashboard, click the ...
icon beside the Zap template you built, and select Create Zap
. A new window will open, creating a Zap from the Zap template. Click through each step of the Zap, validate everything works as expcted, and that you can turn the Zap on.
Submit for Review
in the same modal where you added the title and description. This will submit the Zap template to our team to review to ensure it works as expected and meets our standards.
After your Zap template(s) have been reviewed, we’ll send you an automated email with the subject We’ve reviewed your Zap templates!. Reviews are typically completed within 2 weeks. If your Zap template(s) are approved, we will publish them to have them appear on your app’s directory page and in our embed solutions.
If your Zap template is rejected, the automated email will provide a reason and how the Zap template needs to be updated before re-submitting for review.
You can create and submit as many Zap templates as you like! The more you create, the easier it will be for users to discover your integration and build Zaps using it.
eventType
between the trigger and step 2 of your Zap template, but eventType
isn’t available in the trigger’s sample data, you could create a custom pill to pull this field dynamically. Here’s how to create custom pills.
Step 1: Identify the step position
eventType
{{
__
}}
eventType
field isn’t returned in the sample data for Google Calendar > New Event. If you want to map that field in a Zap template, you can do so using the custom pill {{1__eventType}}
.
Step 4: Insert custom pill
{{1__questions__3}}
Where can I find a Zap template's ID?
...
icon beside the Zap template.Copy Template ID
.Why do I see Zap templates on my app's directory page that don't appear on my "Zap Templates" page in the developer platform?
Who can publish Zap templates using my integration?
Can I opt out of Zapier-generated Zap templates for my integration?
Can we remove or hide Zap templates that include our competitors from our directory page?
How can I make changes to a published Zap template?
How can I re-order Zap templates on my directory page?
How can I exclude specific Zap templates on my directory page?
How can I view all Zap templates created by my integration team?
How can I unpublish a Zap template?
Why were my Zap templates rejected?
Can I select which Zap templates to display in my embed?
How many users are using a particular Zap Template
How many Zap templates should my integration have?
Why did my Zap Templates stop working?
Which use cases should my Zap templates highlight?
Can I add filters/other conditions to my Zap templates?
Do users need to have an account to create their own Zaps?