Bulk Create Tags

convertkit.bulk_create_tags
ActionEmailconnection required

Calls the ConvertKit API with the connection's credentials.

Create many tags in one call, returning the tags Kit created or matched and any it refused.

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, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
names
The tag names to create: a JSON array, or one comma-separated string.
arrayYes—array of string["Webinar signup","Trial started"]
callback_url
Webhook Kit posts the outcome to when the batch is too large to process synchronously (more than 100 items).
stringNo—url format—

Example configuration

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

{
  "names": [
    "Webinar signup",
    "Trial started"
  ]
}

Output

One shape.

result

FieldTypeExample
items
The records Kit created or updated, when it answered synchronously.
array—
failures
One entry per item Kit refused, each carrying its own 'errors' list and the item that caused them.
array—
succeeded
How many items Kit reported as written.
number—
failed
How many items Kit refused.
number—
requested
How many items this node sent.
number—
queued
True when the batch was larger than Kit's synchronous limit of 100, so Kit accepted it for background processing and returned no per-item result; the outcome arrives at 'callback_url'.
boolean—
{
  "failed": 0,
  "failures": [],
  "items": [],
  "queued": false,
  "requested": 0,
  "succeeded": 0
}

Notes

  • Kit creates 100 tags or fewer synchronously; a larger batch comes back with 'queued' true and is processed in the background.

See Bulk Create Tags 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.