Zapier is a great tool to help you automate your workflow. You can connect Your
Drift account to Zapier so you can start building Zaps to take action automatically.
 

Billing Plan: Integrating with Zapier is available on any paid Drift plan, starting with Premium.

In this article, we'll cover:

• Connecting your Drift account to Zapier
• Some examples of what you can automate
• Adding a second action to your Zap

Here are just a few examples of actions you can do with the Drift<>Zapier Integration:

• Add new contacts in Drift as leads in another CRM
• Send chat transcripts to an email
• Trigger email campaigns in other apps once a contact in Drift provides an email

 
This is a good way to visualize the connection:

 

Set it Up

Select a Trigger

Starting points can change depending on what you're trying to accomplish with the Zap. 

If you have any questions please chat in and we can assist! 

We'll start with a Drift Trigger. (adding actions from a third party into Drift would begin with a trigger for the other app)

Here is a list of all the triggers that Drift offers:

 

A few things to note:

Triggers fire at different times and therefore capture different amounts of information. 

We recommend using Conversation Pushed in order to gather all of the information collected in the conversation. 

A Trigger does not necessarily mean you're gathering all the information you need. In the Pull in Samples step, you can view the available info in the drop down. We'll show you how to add another action to get the rest. 

Connect the two accounts

If you haven't connected your Drift and Zapier accounts, now isthe time to do so!

Navigate to Settings > Integrations > Zapier and you should see a token that looks something like this:

Copy the token and paste it into Zapier, the location where you paste the link can be seen below:

 

Select a Sample

After deciding on your trigger you need to pull a sample from Drift.

 

Depending on the trigger you used, different information will be available, here are a few examples:

• Conversation Pushed - transcript, conversation link, tags, agent name
• New Lead - name, email, phone, other attributes
• User Reached Goal - conversation link, goal id, playbook id

Some triggers won't contain attributes about the contact/site visitor.

If you're using one of these triggers, like Conversation Closed, adding a second action is how you can grab the contact information as well. 
 

Add a Second Action for Contact Data

This is a step that a lot of users miss. If information from the conversation/contact is missing, try adding this step.
Before adding this action, check the Trigger to see if you have a sample with an  Anonymous ID or an End User ID. 
 

• Under "Test This Step" find a sample and unfurl the drop down. 
• Then find either the Anonymous ID or the End User ID. (this example has an Anonymous ID)

Because this example has an Anonymous ID, we'll add the Action "FindUser by Anonymous ID" 
 
If the sample has an End User ID, use the "Find User by End User ID"
 

Next, select "edit options" and set this up so that you pull the Anonymous ID.
 
Your edit options should look like the screenshot below.

This "Search" step is essentially telling Zapier to go into Drift and retrieve any relevant attributes. 

Finally, test this all out and make sure that you see this below.

From here, you are all set to add an  Action .


This will allow you to send this sample, and any other sample you can build, over to another app!

Actions

An “Action” either takes something that happens in another app and maps it back over to Drift, or takes something that happens in Drift, and makes something happen in another app.

Here is an example of sending  Conversation Duration and User ID, two attributes from Drift, over to a Google Sheets document.

We selected that every time a conversation is closed, a new row will be created in our Google Sheets spreadsheet called "Testing Zapier."
 
This row will contain the User ID.

Remember that this is simply an example; you can create actions that are far more complex in terms of the info that they can map for you.

Again, you can also reverse the process and have a third party trigger make something happen in Drift.

Here are the available options for actions in Drift.

Filters

In our example, we set up a zap to send User Id and Conversation Duration over to a Google Sheet.

What if we don't want every conversation? What if, for example, we just want conversations with users who hit the Book a Demo lead stage?

We can set up a Filter by Adding a Step or clicking the plus icon between existing steps!

 

Setting up the Filter is relatively intuitive.

Select the attribute, we then recommend using (Text) Contains, and, of course, enter whichever condition you'd like to filter by.

Lead Stage, specifically, is under Attributes Classification.