Add Subscriber: Zoho Campaigns 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
Mailing List Key listkey	string	Required	Mailing List Key. Example: abc123def456
Contact Email email	string	Required	Contact Email. e.g. "subscriber@example.com"
First Name first_name	string	Optional	First Name. e.g. "John"
Last Name last_name	string	Optional	Last Name. e.g. "Doe"

Sample request

{
  "listkey": "e.g. abc123def456",
  "email": "subscriber@example.com",
  "first_name": "John",
  "last_name": "Doe"
}

Returns

{
  "response": {
    "status": "success",
    "message": "Contact added to the list"
  }
}

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

FAQ

Questions about Add Subscriber.

What does the Add Subscriber action do in Zoho Campaigns?

Subscribes a contact (email + merge fields) to a Zoho Campaigns mailing list. Used to push form fills, customer signups, or CRM segments into your email program.

What inputs does Add Subscriber require?

Required: Mailing List Key, Contact 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 Zoho Campaigns 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 Add Subscriber support batch operations?

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

More actions