See which Drift playbooks are actually earning meetings
Every Monday, WebRun opens Drift, reads how each live playbook performed last week across conversations started, engaged, and meetings booked, logs the numbers per playbook in Airtable, and writes a short keep or fix summary into your Notion revenue page.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I tell which Drift playbooks are booking meetings?
WebRun reviews your Drift playbooks every Monday. It reads last week's conversations started, replies, and meetings booked for each live playbook, logs the numbers and rates in Airtable so trends build up, then writes a Notion summary naming the best performers and recommending what to adjust or pause.
- Every playbook has a weekly meeting rate, not just a conversation count
- Busy playbooks that book nothing are called out by name
- The history builds in Airtable so trends beat single-week noise
Built for B2B marketing teams · sales development teams · revenue operations · demand generation
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.drift.comin a real browser with your saved login - no setup, no API keys. -
1
Drift - read last week's playbook results
drift.com
WebRun opens Drift to read last week's playbook results. - Sign into Drift and open the reporting view for the past seven days
- For each live playbook, capture conversations started, conversations where the visitor replied, and meetings booked
- Note which pages or audiences each playbook targets
- Compare every number against the same playbook in the previous week
- Flag playbooks that started plenty of conversations but booked nothing
Done when Every live playbook has last week's counts, its week over week change, and any zero-booking flag.
-
2
Airtable - log the numbers per playbook
airtable.com How to Automate Airtable
WebRun opens Airtable to log the numbers per playbook. - Open the playbook performance base in Airtable
- Add one row per playbook per week with conversations, replies, and meetings booked
- Calculate the reply rate and the meeting rate on each row
- Keep the history so a playbook can be read as a trend rather than a single week
Done when Airtable holds one row per playbook for last week with reply and meeting rates calculated.
-
3
Notion - write the keep or fix summary
notion.so How to Automate Notion
WebRun opens Notion to write the keep or fix summary. - Open the revenue page in Notion and add last week's summary
- Name the top three playbooks by meetings booked and the three worst by meeting rate
- Call out playbooks that started many conversations but booked none, since those usually need a new question or a better route
- Recommend keep, adjust, or pause for each flagged playbook and leave the decision to a human
Done when The Notion summary names the best and worst playbooks with a recommendation on each flagged one.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it change or pause a playbook?
No. WebRun reads Drift reporting only. It never edits a playbook, never pauses or publishes one, and never replies to a visitor. Recommendations are written into Notion for a human to act on.
Does it read individual chat conversations?
No. It works from playbook-level counts: conversations started, replies, and meetings booked. Visitor messages and contact details stay inside Drift.
Why does a playbook with lots of conversations get flagged?
Because volume without meetings usually means the opening question or the routing is wrong, not the traffic. Flagging it separately stops a busy playbook from looking successful when it books nothing.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.