What Trail Triggers and Actions are Supported?

Supported Actions

  • Create Task - Adds a task to a site with optional content

Supported Triggers (N/A)

  • Trail doesn't support Triggers yet

Supported Searches (N/A)

  • Trail doesn't support Searches yet

How to Get Started with Trail on Zapier

To get started with Trail on Zapier, first you will need to click to connect your Trail account to use with your Zap.

Click connect an account and a pop up will appear asking for an API key.

Contact us to get an API key for your user account, use the chat tool in the bottom right of the screen.

Paste your key back into the Zapier account pop up and then “Continue”. The pop up will now close and you’ll see your Trail account connected to Zapier.

Click on the "Test" button to check if the the account is connecting properly to Trail:

If you see the success message then you’re connected, if not, check the API key was entered correctly and contact Trail if you’re still having trouble.


Tips for creating tasks in Trail.

Creating tasks at the right Site

If your zap needs to create tasks at different Sites on Trail, we need to know which Site to put the task on.

When configuring your Trigger app, be sure to pass the ID of the Site into the “Site ID” field in the Trail action.

You can get a list of your site IDs in this table

For example if you’re creating a Zap which triggers an iAuditor audit to create tasks in Trail, you’ll need to set up a field on your audit form for an ID (just a blank text box would be fine). Then connect it to the Site ID field on the Trail Zap Action. When the auditor is completing their audits, they just enter the site ID of your store into the iAuditor ID field and it’ll create the actions at the correct Site on Trail.

You can also create a lookup table by using the Formatter app by Zapier, which will allow you to map IDs which you define (e.g your internal company IDs for locations) to the ones in Trail. i.e. Converting your internal company Site ID to a Trail Site ID.

When setting up your Zap you’ll need to test the connection as part of the process, be sure to use your Demo Site ID. This will appear at the top of the Sites table in Trail.

Note: At the moment, you can’t create tasks at multiple sites from a single run of a zap. You’d need the zap to run multiple times and create tasks at each individual location.

Updating content on task

First, make sure you’ve created a task template on the Task Planner that you want to appear on a site. (you can do that here)

Through Zapier you can override the task description when it gets added to a site.

You can change the formatting of text with styling (such as bold, italic, block quotes, code blocks and lists) you'll simply need to enter these in the same way you would do on task description on Trail.

For example entering this:

Would look like this when the task appears on Trail.

Read more about text formatting

Setting a due time on a task

When a “zap” is triggered, by default we’ll create a task on the Trail at that moment and it’ll be due 3 days from when it was added.

3 days is the default as a task might get created at 11pm at night and we want to ensure teams have a fair chance to complete it.

If you want to set a specific deadline for the task, you can pass a date into the “End date” field.

Zapier will convert most things you pass it into a date and time. For example you could say:

“Tomorrow at noon” or “next friday at 7pm”, more examples here.

It’s more likely that you’ll want to hook up the date field to a value from the Trigger app you’re using to pass a dynamic date (e.g a due date set by a maintenance contractor or internal auditor).

Just like “Site ID” and “Description”, you link up the fields to bring the date across. You can then adjust that date by adding a modifier in Zapier.

Note: At the moment, you can’t set a task to repeat, you can only set a start and end date for a task, so it appears once per zap.


Common Problems with Trail

Tasks aren’t appearing on my Trails

Whenever your Zap successfully automates something, it's called a Task.

For example, if you have a two-step Zap with one action step to send out an SMS, the automated SMS sent out is your Task. 

Check whether the task happened.

If the task hasn’t happened or there was a problem, follow these guides to identify the problem.

Did this answer your question?