Check Formsite details when a Notion form spec changes
A changed spec can leave you wondering whether the live form is still the right one. Ask Notis to fetch the current Formsite details when the Notion record changes, then bring the useful facts back in its run summary.
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 Form Details
This tool retrieves detailed information about a specific form in formsite. it provides comprehensive details including the form's internal description, directory identifier, name, publishing information (embed code and form link), current state (e.g., "open"), and statistics (file size and number of results).
Why this helps
A form change recorded in one tool can be easy to forget when the live form is managed elsewhere.
- See current form state and publishing information alongside a spec update.
- Catch a closed or outdated form before relying on it.
- Avoid manually reopening Formsite during each review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Formsite to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally for the workflow.
- 3Write one instruction asking Notis to use the changed Notion form record to identify the relevant Formsite form, retrieve its details, and summarize status and publishing information.
- 4Pick the Notion Page Properties Updated trigger and a run-report channel.
- 5Test by changing a real form-spec record and checking the report.
Questions about this workflow
Does the workflow update the Formsite form?
No. It retrieves form details for review and does not change Formsite.
Can the trigger be limited to one database?
The Notion trigger can be scoped to a data source when selecting it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Formsite. A trigger fires from one place; an action lands in another.
Notion triggers
Formsite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Form Details
This tool retrieves detailed information about a specific form in formsite. it provides comprehensive details including the form's internal description, directory identifier, name, publishing information (embed code and form link), current state (e.g., "open"), and statistics (file size and number of results).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Form Items
This tool retrieves all items (questions) for a specific form using the get https://{server}.formsite.com/api/v2/{user dir}/forms/{form dir}/items endpoint. it is an independent action that only requires the form directory (obtainable via formsite list all forms) to retrieve the structure and details such as item ids, question types, text, answer choices, required status, and other properties.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Form Results
This tool retrieves the latest form results from a specified formsite form. it uses the get https://{server}.formsite.com/api/v2/results/latest endpoint to fetch results independently, handling required parameters such as form id, limit, page, and sort direction without referring to external resource ids.
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 Webhooks
This tool retrieves all webhooks configured for a specific form in formsite. it uses the get https://{server}.formsite.com/api/v2/{user dir}/forms/{form dir}/webhooks endpoint to fetch webhook configurations, including url, status, settings, and triggers.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List All Forms
This tool retrieves a list of all forms in the user's formsite account. it provides essential information such as form id, form name, form directory, creation date, last modified date, status, access level, and other metadata. it serves as a foundational tool for further operations.
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 Formsite, 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 Formsite.