All templates

Studio Ninja Automated Weekly Session Digest

Every Monday morning, WebRun opens Studio Ninja, gathers every session booked for the current week, cross-checks Google Calendar to catch any double booking or missing calendar block, and posts a clean weekly digest to Slack with client names, session types, times, and locations so the whole team starts the week aligned.

Runs on WebRun · Strict Lockdown policy
Every Monday at 7:30 AM WebRunorchestrates each step
1 Studio Ninja gather this week's sessions
2 Google Calendar check for conflicts or gaps
3 Slack post the weekly digest
In short

How do I give my photography team a clear view of the week's sessions?

Every Monday, WebRun opens Studio Ninja, gathers every session booked for the week ahead, and cross-checks Google Calendar to catch double bookings or missing calendar blocks. It posts a clean weekly digest to Slack grouped by day, with client, time, location, and any staffing need flagged, so the whole team starts the week aligned and nothing is missed.

  • The whole team starts Monday already knowing the week's full schedule
  • Calendar conflicts surface before a session day, not on it
  • Staffing needs like a second shooter are flagged a week ahead

Built for photography studio owners · studio managers · second shooters · photography 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 app.studioninja.co in a real browser with your saved login - no setup, no API keys.

  2. 1
    Studio Ninja - gather this week's sessions
    studioninja.co
    WebRun in Studio Ninja: gather this week's sessions
    WebRun opens Studio Ninja to gather this week's sessions.
    • Open Studio Ninja and pull every session booked for the current week
    • Capture the client, session type, day, time, and location for each
    • Note any session needing a second shooter or special equipment

    Done when Every session booked this week is listed with its full details.

  3. 2
    Google Calendar - check for conflicts or gaps
    calendar.google.com
    WebRun in Google Calendar: check for conflicts or gaps
    WebRun opens Google Calendar to check for conflicts or gaps.
    • Check Google Calendar for a matching event for each session
    • Flag any session with no calendar block or a conflicting event at the same time
    • Note any personal or studio event that overlaps a session

    Done when Every session is checked against Google Calendar for conflicts or missing blocks.

  4. 3
    Slack - post the weekly digest
    slack.com
    WebRun in Slack: post the weekly digest
    WebRun opens Slack to post the weekly digest.
    • Post the week's full schedule to Slack grouped by day
    • List client, session type, time, and location for each
    • Flag any calendar conflict or second shooter need at the top

    Done when The team has this week's full schedule and any conflicts flagged in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.studioninja.co
ScheduleRuns automatically on this cadence
Every Monday at 7:30 AM
DeliveryHow each run's result reaches you
Weekly session digest · Slack
OutputWhat each run produces - A weekly Slack digest of every booked session grouped by day, with calendar conflicts and staffing needs flagged.
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 contact clients about their upcoming session?

No. This digest is entirely internal. It only posts the week's schedule to your team's Slack channel, it never emails or texts a client.

How does it catch scheduling conflicts?

It checks Google Calendar for a matching event on every Studio Ninja session, and flags anything missing a block or overlapping another event.

What if a session gets added mid-week?

This digest runs once each Monday for the week ahead. A session added later shows up on the following Monday's digest, or you can note it manually in Slack.

Put this on autopilot.

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