Skip to content

Runbook Checklist Runner

Example prompt: "On the first working day of each month, kick off our 'Monthly Close' runbook from Notion. Create the tasks in Asana with the right owners and dates, put the close review meeting on the calendar, post the checklist in #finance Slack, and follow up with each owner if their step isn't ticked off by the deadline."

The Problem

Most operations teams have a folder of runbooks for recurring or triggered events — monthly close, quarterly access review, product launch day, the periodic disaster-recovery drill — and almost all of them get half-executed because the person who wrote them is now doing other work. The runbook lives in Notion, the tasks live in Asana, the kickoff meeting needs to go on five calendars, and the chase-ups happen in Slack. By the time you've copied the checklist into the project board, half the team has missed the kickoff and the runbook is already running late.

How GloriaMundo Solves It

We build a workflow that turns a runbook page into an executed process. The trigger is either a scheduled date (monthly close on the first working day) or a manual fire-off ("run the launch-day runbook for ACME release"). An integration step reads the runbook template page from Notion or Confluence. An LLM step parses the steps, owners, and deadlines into a structured list. A series of integration steps then provisions everything the runbook needs: tasks in the project tool with the right owners and due dates, calendar invites for the review meetings, a tracking page for this specific run, and a kickoff post in the relevant Slack channel with the full checklist. A conditional step monitors task completion against the runbook deadlines and, when a step is late, sends a polite nudge to the owner with a link to the checklist. Glass Box preview lets us walk through every task, invite, and message before any of them are sent.

Example Workflow Steps

  1. Trigger (integration): Fires on a schedule, or manually when a runbook is invoked by name.
  2. Step 1 (integration): Read the runbook template page from Notion or Confluence.
  3. Step 2 (LLM): Parse the page into a structured list of steps with owner, deadline, and description.
  4. Step 3 (integration): Create a per-run tracking page in Notion or Confluence, plus tasks in Asana with the right owners and dates.
  5. Step 4 (integration): Send Google Calendar invites for the meetings the runbook requires.
  6. Step 5 (integration): Post a kickoff message in the runbook's Slack channel with the checklist and tracking page link.
  7. Step 6 (conditional): On a daily check, find tasks that are past their internal deadline and DM the owner with a nudge.

Integrations Used

  • Notion — source of runbook templates and the per-run tracking page
  • Confluence — alternative wiki source when Notion is not used
  • Asana — task creation with owners and due dates
  • Google Calendar — invites for the meetings the runbook requires
  • Slack — kickoff message, checklist, and nudges
  • Gmail — optional email summary to leadership on completion

Who This Is For

Operations, finance, and engineering managers at companies of 30-300 where the same handful of runbooks fire every month or quarter and the manual kickoff costs half a day each time.

Time & Cost Saved

A typical runbook kickoff — copy the checklist, create the tasks, send the invites, post the message, set up the tracker — takes 60-120 minutes of an ops lead's time, and the nudge cycle takes another 30-60 minutes spread across the run. For a team that runs 6-10 distinct runbooks a quarter, that adds up to a working day per month. More importantly, runs that fire consistently are far less likely to miss a step. The workflow uses LLM, integration, and conditional steps and costs a small number of credits per runbook execution.