Revisit customer activity when an issue changes
When issue details shift, a fresh look at Fomo events can help you reconsider urgency with less context switching.
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
Issue changes can prompt manual backtracking to see whether customer activity affects the work.
- Retrieve Fomo events when a Linear issue is updated.
- Reconsider issue urgency with current event information available.
- Reduce the chance that a changed issue sits without a customer context check.
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 after an issue update.
- 3Write one plain-language instruction describing how Notis should report the retrieved events with the changed issue.
- 4Select the Linear Issue Updated trigger and choose a channel for run reports.
- 5Test by updating one real issue and checking the resulting event summary.
Questions about this workflow
Which issue changes can start this automation?
The Issue Updated trigger fires when an issue is updated, including changes such as labels or status.
Will Fomo send a notification to an audience?
No. This workflow retrieves Fomo events for review; it does not send audience notifications.
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.