Organize public event work from the first issue
Let a new public event issue prompt the category setup that helps the team keep related event information organized.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
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."
Why this helps
When a new task starts quickly, a simple categorization step can get lost among more urgent planning work.
- Make category setup part of event issue kickoff.
- Keep public event work easier to organize.
- Avoid relying on a later cleanup reminder.
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.
- 3Describe which category to add to the matching Expofp expo when a public event issue is created.
- 4Select the Public Team Issue Created trigger and choose a run-report channel.
- 5Test with a real public issue and confirm the valid event ID and API token are available.
Questions about this workflow
Can it make a different category for every event?
The action adds a category. Describe the appropriate category in your prompt and provide enough event context for Notis to choose the right expo.
Does it create a booth assignment?
No. The supplied Expofp action adds a category.
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.