Refresh event categories when public issue details change
When a public event issue's properties change the way the work should be grouped, update the related Expofp category while the new context is clear.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
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
A status or classification change may leave an event category out of date, making handoffs harder to parse.
- Keep category labels current after relevant property changes.
- Make public event handoffs easier to understand.
- Reduce later cleanup of stale labels.
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 to set it up conversationally.
- 3Describe which public issue property changes should prompt an Expofp category rename.
- 4Select the Public Team Issue Properties Updated trigger and choose a run-report channel.
- 5Test with a real update and provide the correct category ID and API token.
Questions about this workflow
Will every property change rename a category?
The trigger fires on issue property changes. Explain which changes matter and the intended rename in the prompt.
What does the action require?
A valid Expofp category ID and API token.
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.