Turn Notion Category Briefs into Expofp Categories
Keep event setup moving: ask Notis to add an Expofp category when a new Notion page clearly requests one.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
Category requests can get buried in planning pages, leaving event setup waiting on someone to notice and act.
- Capture clear category requests at page creation.
- Reduce manual copying between planning and expo setup.
- Leave ambiguous or incomplete requests for review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Expofp to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use one plain-language instruction to add a category to the specified expo only when the new Notion page contains an approved category request and the expo ID is known.
- 4Select the Notion New Page trigger and choose where Notis reports runs.
- 5Test with one real category brief and confirm the result in Expofp.
Questions about this workflow
Will every new Notion page create a category?
The instruction should tell Notis to act only when the page clearly contains an approved category request and the needed expo details.
What if the expo ID is missing?
Have Notis report the missing detail for follow-up instead of attempting the category action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Expofp. A trigger fires from one place; an action lands in another.
Notion 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."
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List All Expos
Tool to list all expos. uses mock api endpoint for testing.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
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."
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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'."
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion 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.