Short answer: You can add subscriber to sequence in Kit (ConvertKit) by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Kit (ConvertKit) Add Subscriber to Sequence action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Sequence ID sequence_id | string | Required | Sequence ID. Example: 789 |
Subscriber Email email | string | Required | Subscriber Email. e.g. "subscriber@example.com" |
First Name first_name | string | Optional | First Name. e.g. "John" |
{"sequence_id": "e.g. 789","email": "subscriber@example.com","first_name": "John"}
{"subscription": {"id": 123,"subscriber": {"id": 456,"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.