Make campaign closeout easier to complete
Mark a campaign complete and get a concise Fomo activity summary to help capture useful closeout context before moving on.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
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
Founders often finish the visible work but skip the small closeout review, leaving useful context hard to recover later.
- Connect completion status to an activity review.
- Capture context while the campaign is still easy to recall.
- Make closeout less likely to disappear behind the next priority.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fomo to Notis once in the portal.
- 2Create an automation in Automations, or ask Notis to retrieve Fomo events when a campaign is marked complete.
- 3Use one plain-language instruction asking for a short event summary to support campaign closeout.
- 4Choose the Notion page-properties-updated trigger for the campaign database and a channel for run reports.
- 5Test by marking one completed campaign in Notion.
Questions about this workflow
Does it create a campaign report?
The available action retrieves Fomo events. Notis can summarize those events for the run, but does not create a separate report in Fomo.
Can I preserve the recap in Notion?
This trigger and action package does not include a Notion write action. Review the run output in the selected 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.