PERSONAL PRODUCTIVITY

Flip Slack to Do-Not-Disturb for the duration of each focus block

At the start of every deep-work hold, this sets your Slack status and snooze to match the block.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled check at block boundaries
  • ActionRead upcoming calendar eventsGoogle CalendarGoogle Calendar
  • LogicIs a deep-work hold starting now?
  • ActionSet Slack status and enable DND for block lengthSlack
  • OutputConfirm presence synced to focus blockSlack

What it does

Keeps your Slack presence in sync with your calendar focus blocks. When a deep-work hold begins, it turns on Slack Do-Not-Disturb for exactly the block's length and sets a status that tells teammates when you'll resurface. When the block ends, it lifts the snooze and clears the status automatically.

When to use it

When you protect focus time on the calendar but still get pinged because Slack shows you as available. Use it so your status always reflects your real availability without manual toggling.

How it works

  1. 1A scheduled check runs at the top of each block and reads your upcoming Google Calendar events.
  2. 2A branch filters for events tagged as deep-work holds that are about to start.
  3. 3For a matching block, the flow computes the snooze duration from the event's end time.
  4. 4It sets a Slack status (emoji plus a 'back at HH:MM' message) and enables DND for that duration.
  5. 5The output confirms presence is set; Slack's snooze auto-expires when the block ends, restoring normal notifications.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google CalendarEvents, attendees, availability.
  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.