All templates

Automated Restaurant Period Close Tracking

Every morning during close, WebRun opens Restaurant365, reads each location's close checklist and journal status, compares it to the period-close deadlines in Google Calendar, and posts the team a Slack status of what is complete, what is due today, and which units are running behind.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Restaurant365 read each location's close status
2 Google Calendar check the close deadlines
3 Slack post the close status
In short

How do I track multi-location period-close deadlines automatically?

Every morning during close, WebRun reads each location's close checklist and journal status in Restaurant365, compares it to the period-close deadlines in Google Calendar, and posts the team a Slack status showing what is done, due today, or overdue. Units running behind sit at the top, so no location's close quietly slips past its deadline.

  • Every location's close status is visible in one place each morning
  • Behind-schedule units surface days before the deadline, not after
  • The team spends the daily standup on blockers, not status gathering

Built for restaurant controllers · accounting managers · multi-unit operators · close teams

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

  2. 1
    Restaurant365 - read each location's close status
    restaurant365.com
    WebRun in Restaurant365: read each location's close status
    WebRun reads each location's period-close status in Restaurant365.
    • Open Restaurant365 and read the period-close checklist and journal status for each location
    • Capture which close tasks are done, in progress, or not started per unit
    • Note any location with unreconciled accounts or open AP holding it up

    Done when Every location's close progress has been read from Restaurant365.

  3. 2
    Google Calendar - check the close deadlines
    calendar.google.com
    WebRun in Google Calendar: check the close deadlines
    WebRun checks the period-close deadlines in Google Calendar.
    • Open the period-close calendar in Google Calendar
    • Read the deadline for each close task and milestone in the current period
    • Match each location's task status against the date it is due

    Done when Each close task has been paired with its deadline.

  4. 3
    Slack - post the close status
    slack.com
    WebRun in Slack: post the close status
    WebRun posts the daily period-close status to Slack.
    • Post a per-location close status showing done, due today, and overdue tasks
    • Put the units furthest behind schedule at the top
    • Call out the specific task and owner blocking each late close

    Done when The team has today's period-close status in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
my.restaurant365.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Close status · Slack
OutputWhat each run produces - A per-location close status listing done, due-today, and overdue tasks against their deadlines, worst-behind units first.
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

Does it change anything in Restaurant365?

No. WebRun only reads the close checklist and journal status in Restaurant365. It never marks a task done, posts a journal, or closes a period, so it cannot alter your books, only report on them.

How does it know which units are behind?

It compares each location's task status in Restaurant365 to the deadline for that task in your Google Calendar, then flags anything past due or due today so nothing slips unnoticed.

Can it just message me instead of the whole team?

Yes. WebRun can post the close status to a private channel or a direct message instead of a shared one, so you get the same daily picture without alerting everyone.

Keep going

Related templates

Automated Restaurant365 Invoice Capture
Every morning, WebRun reads new vendor invoice PDFs in Gmail, enters each one into Restaurant365 AP with the vendor, GL account, and location filled in, and posts you a Slack summary of what was captured.
Restaurant365›Gmail›Slack
Automated Restaurant365 Vendor Onboarding
When you open a new restaurant, WebRun reads the vendor list from a Google Sheet, drafts each supplier as a vendor record in Restaurant365 with terms and GL defaults, and posts you a Slack checklist of what still needs a number or a W-9.
Restaurant365›Google Sheets›Slack
Automated Restaurant Vendor Payment Runs
Every week, WebRun reviews approved AP bills due in Restaurant365, builds a proposed payment run staged in Ramp, leaves it queued but unsent, and posts you a Slack summary of who would be paid, how much, and from which account.
Restaurant365›Ramp›Slack

Put this on autopilot.

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

Deploy this workflow Talk to us