Acknowledgment is about versions, not about names
Policy distribution is usually treated as complete once the policy has been sent. The send leaves no record of whether anyone read it or which version they saw. The problem appears only when a dispute occurs.
The version is often ignored. An acknowledgment recorded against a policy that has been amended twice afterward has no value. The record matters only if it states what was acknowledged.
Chasing is the hard part, because the set of people who have not acknowledged keeps changing. Acknowledgment rates do not improve when a reminder has to go to everyone every week.
A one-off batch fails when new employees join or when people return to work. If the policy was introduced in March, someone who starts in June still needs to receive it. A one-off message does not cover that.
How the ActionFlow runs on the canvas
Policies sit in a Notion node with an explicit version field. A Start node bases distribution on a specific version rather than on a document.
An Airtable or PostgreSQL node stores the employee list and the acknowledgment records, keyed on the person and the policy version.
A Filter node builds the set of people who have not acknowledged this version, so every reminder goes only to people who still need it.
A Generate Text node includes a summary of the changes. Without that summary, the policy would be acknowledged without being read.
A Resend or Email node sends the acknowledgment request with a link. A Webhook trigger then writes the acknowledgment back to the records table.
A Start Scheduled node checks weekly, reminds only the outstanding set, and sends the matter to managers after the interval you have set.
A second Start Scheduled flow picks up new starters by comparing the employee list with the acknowledgment records for each active policy version. That is what keeps the record complete over time.
Nodes this ActionFlow uses
- Notion (Integration): holds policies with an explicit version field.
- Airtable (Integration): holds acknowledgment records keyed on person and version together.
- Filter (Data): reduces each send to those who have not acknowledged this version.
- Generate Text (AI Core): writes the request with a plain-language summary of what changed.
- Resend (Communication): sends the request. Email and SMTP fit the same slot.
- Webhook (Trigger): records the acknowledgment when the link is used.
- Start Scheduled: reminds the outstanding set, and separately catches new starters.
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.