Let source page corrections reach the map
Edit a location detail on a Notion page and have Notis refresh its corresponding feature in Felt, reducing the chance outdated information stays in view.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
Action
Create or Update Elements
Tool to create new elements or update existing elements on a map via geojson featurecollection. use when you need to batch add or modify elements on a specified map after confirming the map id.
Why this helps
Small corrections to location notes can be forgotten when the map is maintained separately.
- Keep a map feature closer to the latest source-page detail.
- Reduce manual checking after a correction.
- Protect attention for decisions instead of duplicate updates.
Setup
Build it in a few focused steps.
- 1Connect Notion and Felt to Notis once in the portal.
- 2Write a prompt asking Notis to update the matching geographic feature when the specified Notion page content changes.
- 3Select Page Updated for the specified Notion page.
- 4Choose a run-report channel and test by making a real content correction.
Questions about this workflow
How does Page Updated differ from Page Content Updated?
Page Updated fires when any block within a specified page is updated. Page Content Updated is the content-edit event and can also be scoped to a page.
Can this update a feature on any map?
The prompt should name the existing Felt map and explain how to identify the matching feature.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Felt. A trigger fires from one place; an action lands in another.
Notion triggers
Felt actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create or Update Elements
Tool to create new elements or update existing elements on a map via geojson featurecollection. use when you need to batch add or modify elements on a specified map after confirming the map id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new felt project. use when you need to initialize a project with a specific name, and optional description or organization context.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Element
Tool to delete a specific element from a map. use when you have both map and element ids and need to remove the element permanently.
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.
Delete Layer
Tool to delete a specific layer from a map. use when you have the map's and layer's ids and need to remove it permanently.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Map
Tool to delete a specific map. use when you have the map's id and want to permanently remove it. returns no content (http 204) on success.
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.
Delete Project
Tool to delete a project and all its contents. use when you need to permanently remove a project after confirmation.
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.
Duplicate Map
Tool to duplicate an existing map in felt. use when you need a clone of a map as a starting point.
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.
Create Felt Project
Tool to create a new felt project. use when you need to initialize a project with a specific name and optional description or organization context.
Connect any two apps with Notis in the middle.
Notion and Felt, 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 Felt.