The flow
Starts it 1Service 14
The steps in the order they run, from what starts it.
- 1Create a custom fieldConvert Kit ToolService
- 2Delete a custom fieldConvert Kit ToolService
- 3Get many custom fieldsConvert Kit ToolService
- 4Update a custom fieldConvert Kit ToolService
- 5Add a subscriberConvert Kit ToolService
- 6Get many formsConvert Kit ToolService
- 7Get all subscriptionsConvert Kit ToolService
- 8Get many sequencesConvert Kit ToolService
- 9Get all subscriptions to a sequenceConvert Kit ToolService
- 10Create a tagConvert Kit ToolService
- 11Get many tagsConvert Kit ToolService
- 12Add a tag to a subscriberConvert Kit ToolService
- 13Get many tag subscriptionsConvert Kit ToolService
- 14Delete a tag from a subscriberConvert Kit ToolService
- 15ConvertKit Tool MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 16
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Before you run itNothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.