Carry population-plan changes into Faraday scopes
When the plan changes, let Notis prompt the scope rerun instead of relying on a mental note to revisit it later.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Force Update Scope
Tool to trigger a rerun for a scope resource. Use when you need to force rebuild a scope, causing it to reprocess and update its data.
Why this helps
A revised target population in Notion can leave the Faraday scope out of sync until someone remembers the follow-up.
- Connects revised population plans to scope maintenance.
- Makes follow-up less dependent on memory.
- Keeps prediction scope work tied to current intent.
Setup
Build it in a few focused steps.
- 1Connect Notion and Faraday to Notis once through the portal.
- 2Create the automation in Automations or ask Notis to set it up conversationally.
- 3Write one prompt asking Notis to force-update the relevant Faraday scope when its Notion population plan changes.
- 4Select Page Content Updated for the relevant page or parent and choose a run-report channel.
- 5Test one plan edit and review the scope rerun.
Questions about this workflow
What does the scope update action do?
It triggers a rerun for a scope, causing Faraday to rebuild it.
Can I scope this to one planning page?
Yes. The Notion content-update trigger supports a specific page or immediate parent page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Faraday. A trigger fires from one place; an action lands in another.
Notion triggers
Faraday actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Cohort
Tool to archive a cohort in Faraday. Use when you need to stop updates to a cohort while keeping it visible.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Connection
Tool to archive a connection in Faraday. Use when you need to stop updates to a connection while keeping it visible.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Archive Dataset
Tool to archive a dataset in Faraday. Use when you need to archive a dataset and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
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.
Archive Outcome
Tool to archive an outcome in Faraday. Use when you need to stop updates to an outcome while keeping it visible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Archive Persona Set
Tool to archive a persona set in Faraday. Use when you need to stop updates to a persona set while keeping it visible.
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.
Archive Place
Tool to archive a place in Faraday. Use when you need to stop updates to a geospatial area or address set while keeping it visible.
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.
Archive Scope
Tool to archive a scope in Faraday. Use when you need to stop updates to a scope while keeping it visible.
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.
Archive Stream
Tool to archive a stream in Faraday. Use when you need to archive a stream and optionally its downstream resources. Archiving stops updates to the resource but keeps it visible.
Connect any two apps with Notis in the middle.
Notion and Faraday, 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 Faraday.