Keep event category names aligned with project updates
A project update can explain a change in direction. Use it to refresh the matching Expofp category while the new language is clear.
Trigger
Project Update Posted
Fires when a project status update is posted on the Linear project's Updates tab. Covers projects in both public and private teams — polls with the connected user's token.
Action
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'."
Why this helps
When project language changes, an older category label may cause unnecessary questions during event handoffs.
- Refresh event labels when project direction changes.
- Keep handoff language consistent across tools.
- Reduce questions caused by outdated categories.
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 describe it to Notis in plain language.
- 3Tell Notis when a posted project update should rename a related Expofp category and provide the intended label.
- 4Select the Project Update Posted trigger and choose a channel for run reports.
- 5Test with a real project update and valid Expofp category ID and API token.
Questions about this workflow
Does this use an update from the project's Updates tab?
Yes. The selected trigger fires when a project status update is posted on the Updates tab.
Can the workflow add a new category if needed?
This action updates an existing category. Adding a new category requires the separate add-category action.
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.