Add Fomo activity to issue priority reviews
When issue details change, a quick event retrieval can bring customer activity into your next priority decision.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Get Fomo Events
This tool retrieves a list of all events from your fomo application. the endpoint is self-contained and doesn't require any external resource ids, making it independently executable. authentication is handled through the api token.
Why this helps
Reprioritizing work takes focus, and a customer activity check can become one more task to remember.
- Retrieve Fomo events after an issue update.
- Consider recent activity while reviewing changed issue priorities.
- Keep the next customer context check attached to the issue change.
Setup
Build it in a few focused steps.
- 1Connect Linear and Fomo to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to retrieve Fomo events when an issue's priority is updated.
- 3Write one plain-language instruction for the event summary and priority review context.
- 4Choose the Linear Issue Updated trigger and select a channel for run reports.
- 5Test by updating a real issue and confirming the event lookup appears in the run.
Questions about this workflow
Can I set a priority-only trigger?
The provided trigger is Issue Updated, which can include changes such as labels or status. Describe the relevant context in your instruction.
Does this assign work based on Fomo events?
No. It retrieves events to support your review and does not change Linear assignments.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Fomo. A trigger fires from one place; an action lands in another.
Linear triggers
Fomo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Fomo Events
This tool retrieves a list of all events from your fomo application. the endpoint is self-contained and doesn't require any external resource ids, making it independently executable. authentication is handled through the api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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 Fomo, 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 Fomo.