Pair new Notion subpages with discovery forms
A new client, initiative, or research subpage can trigger a focused Byteforms form that gathers context before you switch into follow-up mode.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Create form
Tool to create a new form. use when you need to define and store a form structure.
Why this helps
New threads of work start with incomplete context, forcing you to reconstruct the background later.
- Collect background while a new work thread is still fresh.
- Give contributors a repeatable way to share context.
- Reduce later searching through old notes and messages.
Setup
Build it in a few focused steps.
- 1Connect Notion and Byteforms to Notis once via the portal.
- 2Create an automation or ask Notis in plain language to prepare a discovery form when a subpage is added beneath a chosen hub.
- 3Select Page Added to Page for the hub and choose a run-report channel.
- 4Add one test subpage and inspect the created form.
Questions about this workflow
Does it follow subpages under any page?
This trigger is configured for a specified parent page, so choose the hub where new subpages represent work that needs context.
What kind of context should the form ask for?
State the background details you want contributors to share in the plain-language prompt.
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.