Tell them it is ready, but only once it has been verified
A Make scenario takes a lab-test record id from a webhook and, only if the test's procedure is marked doctor-verified, sends the patient a notification that their result is ready and logs it.
Where this applies
Clinics, labs, repair and service businesses: anywhere a customer should hear that something is ready only once it has been verified.
- gate: doctor-verified, or nothing is sent
- 1
The problem
Telling a customer that something is ready is only useful if it is true, and in some fields saying it too early is worse than saying nothing. The notification has to wait for a human to have verified the thing it announces.
It also has to announce, not disclose: the message says a result is ready, never what it says.
What we built
Triggered by the record, not a schedule
A custom webhook receives a single field (the id of the test record) from whatever marks it ready upstream. Nothing polls.
A gate on verification
The scenario fetches the test record, iterates the procedure codes linked to it and fetches each code's master record. A variable is set true only when the master is flagged doctor-verified, and false otherwise, including when no code is linked, so an unverified or unlinked test never reaches the send.
Send, then log
If the gate is true, the scenario fetches each linked patient, sends a template message through the messaging API, and writes a log record linking the patient and the test, with the send and delivery flags and the execution id as the message id. A failed send stops before the log, so the log only records messages that went.
The outcome
Built and wired end to end, with the webhook attached.
It is switched off and has not yet run, so this page describes a design rather than a volume.
Where it stops
It is switched off and has never run. It has no consent check, no protection against a replayed webhook (a replay would send a duplicate) and no send window, and it does not update the record's result-shared flag. A patient with no phone number fails the request, and errors fall back on Make's default of stopping after three consecutive failures.
Built with
- Make.com
- Airtable
- Webhooks
- HTTP API
Patterns used
- Verification gate
- Notify, don't disclose
- Log after send
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no