Register Formbricks survey displays from Notion campaigns
Tie survey display records to the campaign launch plan already in your workspace.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Create Display
Tool to mark a survey as displayed or link it to a response. Use after obtaining the survey and environment IDs to register a display instance.
Why this helps
A planned survey launch can be missed in the gap between campaign preparation and display tracking.
- Keep display registration linked to campaign readiness
- Reduce forgotten launch tracking steps
- Make survey activity easier to relate to campaign work
Setup
Build it in a few focused steps.
- 1Connect Notion and Formbricks to Notis once in the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3In one instruction, ask Notis to create a Formbricks display for the identified survey when a campaign page is marked ready and the required IDs are available.
- 4Choose the Notion New Page trigger and a channel for run reports.
- 5Test with one real campaign record and confirm the display is registered.
Questions about this workflow
What information does display registration need?
The relevant survey and environment identifiers must be available to Notis for the Create Display action.
Can the workflow wait for launch readiness?
Yes. Include the readiness condition in the prompt so Notis does not register a display prematurely.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Formbricks. A trigger fires from one place; an action lands in another.
Notion triggers
Formbricks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Action Class
Tool to create a new action class. Use when defining custom action logic in your environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Attribute Class
Tool to create an attribute class in Formbricks. Use when you need to define new attribute classes for segmentation or attributes management.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Contact
Tool to create a new contact. Use when you need to register a contact in a Formbricks environment.
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 Display
Tool to mark a survey as displayed or link it to a response. Use after obtaining the survey and environment IDs to register a display instance.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Survey Response
Tool to create a response for a survey. Use after collecting all survey answers.
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.
Create Survey
Tool to create a new survey. Use after defining survey details and questions.
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.
Create Webhook
Tool to create a new webhook. Use when you need to register an external endpoint to receive form response events.
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 Attribute Class
Tool to delete an attribute class. Use when you need to remove an attribute class by its ID after confirming it's no longer needed.
Connect any two apps with Notis in the middle.
Notion and Formbricks, 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 Formbricks.