Follow through on source references across your workspace
Let a page event cue retrieval of the Metaphor documents it actually names.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
Get document contents by IDs
Tool to retrieve parsed html/text contents and metadata for documents by their ids." use when you need to fetch the full text and metadata of multiple documents at once.
Why this helps
References spread across workspace pages are easy to forget when context switching interrupts a research session.
- Covers created and updated pages across the accessible workspace.
- Retrieves only documents identifiable by referenced IDs.
- Makes research follow-through easier to keep in motion.
Setup
Build it in a few focused steps.
- 1Connect Notion and Metaphor to Notis once in the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3In a single instruction, tell Notis to retrieve Metaphor contents for any document IDs explicitly cited in a newly created or updated Notion page.
- 4Select All Page Events and a report channel; test with a page that contains a valid ID.
Questions about this workflow
Will this scan pages to discover new Metaphor sources?
No. It retrieves documents by ID, so the page must contain the Metaphor document IDs.
Is this a broad trigger?
Yes. All Page Events covers page creations and updates across the workspace the integration can access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Metaphor. A trigger fires from one place; an action lands in another.
Notion triggers
Metaphor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get document contents by IDs
Tool to retrieve parsed html/text contents and metadata for documents by their ids." use when you need to fetch the full text and metadata of multiple documents at once.
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 Metaphor, 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 Metaphor.