Connect Notion to Formbricks
When something happens in Notion, Notis takes the next step in Formbricks. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Notion to Formbricks
View exampleTurn a research brief into a feedback survey
When a new research brief lands in Notion, create a Formbricks survey so customer discovery can start without a separate setup session.
View exampleKeep interview participants ready in Formbricks
When participant details change in a Notion database, create a Formbricks contact so the person is available for research follow-up.
View exampleConvert feedback discussion into a follow-up survey
A new Notion comment can capture a customer question worth validating. Have Notis create a Formbricks survey while the discussion is active.
View exampleCapture approved feedback as a Formbricks response
When a Notion page's content is updated with finalized feedback, create a Formbricks response from the information available in the page.
View exampleSet up response delivery from a Notion plan
When a Notion page documents a new feedback pipeline, create a Formbricks webhook to deliver survey response events to the planned endpoint.
View exampleKeep a Formbricks survey aligned with its Notion spec
When a survey specification changes in Notion, update its corresponding Formbricks survey so the working version stays aligned.
View exampleTurn a named feedback follow-up into a contact
When a Notion comment identifies someone to follow up with, create a Formbricks contact so the next conversation is easier to start.
View exampleRegister a survey display for a new campaign
When a campaign page is added to Notion, have Notis register the relevant Formbricks survey display when the campaign is ready to launch.
View exampleAdd a Formbricks attribute for a new research dimension
When a Notion data source gains a new research property, create a matching Formbricks attribute class to support useful segmentation.
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.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Notion and Formbricks
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.