Resources · Make integration

Drift Make integrationAutomate Drift with Make.

What if every new lead reached Drift already tagged and ready for sales? The Drift Make integration gives you 24 modules: 16 actions and 8 searches. This page shows sales and support teams how to link the account and build a first working scenario.

Try the Drift integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Drift Make integration do for you?

The Drift Make integration lets Make read and write your Drift data: contacts, tags, users and conversations. You build a scenario, the automation you assemble in Make, out of modules, the small bricks that each do one job. Drift offers 16 action modules and 8 search modules, with no code.

Leads that arrive ready. A form or a CRM in another app sends a new person, Create a Contact adds them to Drift, and Add Tags labels them by source. Your reps open the chat already knowing where the lead came from.

A cleaner contact base. When someone asks to stop receiving emails in your billing tool, Get a Contact finds them by email and Unsubscribe a Contact applies the choice in Drift too. Delete a Contact handles removal requests.

Conversations you can reuse. List Conversations and List Conversation Messages pull chat history out of Drift, so a support lead can copy it into a shared table or a ticket.

Drift has no trigger module in Make, so a scenario starts from another app or from a schedule, every 15 minutes by default. The doc lists no limits for this app. The same app also exists as a node in n8n: see the Drift n8n integration and the n8n vs Make comparison. New to the editor? The Make training starts from zero.

Connect

How do you connect Drift to Make?

  1. 01

    Open a Drift module

    In your scenario, add any Drift module, for example Get a Contact. In the module panel, click Create a connection. A connection is your Drift account linked to Make once, then reused by every Drift module.

  2. 02

    Name the connection

    Give the connection a name if you like, such as the workspace it points to. It is optional, but it helps later when several people or several Drift accounts share the same Make organization.

  3. 03

    Authorize and save

    Make opens Drift's authorization page: sign in and allow access, or paste the key Drift gives you if Make asks for one. Back in Make, click Save. The module can now read your Drift data.

First scenario

Your first scenario: tag every new lead in Drift

GoalWhen a new lead appears in another app, Make creates the contact in Drift and tags it for sales.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where your leads land first, such as your form tool, and choose its module that watches new entries.

  2. 02

    Add Create a Contact

    Click the + on the right of that first module, search for Drift and pick Create a Contact. Click Create a connection if Drift is not linked yet.

  3. 03

    Map the lead's details

    Fill the contact fields by mapping values from the first module: each new entry arrives as a bundle, one item passed from one module to the next. The email is the usual starting point.

  4. 04

    Tag the new contact

    Add Add Tags after it. Map the contact produced by Create a Contact, then type the tag your sales team filters on, for instance the name of the form.

  5. 05

    Test with Run once

    Submit a test entry in your form, then click Run once. Read the bundles each module received, and check the new contact in Drift.

  6. 06

    Schedule and switch on

    Open the clock on the first module and keep the schedule, every 15 minutes by default, or shorten it on a paid plan. Switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each Drift module does

Drift gives you 24 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Drift1

Add Tags

Action

In Make“Adds tags to a specified contact.”

Puts one or more labels on a Drift contact you point to, so reps can filter and route that person without reading the whole history.

When to use it
right after a contact comes in from a campaign, to stamp it with the campaign name before sales sees it.
Watch out
the contact must already exist, so place Create a Contact or Get a Contact earlier and map its result.
Drift2

Create a Contact

Action

In Make“Creates a contact.”

Adds a new person to your Drift contacts from data that lives somewhere else: a form entry, a CRM record, a spreadsheet row.

When to use it
a lead is born outside Drift. Your team wants to recognize that person the very first time they open the chat widget on your site.
Watch out
to avoid duplicates, run Get a Contact first and add a filter so the scenario only creates people Drift does not know.
Drift3

Create a Conversation

Action

In Make“Creates a new conversation.”

Opens a fresh conversation in Drift from your scenario, so a request born in another tool lands where your team already answers chats.

When to use it
a customer fills a support form elsewhere and you want the thread to live in the Drift inbox, not in a separate mailbox.
Watch out
each run opens a new thread; test with Run once on a single bundle before switching the scenario on.
Drift4

Create/Edit/Delete a Message

Action

In Make“Creates, updates or deletes a message in a conversation.”

One module, three jobs: it writes a new message into an existing conversation, changes one, or removes one. You pick the job inside the module.

When to use it
posting an automatic note into a thread, for example the order status pulled from your shop, so the agent answers with the facts.
Watch out
the delete option removes the message for good, so double check which job the module is set to before a live run.
Drift5

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from your Drift base for good, the right move when a person's record should no longer exist anywhere in your tools.

When to use it
a deletion request arrives through your privacy form, and the same person has to disappear from Drift as well.
Watch out
a deleted contact does not come back. Map the ID from Get a Contact rather than typing it, and test on a dummy contact first.
Drift6

Delete a Tag

Action

In Make“Delete a tag from a specified contact.”

Takes a single label off a given contact and leaves the others in place, which keeps segments accurate as a lead moves along.

When to use it
a prospect becomes a customer in your billing tool, and the “trial” tag in Drift should go while the rest stays.
Watch out
to clear several labels at once, Delete Tags does it in one run and saves operations.
Drift7

Delete Tags

Action

In Make“Deletes tags from a specified contact.”

Strips several labels from one contact in a single step, a quicker reset than calling Delete a Tag once per label.

When to use it
a contact leaves a campaign or changes owner, and every tag tied to the old situation must go together.
Watch out
list the exact tags to remove; List Tags on that contact shows what is currently attached before you decide.
Drift8

Generate a Conversation Report

Action

In Make“Generates a conversation report.”

Asks Drift to build a report on your conversations, so the numbers reach a sheet or a dashboard without anyone exporting by hand.

When to use it
a support manager wants the report in a shared table after a campaign ends, next to results from other channels.
Watch out
the report comes back as data for the next module; add a spreadsheet or database module after it to keep it.
Drift9

Get a Conversation

Action

In Make“Retrieves a conversation.”

Fetches one Drift conversation you already have the reference for, with its details, ready to feed the rest of the scenario.

When to use it
a ticket in your help desk stores the Drift conversation ID, and you want its details copied onto the ticket.
Watch out
it reads one conversation only; to walk through many, start with List Conversations instead.
Drift10

Get a Conversation Attachment

Action

In Make“Retrieves a message attachment.”

Downloads a file a visitor or an agent shared in a chat, so it can be stored somewhere safer than the thread.

When to use it
customers send screenshots or invoices through Drift, and your team wants each file saved in the client folder of a storage app.
Watch out
on the Free plan Make handles files up to 5 MB, so heavier attachments call for a paid plan.
Drift11

Get Conversation Statuses

Action

In Make“Retrieves a count of the conversations according to their status.”

Returns how many conversations sit in each status, a quick snapshot of the workload waiting in Drift without opening the inbox.

When to use it
posting the count of open chats into a team channel when a shift starts, so everyone sees the backlog.
Watch out
you get counts, not the conversations themselves; pair it with List Conversations when you need the details.
Drift12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Drift API through the connection you already set up, which covers any endpoint the other modules leave out.

When to use it
you need a Drift feature that none of the 24 modules offers, and the Drift API documentation describes it.
Watch out
you write the path and the body yourself, so read the Drift API reference first and test with Run once.
Drift13

Post a Timeline Event

Action

In Make“Posts a timeline event to a contact's timeline.”

Writes an entry on a contact's timeline in Drift, so reps see what happened in other tools next to the chat history.

When to use it
a lead books a demo or pays an invoice elsewhere, and the rep should read it on the timeline before replying.
Watch out
the event is attached to one contact, so find that contact with Get a Contact earlier in the scenario.
Drift14

Unsubscribe a Contact

Action

In Make“Unsubscribes the contact from emails.”

Stops Drift from emailing a given person, applying an opt-out you collected somewhere else so they hear nothing more from you.

When to use it
someone clicks unsubscribe in your newsletter tool, and the same choice must hold in Drift to keep your lists consistent.
Watch out
this module only concerns emails; the contact stays in your Drift base; to remove the person entirely, use Delete a Contact.
Drift15

Update a Contact

Action

In Make“Updates a contact.”

Changes the details of an existing Drift contact, keeping what Drift knows in line with your CRM or billing tool.

When to use it
a lead gets a new job title or company in your CRM, and your chat team should see the fresh details.
Watch out
check the attribute names with List Attributes first, so values land in the right custom fields.
Drift16

Update a User

Action

In Make“Updates a user.”

Edits a Drift user, meaning a member of your own team rather than a visitor or a lead, from inside a scenario.

When to use it
your HR or scheduling tool records a change for an agent, and their Drift profile should follow without an admin stepping in.
Watch out
users are not contacts; get the right user ID from List Users or Get a User before mapping.
Drift17

Get a Contact

Search

In Make“Retrieve a contact using email or ID.”

Looks up a Drift contact by email or ID and returns what Drift stores about them, the usual first step before any change.

When to use it
checking whether a lead from your form already exists, then routing the scenario to Update a Contact or Create a Contact.
Watch out
as a search, it can return zero results; add a filter so the next module does not run on nothing.
Drift18

Get a User

Search

In Make“Retrieves an user.”

Reads one member of your Drift team and brings back their profile, handy when a scenario must name or notify the right agent.

When to use it
a conversation carries an assignee ID, and you want that agent's name in the message sent to your team chat.
Watch out
it needs the user reference; when you only know a name, start from List Users and filter.
Drift19

List Attributes

Search

In Make“Lists all contact attributes.”

Shows every contact attribute defined in your Drift account, custom ones included, so you know exactly what you can fill.

When to use it
while designing a sync with your CRM, to match each CRM field with the right Drift attribute before writing.
Watch out
it describes the attributes, not their values; read a contact with Get a Contact to see the values.
Drift20

List Bot Playbooks

Search

In Make“Retrieves currently enabled and active playbooks.”

Returns the bot playbooks currently enabled and active in Drift, the chat flows your bots run on your site.

When to use it
keeping an inventory of live playbooks in a shared table, so marketing knows which flows visitors can meet right now.
Watch out
disabled playbooks do not show up, so an empty result can simply mean nothing is switched on.
Drift21

List Conversation Messages

Search

In Make“Retrieves all messages of a conversation.”

Pulls every message of one conversation, each arriving as its own bundle, so the full exchange can be copied or analyzed.

When to use it
a chat turns into a support ticket, and the agent taking over needs the whole thread pasted into it.
Watch out
each message becomes a bundle and every later module runs once per bundle; add an aggregator to merge them into one text.
Drift22

List Conversations

Search

In Make“Retrieves all conversations.”

Retrieves your Drift conversations as a series of bundles, a starting point for archiving, reporting or follow-ups.

When to use it
building a table of every chat after a product launch, to see which questions came back most often.
Watch out
a large inbox means many bundles, and each module after it counts one operation per bundle on your plan.
Drift23

List Tags

Search

In Make“Retrieves a contact's tags.”

Gives the tags attached to one contact, which tells the scenario which segment that person belongs to before it acts.

When to use it
sending a lead to a different sales pipeline depending on whether it carries a “partner” or “enterprise” tag.
Watch out
it reads a single contact's tags, not the list of all tags in the account.
Drift24

List Users

Search

In Make“Retrieves the users in your organization.”

Returns the users of your Drift organization, meaning your agents and admins, as bundles you can filter or copy.

When to use it
matching Drift agents with people in your HR or planning tool, or finding the ID that Update a User needs.
Watch out
one bundle per user means one operation per user in every following module; filter early.
Need help

Need help automating Drift with Make?

A person reads every message.

FAQ

Drift and Make: common questions

01Is the Drift Make integration free?
Yes, Drift is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops each run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow runs of 40 minutes. Make counts usage in credits, one per module run. Your Drift subscription is a separate matter.
02What do you need to connect Drift to Make?
A Drift account and a Make account. The Make doc for Drift lists no prerequisite and no specific steps, so the standard flow applies: add a Drift module, click Create a connection, name it if you want, authorize Make on the Drift page or paste the key Drift provides, then click Save. That connection is then reused by all 24 Drift modules, so you only set it up once per account.
03Can Drift start a Make scenario in real time?
No, not on its own. Drift has no trigger module in Make, only 16 actions and 8 searches. A Drift scenario therefore starts in one of two ways: from a trigger of another app, such as a form tool or a CRM, or from the schedule on the first module, which runs every 15 minutes by default. If that other app has an instant trigger, it calls Make through a webhook as soon as something happens, and the Drift steps run right after.
04What if a Drift module you need is missing in Make?
Use Make an API Call. It sends any request to the Drift API with the connection you already created, so an endpoint missing from the list of modules stays reachable. You write the path and the body yourself from the Drift API documentation, then test with Run once. The Make doc lists no specific limit for Drift, so if a run fails, the error shown on the module is your starting point.
05Should you use Make or n8n for Drift?
It depends on the tool your team already uses. Drift exists in both: in Make as 24 modules, in n8n as a node. On the Make side, this page shows the full catalog, the connection and a first scenario, and Make an API Call covers the rest of the API. If your other automations already run in n8n, keeping Drift there avoids splitting your flows across two tools. The comparison page linked above goes through the criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations