Review hidden form configuration when a process changes
A change to the process can be a good time to inspect the hidden fields that support its Feathery form.
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
List Hidden Fields
Tool to list all hidden form fields in the account. Use when you need to retrieve hidden field configuration before processing form submissions.
Why this helps
Invisible form configuration can be forgotten when the visible process changes, creating confusion during later troubleshooting.
- Surfaces hidden field configuration for inspection.
- Connects process updates to a practical form review.
- Helps keep internal form behavior understandable.
Setup
Build it in a few focused steps.
- 1Connect Notion and Feathery to Notis once in the portal.
- 2Create an automation in Automations -> New Automation or ask Notis to set it up conversationally.
- 3In one instruction, ask Notis to list Feathery hidden fields relevant to the process when its Notion record changes.
- 4Select Page Properties Updated and choose a channel for run reports.
- 5Test with one process update and review the returned hidden fields.
Questions about this workflow
Does this create or change hidden fields?
No. List Hidden Fields retrieves the account's hidden field configuration.
Can this be used during a review?
Yes. It surfaces the current hidden field setup when the Notion process record changes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Feathery. A trigger fires from one place; an action lands in another.
Notion triggers
Feathery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Edit Feathery Account
Tool to edit an existing account’s role and permissions. Use when modifying account settings after confirming identity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Info
Tool to get your Feathery team name and list of accounts. Use when you need to fetch your team's account info.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Fill or sign document template
Tool to fill or sign a Feathery document template. Use when you need to generate a completed or signed document file after mapping template fields.
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.
List Document Envelopes
Tool to list generated document envelopes by document or user ID. Use when you need to retrieve envelope records for auditing or tracking.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create hidden field
Tool to create a new hidden field in a form. Use when you need to add a non-visible field after confirming you have a unique field_id.
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.
Delete Form
Tool to delete an existing form. Use when you need to permanently remove a form after confirmation.
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.
Get form schema
Tool to retrieve the schema of a specific form. Use after confirming the form ID.
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.
List Forms
Tool to list all forms in your Feathery account. Use when you need to view or filter available forms.
Connect any two apps with Notis in the middle.
Notion and Feathery, 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 Feathery.