Comment Notification Routing
Your communication style is unique. Route comments through your preferred channels and notification formats automatically, no manual sorting required.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
Get String Variables
Tool to fetch all string variables. use after authenticating the apilio api.
Why this helps
Comments arrive in a flood. Some need immediate action, others are FYI, but you manually review each one instead of routing them smartly. Mentions get buried.
- Routes comments to the right place automatically
- Respects your notification preferences without manual setup
- Reduces notification fatigue from low-priority comments
- Ensures mentions never get lost in the noise
Setup
Build it in a few focused steps.
- 1Connect Linear and Apilio to Notis (one-time in the portal).
- 2Set up your notification preferences in Apilio as string variables (e.g., 'mention_channel', 'fyi_routing', 'urgent_flag').
- 3Ask Notis: 'When a comment is received on a Linear issue, fetch my Apilio notification preferences and route the alert accordingly.' Create via portal or chat.
- 4Select 'Comment Received' as your trigger and pick your notification channel.
- 5Test by commenting on an issue you're assigned to and verify routing matches your preferences.
Questions about this workflow
How do I set up notification preferences in Apilio?
Create string variables in Apilio (e.g., 'urgent_notification_channel', 'fy_i_routing'). Notis fetches these automatically and uses them to route comments.
Can I have different preferences for different types of comments?
Yes. Set multiple string variables in Apilio for different scenarios (mentions, replies, team updates). Your Notis prompt specifies which to use.
What if I'm in hyperfocus and don't want notifications?
Toggle a boolean flag in Apilio and Notis skips routing. Pause notifications without rewriting automation logic.
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.