Tag Subscriber

convertkit.tag_subscriber

ActionEmailconnection required

Calls the ConvertKit API with the connection's credentials.

Apply a tag to a subscriber, identified either by their Kit id or by their email address.

Connection

Required: Yes — the node will not save without one
Auth type: API key
Providers: ConvertKit
Secret shape: the v4 API key, or {"api_key": "…"}, or {"access_token": "…"} for OAuth
Config it needs: base_url
Resolved by: config.connection_id, else node.connection_id

3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

Field	Type	Required	Default	Constraints	Example
tag_id The Kit id of the tag to apply.	string	Yes	—	—	218
subscriber_id The subscriber's Kit id. Give this or 'email_address'.	string	No	—	—	1258
email_address The subscriber's email address, when you do not hold their Kit id.	string	No	—	email format	alice@example.com

Every value below is the contract’s own example or default — nothing invented.

{
  "email_address": "alice@example.com",
  "subscriber_id": "1258",
  "tag_id": "218"
}

One shape.

Field	Type	Example
subscriber The subscriber record Kit returned, unchanged.	object	—
id The subscriber's Kit id.	number	—
email_address The subscriber's email address.	string	—
state active, cancelled, bounced, complained or inactive.	string	—
warnings Custom field keys Kit did not recognise and therefore ignored; empty on a fully applied write.	array	—

{
  "email_address": "",
  "id": 0,
  "state": "",
  "subscriber": {},
  "warnings": []
}

The subscriber must already exist; tagging an unknown address is a 404, not a create.

In a technical demo we add the ConvertKit connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.