Never Miss Emergencies: Auto-Exit Snooze for Urgent Issues
Neurodivergent founders use Slack snooze to protect focus time. This workflow intelligently ends snooze when a truly urgent issue arrives, ensuring emergencies still get through.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
End snooze
Ends the current user's snooze mode immediately.
Why this helps
You're in snooze mode focusing on deep work, but a critical issue arrives and you don't see it for hours because notifications are blocked.
- Protect your focus time while ensuring true emergencies still break through
- Automatically re-enable notifications for critical issues only
- Balance deep work protection with business continuity
Setup
Build it in a few focused steps.
- 1Connect Jira and Slack to Notis (one-time).
- 2Create an automation with the prompt: 'When an issue priority changes to Critical or Blocker in Jira, end my Slack snooze mode immediately.'
- 3Select 'Updated Issue' as the trigger.
- 4Specify what 'urgent' means for your team (e.g., Critical priority, Blocker status, specific labels).
- 5Test by setting yourself to snooze and then updating an issue to Critical.
Questions about this workflow
Will this interrupt my focus time constantly?
Only if issues are actually marked Critical. Use strict criteria in your prompt (e.g., 'only if priority changes TO Critical') to prevent noise.
Can I set a threshold (e.g., only end snooze for Blocker, not just Critical)?
Yes. Adjust your prompt: 'Only end snooze if the issue is marked Blocker or has the label Production-Down.'
What if I want to be notified but not exit snooze?
Use a reminder workflow instead, which will queue notifications without ending snooze.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Slack. A trigger fires from one place; an action lands in another.
Jira triggers
Slack actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
New Project
Triggered when a new project is added in Jira
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
Not just Jira and Slack. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Slack.