ConvertKit gives you two distinct ways to automate email flows: visual automations and rule-based sequences. They look similar in the dashboard, but they’re built on different engines, trigger differently, and impose different constraints on what you can build.
If you’ve been using one without understanding the other, you’ve probably hit a wall trying to do something that feels simple but won’t work in the tool you picked. Here’s how they differ, when to use each, and one non-obvious trick that makes visual automations significantly more powerful.
Visual automations: event-driven, branch-heavy
Visual automations are ConvertKit’s newer system. They trigger based on events—someone subscribes to a form, clicks a link, makes a purchase, or gets tagged. You drag blocks onto a canvas, connect them with lines, and build conditional branches.
The engine checks conditions in real time. If a subscriber meets the criteria for a branch, they move down that path immediately. If they don’t, they skip it. You can nest conditions, add delays, and split paths based on behavior.
Visual automations handle complexity well. You can build onboarding sequences that fork based on which lead magnet someone downloaded, re-engagement flows that pause if someone opens an email, or post-purchase sequences that change based on product type.
But they have two practical limits. First, each automation can have a maximum of 50 steps. That sounds like a lot until you realize that every condition, delay, and email counts as a step. A moderately complex flow hits that ceiling fast. Second, visual automations don’t let you manually add subscribers in bulk. They only trigger from events. If you want to enroll 200 people at once, you need a workaround—usually tagging them, then using the tag as a trigger.
Rule-based sequences: linear, broadcast-style
Sequences are ConvertKit’s original automation system. They’re linear: a list of emails sent in order, each after a set delay. You write the emails, set the intervals, and subscribers move through from top to bottom.
Sequences trigger when you manually add someone or when an automation rule enrolls them. You can set rules like “subscribe to this sequence when someone joins Form A” or “subscribe when someone is tagged with X.” Once someone’s in, they get every email in order unless you manually remove them or they unsubscribe.
Sequences are simple and predictable. They work well for drip courses, evergreen onboarding, or any flow where everyone gets the same emails in the same order. But they don’t branch. If you need conditional logic—send Email A to buyers and Email B to non-buyers—you can’t do it inside a sequence. You’d need to split it into two sequences and use tags or visual automations to route people correctly.
One advantage: sequences let you bulk-add subscribers. You can upload a CSV or select a segment and enroll hundreds of people at once. Visual automations can’t do that without a tag-based trigger step.
When each system breaks down
Visual automations struggle with scale in two ways. The 50-step limit forces you to split large flows into multiple automations, which means managing handoffs between them—usually with tags. And because they’re event-driven, debugging gets messy when subscribers don’t move as expected. You’ll find yourself checking event logs to see if a link click registered or if a tag applied at the right time.
Sequences struggle with personalization. If you want to send different emails based on behavior mid-flow, you can’t. You’d need to pause the sequence, tag people based on their actions, and move them into a different sequence or visual automation. That’s clunky and introduces delays.
Another thing: sequences don’t let you A/B test individual emails inside the sequence. You can A/B test the first email when someone subscribes, but not Email 3 or Email 7. Visual automations let you split paths and send different emails to different groups, which functions as a manual A/B test if you’re willing to analyze the results yourself.
The non-obvious trick: hybrid workflows
The most powerful ConvertKit setups use both systems together. Start with a sequence for the linear parts—your core onboarding emails that everyone should get. Then use visual automations to handle the branching logic.
For example: run a 5-email welcome sequence. At the end, tag people based on whether they’ve opened or clicked. Then trigger a visual automation off those tags. If someone engaged, send them a product pitch. If they didn’t, send a re-engagement email or move them to a different nurture track.
This keeps your sequences simple and your visual automations focused. You’re not trying to cram everything into one system or hitting step limits because you’re splitting the work across tools that each do one thing well.
One more thing: if you’re using ConvertKit’s Creator or Creator Pro plan, you get access to link triggers in visual automations. That means you can embed a URL in any email—even a broadcast or a sequence email—and trigger a visual automation when someone clicks it. That’s how you add conditional logic to sequences without rebuilding them as visual automations.
If you’re running ConvertKit and haven’t audited which system you’re using for each flow, do it this week. Chances are you’re using sequences for something that should be a visual automation, or you’ve built a visual automation that’s unnecessarily complex because it’s trying to do what a sequence handles better.
And if you’re just starting out, default to sequences for anything linear and predictable. Save visual automations for the moments where behavior actually matters.