Check the expo list when a Linear project appears
New projects often arrive before the full event context is obvious. Have Notis check Expofp's expo list while the project is fresh.
Trigger
Project Created
Fires when a new Linear project is created. Covers projects in both public and private teams — polls with the connected user's token, so visibility matches what the connected user can see in Linear.
Action
List All Expos
Tool to list all expos. uses mock api endpoint for testing.
Why this helps
A founder may lose track of whether a project already has a corresponding expo record while switching between planning and setup.
- Bring the expo lookup to the start of project planning.
- Help avoid duplicating event records.
- Give the team one less manual search to remember.
Setup
Build it in a few focused steps.
- 1Connect Linear and Expofp to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Describe that each new Linear project should prompt a list of Expofp expos for review.
- 4Select the Project Created trigger and choose a run-report channel.
- 5Test with a real project and check that the output helps identify relevant expos.
Questions about this workflow
Will every new Linear project run the check?
Yes, if you select the Project Created trigger. Include event context in your prompt so Notis can make the result useful.
Does Expofp support creating expos through this action?
The supplied Expofp action lists expos. This workflow uses that lookup and does not claim to create or update expo records.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Expofp. A trigger fires from one place; an action lands in another.
Linear triggers
Expofp actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Category
Tool to add a new category to an expo. use when you have both the expo event id and a valid api token. example: "add category 'keynotes' to event 2655."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List All Expo Extras
Tool to list all extras for an expo. use after obtaining a valid exporter api token and expo event id. example: "list all extras for event 2655."
Comment Received Trigger
Triggered when a comment is received.
List All Expos
Tool to list all expos. uses mock api endpoint for testing.
Issue Created Trigger
Triggered when a new issue is created.
Remove Category
Tool to remove a category from an expo. use when you have the category id and a valid api token. example: "remove category #123."
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Update Category
Tool to update an existing category. use when you have the category id and a valid api token. example: "update category #1 name to 'category blue'."
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 Expofp, 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 Expofp.