Never Forget Follow-Ups: Automatic Task Reminders
Neurodivergent founders often create follow-up tasks but forget to act on them. This workflow automatically creates a Slack reminder for every new follow-up or review task in Jira.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Delete a Slack reminder
Deletes an existing slack reminder, typically when it is no longer relevant or a task is completed; this operation is irreversible.
Why this helps
Follow-up work (like 'review customer feedback' or 'schedule meeting') sits in Jira without action. You assume it will happen organically but it gets buried.
- Automatically surface follow-up work in Slack instead of waiting for Jira checks
- Reduce forgotten tasks by scheduling reminders at optimal times
- Create accountability by making follow-ups visible in Slack
Setup
Build it in a few focused steps.
- 1Connect Jira and Slack to Notis (one-time).
- 2Create an automation with the prompt: 'When a new issue is created in Jira with the label follow-up or type Follow-Up Task, create a Slack reminder for me in 2 days with the task and due date.'
- 3Select 'New Issue' as the trigger.
- 4Customize the reminder delay to your preference (in 1 hour, tomorrow, in 3 days, etc.).
- 5Test by creating a follow-up task in Jira and verifying the reminder arrives in Slack.
Questions about this workflow
How do I mark something as a follow-up task?
Tag it in Jira with a label (follow-up, review, etc.) or use a specific issue type (Follow-Up Task). Notis reads these.
Can different follow-ups have different reminder times?
Yes. Create separate automations for different scenarios (urgent follow-ups in 1 hour, regular follow-ups in 2 days).
What if I need multiple reminders?
Notis can create recurring reminders. Ask in your prompt: 'Create a reminder today and repeat it daily until the issue is marked Done.'
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.