Create Drip Subscriber: Drip action

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
Email email	string	Required	Email. e.g. "user@example.com"
First Name first_name	string	Optional	First Name. e.g. "John"
Last Name last_name	string	Optional	Last Name. e.g. "Doe"
Tags tags	string	Optional	Comma-separated tags

Sample request

{
  "email": "user@example.com",
  "first_name": "John",
  "last_name": "Doe",
  "tags": "e.g. customer, vip"
}

Returns

{
  "subscribers": [
    {
      "id": "abc123",
      "email": "user@example.com",
      "first_name": "John"
    }
  ]
}

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

FAQ

Questions about Create Drip Subscriber.

What does the Create Drip Subscriber action do in Drip?

Creates or upserts a subscriber by email with custom fields, tags, and starting campaign. The base hook for "form submission → push to Drip" sync workflows in e-commerce email programs.

What inputs does Create Drip Subscriber require?

Required: Email. 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 Drip 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 Create Drip Subscriber support batch operations?

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

More actions