A message that does not apply to you teaches you to stop reading
Cohort announcements go to everyone, and most contain a section that applies to some students. Those who are already compliant read an instruction they have satisfied. After a few of those, they stop opening the sender's messages.
Relevance filtering is the fix, and it is arithmetic, not judgment. A student who submitted does not need the submission reminder. Excluding them costs one filter.
Personal detail is the other half. “Your assignment is due” is generic. “your draft is due Thursday, and your supervisor is named” is a message that gets acted on.
Timing per student matters where deadlines differ. Extensions, resits, and part-time routes mean that one cohort has several deadlines. A single date in a bulk message is wrong for a portion of the group.
How the ActionFlow runs on the canvas
Input arrives at a Start node: the announcement and the cohort. An HTTP Request node then reads the student list with each student's own status for the thing being announced.
A Filter node removes students to whom the message does not apply before anything is generated. Filtering first, rather than conditionally rendering, keeps the cost down and the logic legible.
A Loop node walks the remaining students. A Generate Object node returns, per student, the personal details the message needs (their deadline, their supervisor, their outstanding item), drawn from the record rather than invented.
A Validate node confirms every personalized field resolved. A message containing an unresolved placeholder is worse than a generic one, and it happens constantly in bulk sends.
A Generate Text node writes each message from your approved template with those fields inserted. A Resend node sends.
A Human in the Loop node holds the first message of any new announcement for review, so the template is checked once against real data rather than assumed correct.
A Google Sheets node records who was included and who was filtered out, which answers the question that always follows a bulk send.
Nodes this ActionFlow uses
- Start: takes the announcement and the target cohort.
- HTTP Request (Util): reads the student list with each student's own status.
- Filter (Data): removes students the message does not apply to, before generation.
- Loop (Control): walks the remaining students one by one.
- Generate Object (AI Core): resolves each student's own details from the record.
- Validate (Data): confirms every personalized field resolved before sending.
- Resend (Communication): sends the messages. Email fits the same slot.
- Google Sheets (Integration): records who was included and who was filtered out.
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.