ActionDriftUpdated May 2026

How do I fetch a Drift contact?

Short answer: Drop the "Drift → Get Drift Contact" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 4 Drift actions

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 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 Get Drift Contact support batch operations?

Yes. Run Get Drift Contact inside a Loop node to process arrays. Tiny Command handles Drift's rate limits automatically so you don't have to throttle manually.

More actions