← Return to Long Post and Random Thoughts

Long Post

What are the differences between Kit Visual Automation and Sequence? A comparison that's easy for beginners to understand.

What exactly is the difference between Kit Visual Automation and Sequence? This article uses the analogy of a roadmap and a stack of emails to explain their respective roles, when to use them independently, and how to connect them into a complete email automation system.

Kit Visual Automation vs Sequence 差在哪?新手最容易懂的比較

You compose five emails in Kit, only to find that no one has received them. Then you open Visual Automation, see a bunch of squares and lines, and have no idea where to put the emails.

This usually means that the work of two functions is mixed up.

The shortest way to remember it is:Sequence is the message, Visual Automation is the path.

What is a Kit Sequence?

A sequence is a stack of emails arranged in order. It determines:

  • The main point and content of each letter.
  • When will the first letter be sent?
  • The next one will take several hours or days.
  • Which days are permitted for shipping?
  • Who should be excluded?

For example, a Welcome Sequence consists of three emails: one to deliver the materials today, one to introduce the method two days later, and one to invite you to reply to questions two days after that.

The Sequence itself may not know who wants to join. You still need to use Forms, Rules, or Visual Automation to send people in.

What is Kit Visual Automation?

Visual Automation is a roadmap. It determines:

  • From which form, tag, or purchase event did the person come in?
  • Which sequence to add first.
  • How long will it take?
  • When something happens, should we jump to the back?
  • Which path should people who meet different conditions take?
Kit Automation 裡的 Event、Action 與 Condition
Events, Actions, and Conditions in Kit Automation

In Visual Automation, you will see three commonly used nodes:

  • Action: To do something, such as adding a Sequence, adding a Tag, or waiting.
  • EventWhen something happens, it brings people in the process to this step.
  • ConditionAsk a question, and if the answers differ, we go our separate ways.

Kit Visual Automation vs Sequence Comparison Table

question Sequence Visual Automation
Main uses The interval between writing letters and arranging mailing Design of entrances, routes, and traffic flow.
Where to put the content Every email editor Nodes and connections
Can it exist independently? Yes, but there needs to be another entry point to add people. It can accept tags, delays, conditions, etc.
Common errors Email or Draft Automation or Inactive
What does it most resemble? A stack of neatly arranged letters Map or conveyor belt

In what situations is only a Kit Sequence required?

If you only want to manually add a group of confirmed people to a fixed set of five emails, a sequence might be sufficient. This assumes you know who will be added and don't need complex routing.

When is Kit Visual Automation needed?

Visual Automation is used when you need any of the following:

  • Different forms lead to different welcome messages.
  • Those who made a purchase stopped the promotion and improved the onboarding process.
  • The event date has arrived, let's all move forward together.
  • People with a certain tag will have different outcomes.
  • Each person has a different self-set date, and you will have to wait until your own date.

How do I connect Kit Sequence and Visual Automation?

Take the list magnet as an example:

Request Tag → Welcome Sequence → End

名單磁鐵與 Welcome Sequence 完整路線
List magnet with Welcome Sequence full route

The order of operations can be:

  1. First, finish writing the letters in the Sequence.
  2. Return to Visual Automations and create an entry point.
  3. Press the plus sign and select... Action → Email sequence.
  4. Select the Sequence you just created.
  5. Check if Delay, Event, or Condition are needed afterward.

How can beginners avoid overcompacting the Kit process?

Start with one entry point, one sequence, and one clear endpoint. If different needs arise, add another branch.

A flowchart may look impressive, but that doesn't mean it's useful. Each additional node adds another point for later checking. Stabilizing the most frequently repeated section first is more reliable than filling the entire canvas at once.

If you want to first identify which parts are worth making into sequences and which parts need automation, you can do this 5-day offline test. You'll see where the process stops first, and then decide whether to write an email or interrupt the process.

Official Reference

Try it for free for 14 days with my Kit's exclusive link.No credit card needed, start here →

Additional note: If you start using the Kit through the dedicated link in the article, I will receive a small amount of feedback, which will not increase your cost at all; this is an extra benefit from the platform.

en_US