Get a useful review when a Notion page changes
When page content shifts, Griptape can prepare the summary or review you asked for, helping you return to the work without reconstructing every edit.
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
Assistant Run Creation
Tool to initiate a new assistant run. Use when starting a fresh execution with custom arguments or resources after selecting the assistant.
Why this helps
Returning to an edited page often means scanning the whole thing to find what changed.
- Get a focused review after content edits.
- Spend less time finding the meaningful changes.
- Make recurring page checks easier to resume.
Setup
Build it in a few focused steps.
- 1Connect Notion and Griptape to Notis once.
- 2Create an automation and write one plain-language instruction for reviewing page content changes.
- 3Choose the Notion Page Content Updated trigger and optionally scope it to a page or data source.
- 4Choose a run-report channel, then test by editing one real page.
Questions about this workflow
Does every keystroke start a run?
Notion aggregates content edits over a short window, typically around 60 seconds, before sending the event.
Can I use this for one page?
Yes. The trigger can be scoped to a specific page, a data source, or a page's immediate children.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Griptape. A trigger fires from one place; an action lands in another.
Notion triggers
Griptape actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Assistant Creation
Tool to create a new assistant. Use when you need to register a uniquely named assistant in Griptape Cloud before initiating runs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Assistants
Tool to list all assistants. Use after authenticating with Griptape Cloud to retrieve available assistants. Supports optional pagination.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Cancel Assistant Run
Tool to cancel an ongoing assistant run. Use when you need to stop a run prematurely after confirming the run ID is valid.
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.
Assistant Run Creation
Tool to initiate a new assistant run. Use when starting a fresh execution with custom arguments or resources after selecting the assistant.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Assistant Run Error Details
Tool to fetch detailed error information for a specific assistant run. Use after an assistant run has failed to inspect error details.
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.
Stream Assistant Run Events
Tool to stream real-time events for a specific Assistant run. Use after initiating a run to monitor its progress.
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.
List Assistant Runs
Tool to list all runs for a given assistant. Use when you need historical run executions for analysis after using the assistant.
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.
Assistant Run Logs Retrieval
Tool to retrieve logs generated during the execution of a specific assistant run. Use after confirming the run_id to fetch all log events once the run has completed.
Connect any two apps with Notis in the middle.
Notion and Griptape, 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 Griptape.