ConvertKit has two automation editors—here's which to use
The café near Hoxton Square smells like burnt filter coffee and laptop heat this morning, and every second table has a Notion tab open next to a ConvertKit dashboard. Someone just asked the barista if the Wi-Fi can handle a Zoom call. It cannot.
ConvertKit has two automation editors and most operators pick the wrong one
The visual builder and the rule-based editor do identical work, but one makes debugging a nightmare.
ConvertKit ships two ways to build the same automation: a drag-and-drop visual canvas with boxes and arrows, and a text-based rule editor that looks like a settings panel from 2011. Both trigger sequences, apply tags, and segment subscribers. Both cost the same. But they fail differently, and that difference matters when you’re troubleshooting a broken funnel at 11pm.
The visual editor wins when you’re mapping a new automation from scratch or handing off workflows to a VA who doesn’t live in ConvertKit daily. It shows the whole path on one screen, makes branching logic obvious, and catches some errors before you publish. The rule editor wins when you’re cloning existing automations, debugging why a tag didn’t apply, or managing more than a dozen steps—because the visual canvas turns into spaghetti once you pass fifteen nodes, and scrolling a two-dimensional grid to find the one broken condition is slower than scanning a vertical list.
Most operators default to whichever editor they opened first and never switch. That’s leaving time on the table. The visual editor is better for building, the rule editor is better for fixing, and knowing when to toggle between them saves you an hour every time you need to trace why a subscriber got tagged twice or missed a sequence entirely.
TACTIC
Mailchimp segments don’t refresh instantly—here’s the lag
You update a custom field, rebuild a segment filter, and expect Mailchimp to reflect the change in seconds. It doesn’t. Segment re-evaluation can take 90 minutes depending on list size, filter complexity, and whether you’re using calculated fields. That delay breaks time-sensitive campaigns—product launches, flash sales, behaviour-triggered follow-ups. Tags update instantly; segments batch-process. If you’re building automations that depend on up-to-the-minute accuracy, you need to know which trigger mechanism actually fires when you expect it to.
READER QUESTION
Zapier webhook retries stop after three attempts
When a Zap calls a webhook and the endpoint times out or returns an error, Zapier doesn’t give up immediately. It retries three times over 90 minutes, backing off exponentially between attempts. If all three fail, the task is marked as errored and you get a notification—but the data doesn’t queue for a fourth try. That’s fine for non-critical workflows, but if you’re using webhooks to log subscriber events, sync CRM records, or trigger fulfilment, three attempts might not be enough. Knowing the retry schedule lets you build a fallback—whether that’s a manual replay, a secondary Zap, or a database that catches missed events.
WORTH READING
WordPress cache plugins purge at different speeds
You publish a post, clear the cache, and assume the new version is live. But WP Rocket, W3 Total Cache, and LiteSpeed Cache all purge differently. Some clear the homepage instantly but leave category pages stale for minutes. Others purge HTML immediately but keep CSS and JavaScript cached until the next manual flush. If you’re running time-sensitive content—product drops, affiliate promotions, breaking news—you need to know which plugin clears what, when, and whether your CDN respects the purge signal. Otherwise, half your traffic sees yesterday’s page while you’re already promoting today’s.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.