PERSONAL PRODUCTIVITY

Pre-meeting Slack check-in confirming the agenda is current

Two hours before each recurring meeting, posts a Slack message to the organizer asking them to confirm or update the agenda.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMeeting starts in ~2 hours
  • ActionFetch current agenda from inviteOutlook
  • ActionDM organizer Confirm/Needs-update on SlackSlack
  • LogicAwait response or timeout at start time
  • OutputPost 'agenda unconfirmed' to channel if silentSlack

What it does

Adds a lightweight accountability checkpoint right before the meeting. It DMs the organizer a couple of hours ahead with the current agenda and a quick 'Confirm' / 'Needs update' choice. If they confirm, the meeting proceeds clean; if they go silent past start time, it posts a short 'agenda unconfirmed' note in the team channel so attendees know what they're walking into.

When to use it

For teams that want explicit owner sign-off on the agenda every cycle, not just a once-a-week nudge. Good where meetings start cold and nobody is sure the agenda reflects today's priorities.

How it works

  1. 1A meeting-starting-soon event fires roughly two hours before each recurring instance.
  2. 2It fetches the meeting's current agenda from the calendar invite via Outlook.
  3. 3It DMs the organizer on Slack with the agenda text and Confirm / Needs-update buttons.
  4. 4A logic step waits for the response or a timeout at meeting start.
  5. 5On confirm it logs and exits; on no-response it posts an 'agenda unconfirmed' message to the meeting's Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.