All templates
For wedding planners, event coordinators & catering liaisons

Lock in final headcounts before your caterer's deadline

Every morning, WebRun opens Aisle Planner, finds weddings within 10 days of their final headcount deadline, tallies the confirmed RSVPs and dietary notes, logs the finalized count in Google Sheets, and drafts the confirmation email to the caterer or venue in Gmail for your review before it sends.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 Aisle Planner tally confirmed RSVPs for each wedding
2 Google Sheets log the finalized headcount and dietary notes
3 Gmail draft the final count confirmation for the caterer or venue
Run a sample
In short

How do I automatically confirm final wedding guest counts with vendors?

WebRun checks Aisle Planner every morning for weddings within 10 days of their final headcount deadline, tallies the confirmed RSVPs and dietary notes, and logs the locked-in number in Google Sheets. It then drafts the confirmation email to the caterer or venue in Gmail, so your final count reaches vendors accurately and on time.

  • Final headcounts are locked in and logged before every caterer deadline
  • Dietary requirements travel with the count instead of getting lost in email threads
  • Vendor confirmations go out accurate and on time, every wedding

Built for wedding planners · event coordinators · catering liaisons · venue coordinators

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 app.aisleplanner.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Aisle Planner - tally confirmed RSVPs for each wedding
    aisleplanner.com How to Automate Aisle Planner
    WebRun in Aisle Planner: tally confirmed RSVPs for each wedding
    WebRun opens Aisle Planner to tally confirmed RSVPs for each wedding.
    • Open Aisle Planner and find weddings within 10 days of their final count deadline
    • Tally the confirmed RSVP count for each, excluding declines and no responses
    • Capture dietary requirements and any special meal counts attached to responses

    Done when Every wedding nearing its final count deadline has a confirmed headcount and dietary breakdown.

  3. 2
    Google Sheets - log the finalized headcount and dietary notes
    google.com How to Automate Google Sheets
    WebRun in Google Sheets: log the finalized headcount and dietary notes
    WebRun opens Google Sheets to log the finalized headcount and dietary notes.
    • Open the guest count tracker in Google Sheets
    • Log the finalized headcount, dietary counts, and deadline date for each wedding
    • Flag any wedding where the count changed from the last logged figure

    Done when The Sheet reflects the current locked-in headcount and dietary notes for every wedding in the window.

  4. 3
    Gmail - draft the final count confirmation for the caterer or venue
    gmail.com How to Automate Gmail
    WebRun in Gmail: draft the final count confirmation for the caterer or venue
    WebRun opens Gmail to draft the final count confirmation for the caterer or venue.
    • Draft a confirmation email to the caterer or venue with the final headcount and dietary breakdown
    • Reference the wedding date and the deadline it is confirming against
    • Save it as a Gmail draft, left unsent for your review

    Done when A ready-to-send final count confirmation draft exists in Gmail for every wedding in the window.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.aisleplanner.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Final count confirmation drafts · Gmail
OutputWhat each run produces - A logged final headcount with dietary notes in Google Sheets, plus a ready-to-send Gmail confirmation for the caterer or venue.
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 the final count to my caterer without my approval?

No. The confirmation email is saved as a Gmail draft only. Nothing reaches your caterer or venue until you review the numbers and send it yourself.

What counts as a confirmed guest for the final headcount?

Only RSVPs marked confirmed in Aisle Planner. Declines and still-pending responses are excluded from the number WebRun logs and confirms.

What if the count changes after the confirmation is sent?

The next morning's run picks up the updated RSVP data, logs the new figure in Sheets, and flags the change so you know a revised confirmation is needed.

Put this on autopilot.

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