Short answer: Drop the "Kit (ConvertKit) → Add Subscriber" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email email_address | string | Required | Email. e.g. "subscriber@example.com" |
First Name first_name | string | Optional | First Name. e.g. "John" |
State state | options | Optional | State. Options: Active, Inactive |
Tag IDs tags | string | Optional | Comma-separated tag IDs to apply |
{"email_address": "subscriber@example.com","first_name": "John","state": "{{trigger.state}}","tags": "e.g. 123, 456"}
{"subscriber": {"id": 12345,"state": "active","created_at": "2025-01-15T12:00:00.000Z","first_name": "John","email_address": "subscriber@example.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.