Keep private event labels current
A private planning change can affect how an event should be organized. Let the issue update prompt a clear category refresh in Expofp.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled 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 private plans shift, stale category names can make it harder for teammates to understand where work belongs.
- Keep private event organization aligned with current plans.
- Make handoffs clearer with current category names.
- Reduce forgotten cleanup after planning changes.
Setup
Build it in a few focused steps.
- 1Connect Linear and Expofp to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Tell Notis which private issue property changes should rename a corresponding Expofp category.
- 4Select the Private Team Issue Properties Updated trigger and choose a channel for reports.
- 5Test using a private issue the connected user can access, plus a valid category ID and API token.
Questions about this workflow
Does the private trigger use my access?
Yes. It polls with the connected user's token, so visibility reflects what that user can access.
Can it create a missing category instead?
This workflow uses the update-category action, which requires an existing category ID.
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.