Recheck Fomo activity when project plans change
A shift in project status, lead, target date, or priority can be a good time to revisit customer activity.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
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
Changes to project plans require attention, and checking Fomo separately adds another follow-up to remember.
- Retrieve Fomo events after Linear project properties change.
- Review customer activity during project replanning.
- Keep the activity check attached to the project change that prompted it.
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 a project property changes.
- 3Write a single plain-language prompt explaining what project context and event summary to report.
- 4Select the Linear Project Properties Updated trigger and choose a channel for run reports.
- 5Test with one real project property change and review the retrieved events.
Questions about this workflow
What kinds of project updates can trigger it?
The trigger covers project property changes such as status, lead, target date, or priority.
Does it update Fomo campaign settings?
No. The available Fomo action retrieves the event list.
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.