Tag Subscriber: Kit (ConvertKit) 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
Tag ID tag_id	string	Required	Tag ID. Example: 123456
Subscriber Email email	string	Required	Subscriber Email. e.g. "subscriber@example.com"

Sample request

{
  "tag_id": "e.g. 123456",
  "email": "subscriber@example.com"
}

Returns

{
  "subscription": {
    "id": 123,
    "subscriber": {
      "id": 456,
      "email_address": "subscriber@example.com"
    }
  }
}

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

FAQ

Questions about Tag Subscriber.

What does the Tag Subscriber action do in Kit (ConvertKit)?

Applies a tag to a subscriber by tag ID (not name). Tags drive Kit automation triggers and segmentation. For "engagement threshold crossed → tag for behavioural segment" workflows.

What inputs does Tag Subscriber require?

Required: Tag ID, Subscriber 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 Kit (ConvertKit) 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 Tag Subscriber support batch operations?

Yes. Run Tag Subscriber inside a Loop node to process arrays. Tiny Command handles Kit (ConvertKit)'s rate limits automatically so you don't have to throttle manually.

More actions