Recheck the available forms when request details change
When key request details shift in Notion, have Notis retrieve your Fillout form list for a fresh review.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Get forms
Tool to retrieve a list of all forms in your account. use when you need to list your forms after authenticating with fillout.
Why this helps
A changed request can make yesterday's form choice irrelevant, while the reason for revisiting it gets buried.
- Revisit the form options after a request changes.
- Reduce the chance of acting on outdated intake context.
- Keep the follow-up anchored to the Notion update.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fillout forms to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve Fillout forms when a relevant Notion request changes.
- 3Select the Notion Page Properties Updated trigger and choose a channel for run reports.
- 4Test by updating one real request and confirm Notis retrieves the form list.
Questions about this workflow
Can the trigger watch only one database?
The provided trigger supports an optional data source scope. Select the trigger; the automation prompt describes the intended request review.
Does the lookup submit or edit a form?
No. It retrieves the forms in your Fillout account and does not change or submit them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fillout forms. A trigger fires from one place; an action lands in another.
Notion triggers
Fillout forms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authorize OAuth
Tool to initiate the oauth authorization process for third-party applications. use when you need to generate the url to redirect your users to the fillout consent page.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get forms
Tool to retrieve a list of all forms in your account. use when you need to list your forms after authenticating with fillout.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Invalidate Access Token
Tool to revoke an existing oauth access token. use when the user logs out or you need to programmatically invalidate a token after deauthorization. example: "invalidate token abcdefg123456". this endpoint does not return a json body. successful calls return http 200 or 204.
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 Fillout forms, 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 Fillout forms.