All templates

Automated TMS Course Session Tracking

Every Monday, WebRun opens Osmind, counts the completed treatments for each patient in an active TMS course against their planned session total, flags patients falling behind pace or approaching their authorized session limit, logs each course status to Google Sheets, and drafts a short progress note in Gmail for the treating clinician to review.

Deploy this workflow Browse all templates
Runs on WebRun · Strict Lockdown policy
Every Monday at 7:30 AM WebRunorchestrates each step
1 Osmind count completed TMS sessions
2 Google Sheets track course progress
3 Gmail draft progress notes for clinicians
In short

How do I track TMS course progress and session counts automatically?

WebRun opens Osmind every Monday and counts completed sessions for each patient in a TMS course against their planned and authorized totals. It flags patients behind pace or nearing their session limit, logs the status to Google Sheets, and drafts an internal progress note in Gmail for the treating clinician to review and act on.

  • Behind-pace TMS courses surface weekly before patients drop off
  • Courses nearing their authorized limit are flagged in time to re-authorize
  • Clinicians get a drafted progress note for every course that needs attention

Built for TMS treatment centers · interventional psychiatry clinics · TMS technicians · psychiatric practice 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 app.osmind.org in a real browser with your saved login - no setup, no API keys.

  2. 1
    Osmind - count completed TMS sessions
    osmind.org
    WebRun in Osmind: count completed TMS sessions
    WebRun opens Osmind to count each patient's completed TMS sessions.
    • Open Osmind and list patients in an active TMS treatment course
    • For each, count completed sessions against the planned course total and the authorized session count
    • Read the start date and compute whether the patient is on pace for a typical course schedule
    • Capture patient initials, sessions completed, course total, authorized total, and pace status

    Done when Every active TMS patient has completed sessions counted against their course total and authorized limit.

  3. 2
    Google Sheets - track course progress
    google.com
    WebRun in Google Sheets: track course progress
    WebRun logs each TMS course's progress and flags the at-risk ones.
    • Open the TMS Course Tracker sheet
    • Append this week's row per patient with sessions completed, remaining, and percent of course done
    • Flag patients behind the expected pace and those within five sessions of their authorized limit
    • Sort so courses needing attention or a re-authorization sit at the top

    Done when The tracker reflects each patient's course progress with behind-pace and near-limit patients flagged.

  4. 3
    Gmail - draft progress notes for clinicians
    gmail.com
    WebRun in Gmail: draft progress notes for clinicians
    WebRun drafts an internal TMS progress note, left unsent for review.
    • For each flagged course, draft an internal progress note in Gmail to the treating clinician
    • Summarize sessions completed, sessions remaining, pace, and whether re-authorization is coming due
    • Leave every note as an unsent draft for the clinician to review and act on
    • Do not contact the patient and do not send any message automatically

    Done when An internal progress note draft awaits the treating clinician for each flagged TMS course.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.osmind.org
ScheduleRuns automatically on this cadence
Every Monday at 7:30 AM
DeliveryHow each run's result reaches you
Course tracker · Google Sheets
OutputWhat each run produces - A Google Sheet tracking each TMS course's session count and pace, plus internal Gmail progress notes drafted for clinicians on the courses that need attention.
Spreadsheet + drafts
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 message patients or clinicians without review?

No. WebRun logs the internal Google Sheet automatically, but every clinician progress note is saved as an unsent Gmail draft for review. It never messages the patient. A person acts on each note themselves.

How does it know a course is behind pace?

It reads each patient's session count and start date in Osmind and compares completed sessions to a typical course schedule. Patients trailing the expected pace or nearing their authorized limit are flagged for attention.

Does any patient information leave our systems?

No. The Google Sheet and Gmail drafts use patient initials and session counts only and stay inside your own connected workspace, so no protected health information is sent to any outside service.

Keep going

Related templates

Automated Spravato Monitoring Window Log
Every morning, WebRun opens Osmind, finds today's Spravato patients, checks each one is booked for the required two-hour post-dose monitoring, logs any gaps to Google Sheets, and posts the clinic team a Slack list of who needs a monitoring slot.
Osmind›Google Sheets›Slack
Automated Ketamine Series Booking Worklist
Each morning, WebRun opens Osmind, finds patients mid-way through a ketamine infusion series whose next dose is due soon, checks Google Calendar for a booked next visit, and logs a worklist of who still needs an appointment to Google Sheets so the front desk can fill the gaps.
Osmind›Google Calendar›Google Sheets
Automated PHQ-9 and GAD-7 Trend Digest
Every week, WebRun opens Osmind, reads each active patient's latest PHQ-9 and GAD-7 scores, compares them to their baseline and prior visit, logs the trend to Google Sheets, and posts your clinicians a Slack digest of who is improving and who is stalling.
Osmind›Google Sheets›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