Blocked Work Detection
Blocked work stops being invisible. The moment an issue is marked blocked, conditions check whether it can self-unblock or needs escalation.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
Why this helps
Blocked work gets marked as such and then forgotten. You come back weeks later wondering why nothing happened. Blockers stay unresolved because nobody actively manages them.
- Detects blocked work instantly when status changes
- Evaluates whether blockers can be auto-resolved
- Escalates manual blockers immediately instead of weeks later
- Prevents blocked work from being forgotten
Setup
Build it in a few focused steps.
- 1Connect Linear and Apilio to Notis (portal setup, one-time).
- 2In Apilio, define conditions for blocker evaluation (e.g., 'has_unblocking_automation', 'escalation_required', 'external_blocker').
- 3Ask Notis: 'When a Linear issue changes to blocked status, check my Apilio conditions to find unblocking paths or trigger escalation.' Create via portal or chat.
- 4Select 'Issue Updated' as your trigger and choose a notification channel.
- 5Test by marking an issue as blocked and verify conditions are evaluated.
Questions about this workflow
What conditions should I set up?
Start with: 'can this be auto-unblocked?', 'does this need escalation?', 'is this an external blocker?'. Expand based on your common blocker types.
How do I know if a blocker can be auto-resolved?
You define this in your Apilio conditions. Common examples: dependency completed, external service back online, or reviewer became available.
Can I manually override blocker decisions?
Yes. You can always update issue status manually or modify conditions in Apilio. Automation provides suggestions, not hard locks.
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.