Critical Comment Escalation
Critical feedback triggers immediate response. Emergency protocols activate automatically when critical comments arrive.
Trigger
Public Team Comment Created
Fires when a new comment is posted on a *public-team* Linear issue. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_COMMENT_CREATED`.
Action
Get Conditions
Tool to fetch all evaluatable conditions. use when you need to list available conditions.
Why this helps
Critical feedback gets buried in comments. Important issues raised by team members don't get the escalation they need.
- Detects critical comments instantly without manual monitoring
- Activates emergency response protocols automatically
- Prevents critical feedback from being missed
- Ensures urgent issues get the attention they need
Setup
Build it in a few focused steps.
- 1Connect Linear and Apilio to Notis (one-time setup).
- 2In Apilio, define conditions for emergency protocols (e.g., 'activate_urgent', 'notify_leadership', 'escalate_to_ceo').
- 3Ask Notis: 'When a critical comment is posted on a public-team issue in Linear, check my Apilio conditions for emergency escalation.' Create via portal or chat.
- 4Select 'Public Team Comment Created' as your trigger and choose your notification channel.
- 5Test by posting a critical comment and verify your emergency protocols are evaluated.
Questions about this workflow
How do I mark a comment as critical?
Use a specific prefix (e.g., 'CRITICAL:') or tag in the comment. Your Notis prompt identifies critical comments based on your pattern.
What should my emergency protocols do?
Common options: create an urgent ticket, notify leadership, schedule an immediate sync, add to your top-priority list. Define what matches your actual response.
Can I have different escalation levels?
Yes. Create separate conditions for 'urgent', 'critical', and 'emergency'. Your Notis prompt evaluates the severity and triggers the right level.
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.