Start free
ActionDriftUpdated June 2026

How do I send a Drift message?

Short answer: You can send drift message in Drift by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drift Send Drift Message action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Send Drift Message in Drift — start free All 4 Drift actions
Send Drift Message in Drift — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Conversation ID
conversation_id
stringRequiredThe Conversation ID assigned by Drift. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Body
body
stringRequiredMessage body content. Plain text unless the API specifies HTML/markdown.
Type
type
optionsOptional–
Sample request
{
  "conversation_id": "{{trigger.conversation_id}}",
  "body": "e.g. Hi there, thanks for reaching out.",
  "type": "{{trigger.type}}"
}
Returns
{
  "data": {
    "id": 9999,
    "body": "Thanks"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Send Drift Message.

Any of these apps can fire this action as part of a workflow.

Gmail → Drift
1 Gmail triggers
Slack → Drift
13 Slack triggers
Google Sheets → Drift
2 Google Sheets triggers
HubSpot → Drift
18 HubSpot triggers
FAQ

Questions about Send Drift Message.

What does the Send Drift Message action do in Drift?
Posts a message into a specific conversation as the current Drift user. For "AI-drafted response → reviewed by rep → fire via Drift" workflows or for automated replies on routine ticket types.
What inputs does Send Drift Message require?
Required: Conversation ID, Body. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Drift returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Send Drift Message support batch operations?
Yes. Run Send Drift Message inside a Loop node to process arrays. TinyCommand handles Drift's rate limits automatically so you don't have to throttle manually.
More actions

Other Drift actions.

Action
Create Drift Contact
Upserts a contact (Drift dedupes on email) with name, attributes, custom fields. For "sync CRM lead into Drift so the bot has full context when they next chat" workflows.
Action
Get Drift Contact
Returns a contact by ID or email with all attributes and conversation history references. The standard lookup before update or for enrichment patterns.
Action
List Drift Conversations
Paginated conversations with filters by status and assignee. Useful for triage workflows or for "all unassigned conversations from last hour" capacity awareness.
Send Drift Message in Drift — start free