Handle launch discussions with current context
A comment on the launch page can trigger an event review, making it easier to pick up the conversation and move forward.
Trigger
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.
Action
Get Fomo Events
This tool retrieves a list of all events from your fomo application. the endpoint is self-contained and doesn't require any external resource ids, making it independently executable. authentication is handled through the api token.
Why this helps
Launch discussions often require reconstructing status across comments, notes, and activity before anyone can take the next step.
- Add current event context to a launch discussion follow-up.
- Reduce the effort of reopening tools to rebuild status.
- Make it easier to resume a conversation after interruptions.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fomo to Notis once in the portal.
- 2Create an automation in Automations, or tell Notis to retrieve Fomo events when a launch-page comment is added.
- 3Write one plain-language instruction asking Notis to summarize activity relevant to the commented-on launch page.
- 4Select the Notion comment-created trigger and scope it to the launch page if useful; choose a channel for run reports.
- 5Test by adding a comment to the launch page.
Questions about this workflow
What is required for Notion comments?
Enable the Read comments capability for the integration. If already connected, re-authorize after enabling it so comment events can flow.
Does it notify commenters in Fomo?
No. The action retrieves existing Fomo events and Notis reports a summary through the selected run-report channel.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fomo. A trigger fires from one place; an action lands in another.
Notion triggers
Fomo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Fomo Events
This tool retrieves a list of all events from your fomo application. the endpoint is self-contained and doesn't require any external resource ids, making it independently executable. authentication is handled through the api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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 Fomo, 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 Fomo.