Workflow
Table booking
Message contains “book”, “table”, “reserve”
Running
96
runs
88%
settled themselves
12
passed to a person
v2
live version
BTBellwether Table
What happens, in order
The number on each step is how many runs reached it. A step nothing reaches is a step to delete.
TriggerSomeone asks for a table
SendAsk for day, time and how many
WaitWait for a reply
Up to 24 hours
WebhookCheck the book
POST to the booking system
IfIs there a table?
If yesConfirm it and tag them
If noHand to a person
SendConfirm it and tag them
Hand offHand to a person
Offer the nearest alternative
12 of 96 runs ended with a person picking it up. That is the number to keep honest — a workflow that never hands over is either perfect or lying to somebody.