ConvertKit gives you two ways to automate what happens after someone subscribes, clicks a link, or buys a product: the visual automation builder and the older rules-based system. They look different, they feel different, and they solve different problems.
If you’ve ever clicked into Automations and felt paralyzed by the blank canvas—or built a simple rule and wondered why everyone raves about visual workflows—you’re not alone. The platform doesn’t make it obvious when to use which, and picking wrong costs you time or flexibility down the road.
Here’s how to decide.
What each one actually does
The visual automation builder is the flowchart interface. You drag triggers, conditions, actions, and delays onto a canvas. It handles multi-step sequences, conditional logic, tagging, field updates, and webhook calls. You can see the whole journey at a glance.
The rules system is text-based and hidden under Settings → Rules. Each rule is a single if-this-then-that statement: “If someone subscribes to Form A, tag them with Lead Magnet B.” No branching, no delays, no visual feedback.
Both run in the background. Both fire instantly. But they’re built for different levels of complexity.
When to use the visual builder
Use the visual automation builder when your subscriber journey has more than one step, or when the next action depends on what someone does (or doesn’t do).
Examples where it shines:
- Onboarding sequences with conditional branches based on link clicks or form submissions
- Lead nurture flows that tag people differently depending on which resource they download
- Product launch sequences that change behavior based on purchase status
- Re-engagement campaigns triggered by inactivity, with different paths for openers vs. non-openers
The visual builder also makes debugging easier. You can see where subscribers are in the flow, spot bottlenecks, and identify where people drop off. If you’re running anything more complex than a single tag or email, the canvas pays for itself in clarity.
One non-obvious tip: use the Wait Until condition instead of fixed delays when timing matters. Instead of “wait 3 days,” set “wait until tag is added” or “wait until custom field changes.” It keeps automations responsive to real behavior, not arbitrary calendars.
When rules are faster (and safer)
Rules are better when you need a single, permanent action that should never change based on subscriber behavior.
Use rules for:
- Auto-tagging every new subscriber to a specific form
- Assigning a custom field (like “source” or “signup date”) the moment someone joins
- Moving subscribers between sequences when they complete a purchase
- Unsubscribing people from a broadcast tag when they click an opt-out link
Rules execute faster because there’s no flowchart to traverse. They’re also harder to accidentally break—there’s no risk of pausing the wrong branch or deleting a connector by mistake.
The biggest advantage: rules don’t require you to “start” subscribers. Visual automations only affect people who enter after you publish. Rules apply to everyone who meets the condition, past or future, unless you explicitly turn them off.
The hybrid approach most operators miss
You don’t have to choose. The most reliable setups use rules for foundational tagging and field assignment, then use visual automations for behavior-based sequences.
Example: a rule tags every new subscriber with their lead magnet name. A visual automation checks that tag, then sends a welcome sequence tailored to what they downloaded. The rule ensures no one slips through; the automation handles nuance.
This also future-proofs your setup. If you later want to add a branch for people who clicked a specific link, you’re editing an automation—not rewriting a dozen rules.
One warning: don’t duplicate logic across both systems. If a rule and an automation both try to add the same tag based on the same trigger, you’ll get double-fires and confusing analytics. Pick one place for each action.
Where most people get stuck
The most common mistake is building a visual automation when a rule would’ve been cleaner—usually because the visual builder feels more “powerful.”
If your automation is a straight line with no branches, no delays, and no conditions, it’s probably a rule. Save the canvas for when you actually need decision trees.
The second mistake: not testing both. ConvertKit lets you preview automations, but it doesn’t simulate real subscriber movement. Before you publish, manually trigger the flow with a test subscriber and confirm every tag, email, and field change fires as expected.
Want more breakdowns like this? One Two Three Send covers the tools and tactics solo operators actually use—no fluff, no affiliate spam. Subscribe for one article like this every week.
