ActionDripUpdated September 2026

How do I add a subscriber to Drip?

Short answer: You can create drip subscriber in Drip by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Drip Create Drip Subscriber action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Drip Subscriber in Drip — start free All 7 Drip actions

Create Drip Subscriber in Drip — 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
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.

Triggered by

Apps that pair well as the trigger for Create Drip Subscriber.

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

2 Google Sheets triggers

HubSpot → Drip

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Drip 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 Drip Subscriber support batch operations?

Run Create Drip Subscriber 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 Drip's rate limits.

More actions