The no-show is the most interesting segment
In most cases a single follow-up message is sent to everyone on the list. The attendee receives a recording, which is unnecessary. Anyone who had registered but did not turn up is treated as if they had never been interested at all.
The second group first expressed their intention and then encountered an obstacle, such as a scheduling clash, a meeting that ran over, or a link that failed to work. They are nearer to conversion than the average for their group, and they get the least tailored message.
Each group should have its own request. Attendees can have the opportunity to go into greater depth. No-shows should face as little difficulty as possible and be given a second chance. Those who never registered should be given a reason, not a recording.
Writing after a split uses one node and alters the sequence's total value.
How the ActionFlow runs on the canvas
Attendance data reaches the audience split before any writing. A Start node, a Webhook, or a Google Sheets node supplies the data.
The Switch node directs the flow three ways according to the attendance state. Each branch uses its own Generate Text node for a specific purpose, so the email sent to an attendee and the email sent to those who did not show are written for separate jobs rather than being modified from a single template.
Each branch has a Wait node that sets the interval before the second message. The sequence then runs in a single flow rather than as three separately scheduled ones.
A Human in the Loop node holds the first message from each branch until a person has read it. After the first execution, you can release the attendee branch while continuing the reviews of the others.
Resend or Email works. A Google Sheets node keeps a record of which branch each contact entered, and that column lets you compare conversions by branch rather than by campaign.
Place a Filter node before the split rather than inside it, because it excludes anyone who has unsubscribed or already converted before the split runs.
Nodes this ActionFlow uses
- Webhook (Trigger): receives the registration and attendance export. Google Sheets holds it instead.
- Filter (Data): removes unsubscribes and existing customers before the split.
- Switch (Control): routes attendees, no-shows, and non-registrants into separate branches.
- Generate Text (AI Core): one node per branch, each written to a different job.
- Wait (Control): sets the interval before the second message inside each branch.
- Slack (Human in the Loop): holds the first send of each branch for review.
- Resend (Communication): delivers the approved messages. Email fits the same slot.
- Google Sheets (Integration): records the branch each contact entered for conversion comparison.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.