ActionDriftUpdated September 2026

How do I fetch a Drift contact?

Short answer: You can get drift contact in Drift by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drift Get Drift Contact action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Drift Contact in Drift — start free All 4 Drift actions

Get Drift Contact 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.

Field	Type	Required	Description
Contact ID contact_id	string	Required	–

Sample request

{
  "contact_id": "{{trigger.contact_id}}"
}

Returns

{
  "data": {
    "id": 42,
    "attributes": {
      "name": "Jane Doe",
      "email": "jane@x.com"
    }
  }
}

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

Triggered by

Apps that pair well as the trigger for Get Drift Contact.

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

Google Sheets → Drift

2 Google Sheets triggers

HubSpot → Drift

18 HubSpot triggers

FAQ

Questions about Get Drift Contact.

What does the Get Drift Contact action do in Drift?

Returns a contact by ID or email with all attributes and conversation history references. The standard lookup before update or for enrichment patterns.

What inputs does Get Drift Contact require?

Required: Contact ID. 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 run history shows the failed step with its input and the error message Drift returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Drift Contact support batch operations?

Run Get Drift Contact inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Drift's rate limits.

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

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.

Action

Send Drift Message

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.

Get Drift Contact in Drift — start free