ActionDriftUpdated September 2026
How do I add a Drift contact?
Short answer: You can create drift contact in Drift by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drift Create 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.
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 |
|---|---|---|---|
Name name | string | Required | Name |
Sample request
{"name": "{{trigger.name}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Create Drift Contact.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Drift Contact.
What does the Create Drift Contact action do in Drift?
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.
What inputs does Create Drift Contact require?
Required: Name. 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 Create Drift Contact support batch operations?
Run Create 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
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.
ActionList Drift Conversations
Paginated conversations with filters by status and assignee. Useful for triage workflows or for "all unassigned conversations from last hour" capacity awareness.
ActionSend 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.