Private Issue Escalation
Private team issues get routed right. Sensitive work is escalated through the correct channels automatically.
Trigger
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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
Private team issues get lost in the mix. Sensitive work should go to specific people but you manually handle routing, creating bottlenecks and security risks.
- Routes sensitive work through correct channels automatically
- Reduces manual escalation overhead for private issues
- Ensures sensitive issues reach the right people
- Maintains security without creating manual bottlenecks
Setup
Build it in a few focused steps.
- 1Connect Linear and Apilio to Notis (one-time setup).
- 2In Apilio, create logicblocks for different escalation paths (e.g., 'security_escalation', 'exec_escalation', 'urgent_private').
- 3Ask Notis: 'When an issue is created in a private Linear team, fetch my Apilio escalation logicblocks to route it correctly.' Create via portal or chat.
- 4Select 'Private Team Issue Created' as your trigger.
- 5Test by creating an issue in a private team and verify the appropriate escalation logicblock activates.
Questions about this workflow
How do I decide which escalation paths to create?
Think about the sensitivity levels and routing requirements in your private teams. Examples: security issues, executive-only items, legal concerns.
What if I need different routing for different private teams?
Create separate logicblock sets for each private team. Your Notis prompt specifies which team's issue came in and selects the right routing.
Can team members opt out of routing?
Routing follows your automation rules. If you want exceptions, add them to your Notis prompt (e.g., 'unless labeled no-escalate').
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.