ActionKit (ConvertKit)Updated September 2026

How do I tag a Kit subscriber?

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

Tag Subscriber in Kit (ConvertKit) — start free All 4 Kit (ConvertKit) actions

Tag Subscriber in Kit (ConvertKit) — 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
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.

Triggered by

Apps that pair well as the trigger for Tag Subscriber.

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

Gmail → Kit (ConvertKit)

1 Gmail triggers

Slack → Kit (ConvertKit)

13 Slack triggers

Google Sheets → Kit (ConvertKit)

2 Google Sheets triggers

HubSpot → Kit (ConvertKit)

18 HubSpot triggers

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

Run Tag 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 Kit (ConvertKit)'s rate limits.

More actions

Other Kit (ConvertKit) actions.

Action

Add Subscriber

Adds a subscriber with email, name, custom fields, optional starting tags. Respects the list's configured double-opt-in setting. For "form submission outside Kit → push to Kit list" sync workflows.

Action

Add Subscriber to Sequence

Adds an existing subscriber to a Kit evergreen sequence (multi-email automation). For "lead reached qualification threshold → enroll in the nurture sequence" cross-app workflows.

Action

List Kit Tags

Returns every tag in the account with subscriber counts. Useful for resolving tag IDs at workflow-build time (Tag Subscriber takes numeric IDs, not names) and for tag-inventory audits.

Tag Subscriber in Kit (ConvertKit) — start free