All templates
For facilitators, product teams & agile coaches

Have the board ready before everyone joins the workshop

Every morning, WebRun opens Lucidspark, finds the boards for today's workshops, checks each was built from the right template, that the prompt sticky notes are placed, and that every participant has the access they need, then posts the facilitator a ready or not verdict in Slack and the wider team a heads-up in Microsoft Teams.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:30 AM WebRun
1 Lucidspark check the board is ready
2 Slack give the facilitator the verdict
3 Microsoft Teams post the session heads-up
Run a sample
In short

How do I make sure a workshop board is ready before the session starts?

WebRun opens Lucidspark every morning, finds the boards for today's workshops, and checks the template, the prompt sticky notes and every participant's access. It posts the facilitator a ready or not verdict in Slack and a session heads-up in Microsoft Teams, so the first ten minutes are the exercise, not sharing settings.

  • Every workshop board is checked before the first participant joins
  • Missing participant access is named, not discovered live
  • The facilitator gets a per-board verdict with sessions ordered by start time

Built for facilitators · product teams · agile coaches · consultants

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

  2. 1
    Lucidspark - check the board is ready
    lucidspark.com
    WebRun in Lucidspark: check the board is ready
    WebRun opens Lucidspark to check the board is ready.
    • Open Lucidspark and find the boards linked to today's workshops
    • Confirm each board was built from the template the session needs rather than left blank
    • Check the prompt sticky notes and section headings are placed so participants know where to write
    • Read the share settings and confirm every listed collaborator has been invited with edit access where they need it
    • Flag boards where a participant is missing, or where the board is still restricted to the facilitator

    Done when Every board for today has a template, prompts and a checked participant list.

  3. 2
    Slack - give the facilitator the verdict
    slack.com How to Automate Slack
    WebRun in Slack: give the facilitator the verdict
    WebRun opens Slack to give the facilitator the verdict.
    • Send the facilitator a ready or not verdict for each board they are running today
    • List exactly what is missing: the template, the prompts, or named participants without access
    • Put the session starting soonest first with its start time
    • Leave the fixes to the facilitator. WebRun does not change share settings or invite anyone

    Done when The facilitator has a per-board verdict in Slack before the first session.

  4. 3
    Microsoft Teams - post the session heads-up
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: post the session heads-up
    WebRun opens Microsoft Teams to post the session heads-up.
    • Post the team channel a short heads-up of today's workshops and their start times
    • Note which boards are confirmed ready and which are still being prepared
    • Keep participant names out of the public channel where a session is sensitive

    Done when The team has today's workshop heads-up in Microsoft Teams.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
lucid.app/users/login
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Board readiness · Slack
OutputWhat each run produces - A per-board ready verdict covering the template, the placed prompts and every participant's access, with the gaps named.
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 invite participants or change share settings?

No. WebRun checks the share settings and names anyone missing access, but it never invites a person and never changes a permission. Sending an invite stays the facilitator's action inside Lucidspark.

Does it edit the board?

No. It reads the board to confirm the template and the prompt stickies are in place. It never adds, moves or deletes a sticky note, so the board the facilitator built is the board the session gets.

What if a board is not ready?

The Slack message says exactly what is missing, the template, the prompts, or named participants without access, and lists the sessions starting soonest first so the most urgent gap is fixed first.

Put this on autopilot.

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