Rename Tag
convertkit.update_tag
ActionEmailconnection required
Calls the ConvertKit API with the connection's credentials.
Rename an existing tag; it keeps its id and all of its subscribers.
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
Configuration
2 fields, 2 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 rename. | string | Yes | — | — | 218 |
name The new tag name. Kit refuses a blank name or one that duplicates another tag. | string | Yes | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"tag_id": "218"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
tag The tag record Kit returned, unchanged. | object | — |
id The tag's Kit id. | number | — |
name The tag's new name. | string | — |
{
"id": 0,
"name": "",
"tag": {}
}See Rename Tag run in a workflow.
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.