The rule: an approval only counts for the revision it was given for. Edit the caption after approval and the approval stops counting, because editing bumps the revision. The client-facing links below are real HMAC tokens verified in your browser by the same approval-core.js that runs inside the n8n workflows. State is in memory here; in production the three SQL tables hold it.
Agency view — the post
Little Fern Kitchen
revision 1draft
…
Step 3 is on the client's phone: approve once, then approve again — the second tap records nothing new.
Client view — iPhone, WhatsApp link
Little Fern Kitchennow
Nothing sent yet.
No link issued yet.
Steps
Send revision 1 to the client
Client approves revision 1
A second approve tap records one decision, not two
Agency fixes a typo — revision becomes 2
The old link is refused as stale
Publish is blocked for revision 2
Send revision 2
Client approves revision 2
Publish succeeds; a second publish is refused
// results printed as the core returns them
Put this gate in your pipeline
Everything above runs the same core that ships in the workflows. Two ways to have it in production this week:
Installed for you — $149
I put it in your n8n, connect your storage (Drive, Notion or Airtable) and hand over the 20-scenario suite, passing. Three working days from your first message.
If it does not fit your setup, PayPal refund inside 7 days, no argument. Questions go to perun.intelligence@gmail.com — one question, one answer, no sales call.