Drift

Drift

· #366 most-used

Turn every site visitor into a named conversation

CRMSalesMarketingCommunicationSchedulingAutomation

Drift (now part of Salesloft) is a conversational marketing and sales platform that replaces static forms with live chat, AI bots, meeting scheduling, and ABM account intelligence. Connect it to Actionist and your agents can create and enrich contacts, read full conversation threads, assign chats to the right rep, tag leads for playbook targeting, and react to meetings booked — all without a human touching the inbox. The payoff: high-intent visitors reach a rep in seconds, not days.

Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Automating Drift contact enrichment, conversation assignment, meeting logging, and post-chat CRM updates cuts the triage and data-entry work that otherwise occupies the first hour of every revenue rep's day.

Schedule

What your Drift agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
WedFri
Wed
Thu
Fri
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Drift × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
9Apps spanned
~59 hrsSaved / week
6Personas served
For customer success
Featured4 apps

New Drift chat to onboarded customer

When a high-intent visitor books a meeting via Drift chat, your agent reads their full conversation history, creates a personalised Drift contact with enriched firmographics, notifies the CSM in Slack with a three-bullet brief, and drops a kickoff calendar event — all before the rep has finished their coffee. Every new customer arrives with a warm handoff, not a cold introduction.

~11 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a visitor books a meeting via a Drift chat conversation
Result
Update contact with onboarding_started attributePost CSM handoff brief with conversation summaryCreate kickoff call event with agenda and Drift context
The win
Saved per run
45 min
Runs / week
~15×
Zero dropped handoffs
Driven byCustomer Support Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    18 min / week
    Manual chat triage

    Reps scan the Drift inbox each morning to find unassigned conversations and manually route them to the right AE by territory.

    Sales Agent
    0 min
    Agent routes on open

    The moment a conversation starts, the agent reads the account domain, matches it to territory rules, and assigns it to the named AE — before the rep has opened their laptop.

  • Marketing
    13 min / week
    ABM alert copy-paste

    Marketing manually exports Drift account visit data and pastes it into a spreadsheet for the ABM team's weekly review.

    Marketing Agent
    0 min
    Agent logs visits live

    Every target account visit triggers the agent to log company, pages viewed, and intent score to the ABM sheet in real time — the weekly review is already populated before the meeting starts.

  • Customer Support
    18 min / week
    Handoff brief writing

    Support reps read the full Drift chat history and manually type a summary before picking up a handed-off conversation from the bot.

    Customer Support Agent
    0 min
    Agent writes the brief

    When the bot hands off, the agent reads the thread, writes a three-bullet summary, and posts it in the rep's Slack DM — the rep replies with full context in seconds.

  • Human Resources
    7 min / week
    Candidate chat logging

    HR coordinators copy candidate chat conversations from Drift into the ATS manually to maintain a record of initial touchpoints.

    Human Resources Agent
    0 min
    Agent syncs transcript

    After a candidate chat closes, the agent fetches the conversation messages and writes a structured note to the ATS contact — no copy-paste, no lost context.

  • Finance
    13 min / week
    Chat revenue attribution

    Finance manually cross-references Drift conversion events with CRM deals each month to calculate chat-assisted pipeline, taking 30–60 minutes per report.

    Finance Agent
    0 min
    Agent tags at conversion

    The moment a lead converts via chat, the agent stamps the CRM deal with 'drift-assisted' attribution and the conversation ID — the monthly revenue report is a one-click export.

  • Operations
    25 min / week
    Queue depth monitoring

    Ops managers check the Drift inbox manually every hour to spot queue build-up and manually reassign conversations when a rep is at capacity.

    Operations Agent
    0 min
    Agent auto-balances load

    When unassigned conversations exceed the threshold, the agent lists open chats, checks rep capacity, and redistributes — response SLA stays under five minutes with no manager intervention.

  • Legal
    6 min / week
    GDPR erasure checks

    Legal manually searches Drift for a contact by email on each data erasure request and deletes the record after verifying the request is authenticated.

    Legal Agent
    0 min
    Agent executes erasure

    When a verified erasure request arrives, the agent looks up the contact in Drift by email and deletes the record within the legally required window — no manual search, no missed records.

+ 100s of other Drift automations
Average monthly
10 hrs / person / month
Average monthly
10 hrs / person / month
Calculator

Calculate what your team saves

Team size
10 person
Hourly rate
$20 / hr
Hours saved / week
25
Hours saved / year
1,250
Annual ROI
$25,000

Based on Drift's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Drift into Actionist

Pick the connection method that suits your environment.

The fastest path to Drift automation. Install Drift's MCP server in one click and Actionist connects via a permissioned OAuth handshake — contacts, conversations, and account data are all live with zero token management on your end.

1
Open the Apps tab

Find Drift in the Apps library and click Connect. MCP is selected by default.

2
Authorise in Drift

A Drift OAuth window opens — sign in with your Drift account and grant Actionist the requested scopes (read contacts, read/write conversations, read accounts). Enterprise SSO is supported.

3
Test the connection

Actionist runs a read-only call to verify the handshake. You're ready.

Actions

15 action your agent can call

Read and write operations available to your Actionist agent.

Triggers

7 event your agent can react to

Events your agent watches for, and the actions it kicks off in response.

Skills

Skills that pair with Drift

Reusable agent skills that work well alongside this app.

No paired skills curated yet. Add this app to your agent to discover what fits.
MCP servers

MCP servers that work with Drift

Connect Actionist to MCP servers built for or around this app.

No MCP servers indexed for this app yet.
FAQs

Questions about Drift + Actionist

How do I connect Drift to Actionist?
Open the Apps tab, find Drift, and click Connect. The default method is MCP, which walks you through a Drift OAuth flow — grant the required scopes and Actionist verifies the connection with a read-only test call. If you prefer a personal access token, switch to the API key method and paste the token from your Drift developer app settings. Either way, you're connected in under two minutes.
What permissions does Actionist need from my Drift account?
Via OAuth (MCP), Actionist requests read access to contacts and accounts, and read/write access to conversations. It never requests admin or billing scopes. Via API token, the token inherits the scopes of the Drift developer app you created — scope it to contact.read, contact.write, conversation.read, and conversation.write for the actions in this library. You can revoke either at any time from Drift's app settings.
Can I combine Drift with other apps in a single agent workflow?
Yes — Drift is most powerful as part of a chain. A common pattern: a visitor books a meeting via Drift (trigger), the agent reads the conversation thread (Drift), creates a deal in HubSpot, posts a Slack summary to the AE, and drops a kickoff event in Google Calendar — all in one workflow run. Any app in your Actionist library can be combined with Drift's actions and triggers.
What are the most useful Drift automations to start with?
Start with conversation assignment: when a new chat starts, the agent reads the visitor's account domain and routes to the right rep instantly. Second, set up post-conversion CRM sync — when a lead converts via chat, write the deal to HubSpot automatically. Third, use the 'Meeting booked from chat' trigger to fire a pre-call research brief to the rep. These three cover 80% of the manual Drift work most revenue teams do every day.
How do I avoid a trigger loop where the agent's own actions re-fire a trigger?
The safest guard is to add a provenance check: when the agent creates or updates a contact, it sets a custom attribute like 'actionist_updated=true'. Any trigger-based workflow should filter out records where that attribute is already set to true. For conversation triggers, use Drift's sender filter to exclude messages sent by your API credentials. These two checks prevent the agent from triggering itself on its own writes.
Does Actionist support Drift's ABM and account-level data?
Yes. The 'Get account details' action fetches Drift's ABM account object — firmographics, engagement score, and visitor activity by domain. The 'Visitor identified as target account' trigger fires when Drift's ABM engine matches a visitor to your named account list. Use these together to build workflows that alert the AE the moment a target account hits your site, with full account context included in the notification.
Can the agent send messages into an existing Drift conversation?
Yes — the 'Send chat message' action posts into an existing conversation thread on behalf of a team member. Use it for proactive outreach: trial day-3 nudges, renewal reminders, or post-meeting follow-ups sent inside the same Drift thread where the relationship started. The message appears as coming from whichever team member's token you use for the connection, so it looks native.
What happens if Drift's API rate limit is hit during a bulk operation?
Drift's REST API enforces rate limits per token (typically 300 requests per minute for standard plans). If your agent is processing a large contact list or conversation batch, build in a delay between calls or use Actionist's retry logic with exponential backoff. For high-volume operations — syncing thousands of contacts — run them on an off-peak schedule (e.g. Sunday at 2 AM) to avoid hitting limits during business hours when live chat traffic is active.