ConvertKit offers two ways to build automations: the visual automation builder, which looks like a flowchart, and the rule-based editor, which reads like a spreadsheet of conditions. They produce identical results—subscribers get tagged, moved between sequences, or removed from lists based on triggers you define—but they’re built for different kinds of thinking.
Most operators default to whichever interface they first learned. That costs time. Each editor has situations where it’s faster, clearer, and less error-prone than the other.
Visual builder: when branches multiply
The visual automation builder excels when you need to see multiple paths diverging from a single trigger. If a subscriber opens an email, clicks a specific link, and has a tag, send them down path A. If they open but don’t click, path B. If they ignore it entirely, path C after 72 hours.
This is hard to parse in a list of rules. The visual editor makes it obvious: you see the fork, the wait periods, and where paths rejoin or terminate. When you’re debugging, you can trace a subscriber’s journey by eye instead of reading line-by-line conditional logic.
The visual builder also handles time-based delays more intuitively. You drag a “Wait” block between actions and set the interval. In the rule editor, you’re specifying when conditions are checked, which requires you to think about the automation’s internal clock rather than the subscriber’s experience.
Where it breaks down: complex tag logic. If you’re checking for the presence or absence of five tags before taking action, the visual builder forces you to nest condition blocks in ways that become unreadable fast. You end up with a spiderweb.
Rule editor: when conditions stack
The rule-based editor is a vertical list of “if this, then that” statements. It’s less visual, but it’s faster to write and easier to audit when you’re working with multiple overlapping conditions.
Example: you want to tag subscribers who’ve been on your list for more than 30 days, opened at least three emails in the last two weeks, clicked a link in your last broadcast, and don’t already have a “high-engagement” tag. In the visual builder, that’s four nested condition blocks. In the rule editor, it’s four lines with AND logic. You can scan it in three seconds.
The rule editor also makes bulk edits faster. If you need to change a tag name across ten automations, you can copy the rule set into a text editor, find-and-replace, and paste it back. The visual builder requires clicking into each block individually.
Non-obvious tip: use the rule editor to prototype, then rebuild in the visual editor if you need to present it to a client or team member. Rules are faster to write; visuals are faster to explain.
What both editors hide
Neither interface shows you automation timing conflicts. If two automations try to add conflicting tags to the same subscriber at the same moment, ConvertKit processes them in the order they were created—not the order you’d expect from looking at the flowchart or rule list.
You won’t know this happened unless you manually check the subscriber’s activity log. There’s no error message, no warning in the editor. The automation runs; one tag wins. If you’re using tags to trigger downstream actions (like segment splits or sequence enrollment), this silent conflict can route subscribers incorrectly.
The workaround: add a one-minute delay between automations that might overlap. It’s invisible to the subscriber, but it forces ConvertKit to process actions sequentially.
Which to use today
If you’re building a welcome sequence with multiple paths based on engagement, start in the visual builder. If you’re setting up a tagging system based on purchase history or content preferences, use the rule editor. If you’re not sure, default to rules—they’re faster to write and easier to fix when you realize you misconfigured something.
And if you’re managing automations for clients or a team, keep a text file with a plain-English description of what each automation does. Neither editor exports documentation, and six months from now, you won’t remember why you added that three-day wait or what “engaged-2026-Q3” was supposed to mean.
Got a question about how your email platform handles something specific? Reply and tell us—we’ll dig into it and write it up if it’s something other operators are hitting too.