Review a visitor's Formdesk entries from your Notion workflow
Connect a portal update to a focused review of the visitor's submitted entries.
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
Manage Visitor Entries
Tool to list or retrieve a visitor's own form entries. Use after authenticating visitor.
Why this helps
Finding an individual's submissions during a follow-up can interrupt the work already underway in Notion.
- Retrieve the authenticated visitor's own entries when needed.
- Bring submission history into an active follow-up workflow.
- Reduce manual navigation during account review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Formdesk to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve the authenticated visitor's own Formdesk entries when the designated Notion page changes.
- 3Select Page Content Updated for that page, choose a run-report channel, and test using the intended authenticated visitor.
Questions about this workflow
Whose entries does this retrieve?
It retrieves the authenticated visitor's own form entries.
Does this authenticate the visitor automatically?
The visitor must be authenticated for the action to retrieve their own entries.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Formdesk. A trigger fires from one place; an action lands in another.
Notion triggers
Formdesk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Automatic Login
Tool to perform automatic login to Formdesk and retrieve an access token. Use when you need to authenticate with username and password.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Formdesk Entry
Tool to submit a new entry to a Formdesk form. Use after collecting all form field values to send a new entry for a specific formId. Example: "Submit entry to form 12345 with first_name='Bob', email='bob@example.com'."
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Field
Tool to create a new field in a specific Formdesk form. Use after you have the formId and need to extend the form schema with an additional input.
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.
Create Visitor
Tool to add a new visitor to a specific Formdesk form. Use when you need to register a visitor's metadata (e.g., name, email) before submitting entries.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Formdesk Entry
Tool to delete a specific entry from a Formdesk form. Use after confirming the target entry exists.
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 Field in Formdesk
Tool to delete a specific field in a Formdesk form. Use after confirming formId and fieldId.
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.
Delete Form in Formdesk
Tool to delete a specific form. Use when you need to permanently remove a form after confirming it's no longer needed.
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.
Delete Visitor in Formdesk
Tool to delete a specific visitor in a Formdesk form. Use after confirming formId and visitorId.
Connect any two apps with Notis in the middle.
Notion and Formdesk, 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 Formdesk.