Check submitted feedback when Notion review notes change
As review notes develop, pull in the related form responses so you can work from both your notes and the feedback people submitted.
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
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
Why this helps
Review decisions require jumping between notes and forms, breaking concentration and increasing the chance of missed input.
- Keep submitted feedback close to evolving review notes.
- Reduce context switching during a review cycle.
- Make it easier to spot input that needs a response.
Setup
Build it in a few focused steps.
- 1Connect Notion and Byteforms to Notis once through the portal.
- 2Create an automation or ask Notis to retrieve responses from the appropriate Byteforms form when a review page's content changes.
- 3Choose Page Content Updated and scope it to the review page or its data source; choose a report channel.
- 4Test with one review-note edit and inspect the retrieved responses.
Questions about this workflow
Can it target one review page?
Yes. Page Content Updated supports a page scope as well as data source and parent page scopes.
What should I include in the prompt?
Name the relevant Byteforms form and explain how its responses should support the review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Byteforms. A trigger fires from one place; an action lands in another.
Notion triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
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.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
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 Byteforms, 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 Byteforms.