Introduction

Zapier enables you to send messages to your Intuiface experiences based on triggers defined for 1000+ third party applications. Be sure to review this overview article about Web Triggers before going further.

What is Zapier? 

Zapier is a service that gives you the power to integrate two or more Web apps, creating a chain of cause and effect. Zapier refers to these chains as Zaps. Here's a sample Zap: When I get an email in my Gmail account, copy the attachment into Dropbox and then send me a text using Twilio. This amazing power would - in the past - have required significant development skills, if it was possible at all. Now you can integrate Web apps with a couple of mouse clicks.

Thanks to Intuiface's Web triggers support, Intuiface can be paired with any other app on Zapier using a Zap.

How does it work?

The first thing you have to do is create a Zapier account. With that free account you can connect any two apps - aka a "two step Zap" - from among a subset of the 1000+ apps supported by Zapier. Paid accounts enable you to create Zaps with 3+ steps, grant you access to their entire app inventory, and increase the number of tasks you can run in a month.

You can then either pick one of the prebuilt Zaps targetting Intuiface - aka a Zap template - or you can build your own Zap.

Building your own Zap

If you don't want to use an existing Zap template, you can build your own Zap.

After clicking on the Make a Zap! button in your Zapier account, select any of the 1000+ apps available in Zapier and configure a trigger associated with that app. Then specify the message you want to send to Intuiface as a result. That message can contain any set of information, including info exposed by the trigger.

When your Zap is ready, you need to set up one or more instances of the Web Triggers interface asset in Composer to receive these messages and call the proper actions in your experience.

Important Note

All Zapier plans limit how many tasks can be run per month. (A task occurs whenever a Zap successfully performs one action.) Be aware of how many tasks your plan supports to ensure you don’t hit your limit. For example:

• Free Plan: 100 tasks per month
• Starter Plan: 1000 tasks per month

Zaps in action - A demonstration

For your own education, we've built four examples you can try out yourself using the Zapier Demo sample experience located in the Intuiface Examples catalog.

You can learn more about how we built the Demo experience in the Zapier demo sample article.

List of existing Zaps

10+ Zap templates targeting Intuiface are available through Zapier.

 

Alternative use of Zapier

Zapier enables you to send messages to your experiences but you can also leverage it to send messages to other apps from your experiences using the API Explorer.

For example, you can trigger Zapier from an Intuiface experience to send an email via your Gmail account. Once logged into your Zapier account, click on Create and select Zaps

You will have a Trigger and an Action panels, select the Trigger panel

In the list, select Webhooks by Zapier

In the Event list, select Catch hook and click on Continue

In the Triggers tab, just leave the Child key empty as you will most likely use the entire payload of the webhook

Click on Continue again.
The next tab will display the webhook URL you will need to use with the API Explorer

 

Now that you have your webhook URL, you can go into the Composer and use the API Explorer to create the corresponding REST Interface Asset that will be used to trigger Zapier.

Copy the webhook URL into the Request URL of the API Explorer
By default the request is set to a GET, change it to a POST

Then add a parameter Content-Type application/json and set it as Header
Add all of the parameters you want to use in your email and set them as Body

Once you are done, click on the arrow, rename your REST Interface Asset and head back to Zapier.
Go back to the Trigger panel and to the Test tab
You should be now able to test it properly and get the records from the REST Interface Asset displayed


Click on Continue with selected record, it will automatically jumps to the Action panel
Open it and select Gmail

In the Event drop down menu, select Send Email then click Continue

You will be asked to link your Gmail Account to Zapier, once linked, click on Continue.
You will be presented the Action tab where you can specify all of the information you want in the email.
All of these fields can be field manually or you can also use the parameters set in your REST Interface Asset as part of the content used in these fields.

For instance email / Team / location / Signature can be used in any field

Once all of the required fields are completed, click on Continue
You will be asked to Test it or Skip the Test.
Once the test over, you will be able to Publish your new Zap.

Now go back to the Composer, you can add an action in your experience to set some/all of the parameters or keep the ones already set.


This action will send a message to Zapier that will trigger the send email to Gmail action.