ConvertKit’s visual automation builder is one of the cleanest interfaces in email marketing. Drag a trigger, add conditions, branch subscribers into different paths—it feels intuitive until you hit about 40 nodes and the canvas starts choking.
If you’re running a content-driven business with segmented onboarding, product launches, or behaviour-based nurture sequences, you’ve probably felt this. The builder loads slowly. Clicks lag. Moving a single node can freeze your browser for three seconds.
This isn’t a bug—it’s a design tradeoff. Visual builders prioritise clarity over scalability, and ConvertKit’s canvas renders every node, connection, and conditional rule in real time. Past a certain threshold, that becomes expensive.
When the visual builder works perfectly
ConvertKit’s automation canvas excels at linear workflows with light branching. If you’re building a welcome sequence that forks based on one or two subscriber actions—clicked a link, purchased a product, tagged as interested in Topic A vs. Topic B—the visual layout makes logic auditable at a glance.
A typical high-performing automation in this range:
- One trigger (subscribed to a form)
- 3–5 emails spaced over 7–14 days
- 2–3 conditional branches based on clicks or tags
- 1–2 goal events that exit subscribers early
Total node count: 15–25. The canvas loads instantly. Changes save in under a second. You can onboard a VA or collaborator by screenshotting the flow.
Where it breaks down
Problems appear when you start layering complexity:
Nested conditionals. Branch on purchase status, then branch again on engagement level, then fork by content preference. Each layer doubles your node count. A four-level decision tree can balloon to 60+ nodes before you’ve sent ten emails.
Event-based re-entry. If your automation triggers on “tag added” and you’re using tags liberally across your system—post interactions, product interest signals, engagement scores—subscribers can enter the same automation multiple times. ConvertKit handles this, but visualising those re-entry paths on a single canvas creates spaghetti.
Time delays at scale. ConvertKit’s visual builder treats every wait period as a discrete node. If you’re spacing emails across 90 days with variable delays based on activity, you’re adding 10–15 wait nodes just for pacing. Combine that with branching and you’re over 50 nodes easily.
At that scale, the canvas becomes a liability. Loading takes 8–12 seconds. Dragging nodes to reorganise triggers a visual refresh that can pause your browser. Editing a condition three layers deep requires zooming, panning, and waiting for the interface to catch up.
The workaround: split automations and use sequences
ConvertKit offers two tools for sending automated emails: visual automations and sequences (the older, list-based drip feature). Most operators default to automations because the interface is newer and more flexible. But sequences are faster, simpler to manage, and handle high-volume evergreen content better.
Use sequences for linear email courses or onboarding. If your workflow is mostly “send email 1, wait 2 days, send email 2, wait 3 days…” with minimal branching, a sequence is faster to build and never lags. You lose conditional logic, but you gain speed and reliability.
Use automations for decision points, then hand off to sequences. Build a short automation (under 20 nodes) that handles the initial triage—tag based on link clicks, segment by purchase history, apply a custom field. Then use an action step to subscribe users to the appropriate sequence. The sequence handles delivery; the automation handles routing.
This hybrid approach keeps individual automations lightweight and makes debugging easier. If a subscriber isn’t receiving emails, you can check the sequence separately from the routing logic.
Split large automations by goal or time horizon. Instead of one 60-node “master onboarding” automation, build three:
- Days 1–7: Welcome, core content, initial segmentation
- Days 8–30: Nurture based on engagement tags
- Days 31+: Long-term re-engagement or upsell
Each automation stays under 25 nodes. Subscribers flow from one to the next via tags or custom field updates. You lose the single-canvas overview, but you gain maintainability.
One non-obvious tip: name every node
ConvertKit lets you label individual automation nodes with custom names. Most people skip this. Don’t.
When you’re troubleshooting why a subscriber didn’t receive an email, ConvertKit’s activity log shows which automation nodes they passed through—but only by name. If all your conditional branches are labelled “Condition” and all your emails are “Email,” the log is useless.
Name every node descriptively: “Check if purchased Product A,” “Send case study email—Topic B,” “Wait 3 days after click.” It takes an extra 10 seconds per node when you’re building, but it saves 10 minutes every time you debug.
If you’re running ConvertKit automations that feel sluggish or impossible to audit, the problem isn’t the tool—it’s the architecture. Keep individual automations under 30 nodes, offload linear sequences to the sequence builder, and split complex workflows by stage. The visual builder works best when you don’t ask it to do everything at once.
What’s the most complex automation you’ve built? Hit reply and let me know where it broke—I’ll feature anonymised examples in a future roundup.