All templates

Automated Game Night Reminders

Each morning before a scheduled game event, WebRun reads the RSVP roster in Google Sheets, drafts personalized reminder texts via Twilio for your review, and posts a headcount summary to Slack so the organizer knows who is confirmed and who may need a nudge.

Runs on WebRun · Strict Lockdown policy
Every day at 9:00 AM WebRunorchestrates each step
1 Google Sheets read confirmed RSVPs
2 Twilio draft reminder texts for review
3 Slack post headcount summary
In short

How do I send automated game night reminders to reduce no-shows?

WebRun reads your Google Sheets RSVP roster every morning, drafts personalized Twilio reminder texts for players at upcoming events, and posts a headcount summary to Slack. All texts are queued for organizer approval before sending, so no player is messaged without a human review.

  • No-shows reduced with timely player reminders before each event
  • Organizer reviews all texts before any message goes out
  • Headcount visible in Slack without opening the roster sheet

Built for game store owners · hobby shop event organizers · tabletop gaming clubs · card game tournament managers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens docs.google.com/spreadsheets in a real browser with your saved login - no setup, no API keys.

  2. 1
    Google Sheets - read confirmed RSVPs
    google.com
    WebRun in Google Sheets: read confirmed RSVPs
    WebRun opens Google Sheets to read confirmed RSVPs.
    • Open the event roster sheet and filter to events happening within the next 48 hours
    • Collect each confirmed player's name and phone number
    • Skip players already marked as reminded this cycle

    Done when All confirmed players for upcoming events are listed with contact details.

  3. 2
    Twilio - draft reminder texts for review
    twilio.com
    WebRun in Twilio: draft reminder texts for review
    WebRun opens Twilio to draft reminder texts for review.
    • Draft a short, friendly reminder text for each player with the event name, date, and time
    • Include the store address and a note to reply if they can no longer attend
    • Queue the drafts for organizer review before any texts are sent

    Done when Reminder text drafts are queued in Twilio and ready for organizer approval.

  4. 3
    Slack - post headcount summary
    slack.com
    WebRun in Slack: post headcount summary
    WebRun opens Slack to post headcount summary.
    • Post a pre-event headcount summary to the events Slack channel
    • List each upcoming event with confirmed count, total capacity, and number of reminders queued
    • Note if any event is below half capacity so the organizer can promote it

    Done when The organizer has a headcount summary in Slack with queued reminders ready to send.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
docs.google.com/spreadsheets
ScheduleRuns automatically on this cadence
Every day at 9:00 AM
DeliveryHow each run's result reaches you
Reminder drafts · Slack
OutputWhat each run produces - Draft reminder texts queued in Twilio and a Slack headcount summary for each upcoming event.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it send reminder texts to players automatically?

No. WebRun drafts and queues the texts in Twilio for organizer review. No message is sent to a player until the organizer approves the batch.

How far in advance does it run reminders?

WebRun checks each morning for events within the next 48 hours by default, so players get a heads-up with enough time to rearrange their schedule if needed.

What if someone cancels after the reminder is sent?

When a player replies to cancel, you can update the roster in Google Sheets and WebRun will reflect the updated headcount in the next morning's Slack summary.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.