Review account settings alongside process changes
A change to your documented workflow can be a useful reminder to check Jotform settings before the process is reused.
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 User Settings
Tool to retrieve the settings of the authenticated user. use after confirming a valid api key.
Why this helps
Process documentation and account configuration live in separate places, so updates can leave a founder unsure whether settings need review.
- Pair process documentation edits with a settings review prompt.
- Keep account configuration visible during workflow maintenance.
- Reduce the chance of forgetting a related review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Jotform to Notis in the portal once.
- 2Create an automation in the portal or by asking Notis in plain language.
- 3Write one instruction to retrieve Jotform settings when the selected process page content changes.
- 4Select Page Content Updated and scope it to the process page or data source.
- 5Choose a reporting channel and test by editing one real process page.
Questions about this workflow
Will it update any Jotform settings?
No. The action retrieves settings for review; it does not change them.
Can I monitor one process page?
Yes. The Page Content Updated trigger can be scoped to a specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Jotform. A trigger fires from one place; an action lands in another.
Notion triggers
Jotform actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get System Plan
Tool to retrieve details of a specific system plan. use when you need to check limits and pricing of a plan.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Details
Tool to retrieve details of the authenticated user, including account and usage info. use after confirming valid api key.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get User Folders
Tool to retrieve a list of folders created by the authenticated user. use when you need to enumerate user folders after confirming valid api credentials.
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 User Forms
Tool to retrieve a list of forms created by the authenticated user. use after setting up api key authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get User History
Tool to fetch user activity history records. use when auditing or filtering user actions by type or date.
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.
Get User Settings
Tool to retrieve the settings of the authenticated user. use after confirming a valid api key.
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 Jotform, 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 Jotform.