Follow-Up Automation Scheduler
Follow-ups never fall through cracks. Issues tagged for follow-up get scheduled automatically and managed throughout their lifecycle.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
Why this helps
Follow-ups are hard to remember. You mark something for follow-up and then forget. Weeks later you discover nothing happened.
- Prevents follow-ups from being forgotten
- Schedules reminders automatically based on your preferences
- Manages follow-up lifecycle from creation to completion
- Reduces anxiety about dropped follow-ups
Setup
Build it in a few focused steps.
- 1Connect Linear and Apilio to Notis (one-time setup).
- 2In Apilio, create logicblocks for different follow-up schedules (e.g., 'followup_1_week', 'followup_2_weeks', 'followup_monthly').
- 3Ask Notis: 'When an issue is created with a follow-up tag, fetch my Apilio follow-up logicblocks and schedule the reminder.' Create via portal or chat.
- 4Select 'Issue Created' as your trigger.
- 5Test by creating an issue with a follow-up label and verify the reminder gets scheduled in Apilio.
Questions about this workflow
How do I tag an issue for follow-up?
Use a specific label in Linear (e.g., 'follow-up-needed'). Your Notis prompt identifies this label and triggers scheduling.
How far in the future should follow-ups be scheduled?
That depends on the work. Include the timeframe in your tag (e.g., 'follow-up-1-week', 'follow-up-2-weeks') and your Notis prompt schedules accordingly.
What happens when a follow-up reminder fires?
Your Apilio logicblock determines the action: create a new issue, send a notification, or add to your daily queue. You decide.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Apilio. A trigger fires from one place; an action lands in another.
Linear triggers
Apilio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Boolean Variables
Tool to fetch all boolean variables. use when you need the full list of boolean variables and their current states.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
Comment Received Trigger
Triggered when a comment is received.
Get Logicblocks
Tool to fetch all logicblocks of a user. use after authenticating with apilio api when you need to list available logicblocks.
Issue Created Trigger
Triggered when a new issue is created.
Get Numeric Variables
Tool to fetch all numeric variables. use after authenticating the apilio api.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Apilio, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Apilio.