Make feedback collection part of launch planning
When the launch page is created, let Notis prepare the survey you planned to send afterward.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create Form
Tool to create a new form with specified fields and settings. use before collecting submissions to define form structure.
Why this helps
Feedback surveys are easy to forget when launch tasks, announcements, and follow-ups compete for attention.
- Put survey setup alongside launch planning.
- Avoid a separate reminder to create a feedback form.
- Make post-launch learning easier to schedule.
Setup
Build it in a few focused steps.
- 1Connect Notion and Cabinpanda to Notis once through the portal.
- 2Create an automation in the portal, or tell Notis in plain language to prepare a survey when a launch page is created.
- 3Describe the survey purpose and desired form in one instruction to Notis.
- 4Select the Notion Page Created trigger for the launch parent page and choose a channel for run reports.
- 5Test by creating a real launch page and checking the form in Cabinpanda.
Questions about this workflow
Can I use this for a specific launch page?
Yes. Choose the Page Created trigger scoped to the parent page where launch pages are added.
Will the automation send the survey to customers?
No. The selected Cabinpanda action creates the form; distribution is a separate step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cabinpanda. A trigger fires from one place; an action lands in another.
Notion triggers
Cabinpanda actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Form
Tool to create a new form with specified fields and settings. use before collecting submissions to define form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a specific form by its id. use after confirming the target form exists and is safe to remove.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Integration
Tool to delete a specific integration by its id. use when you need to remove or disable an existing integration (e.g., webhook) after confirming the integration id.
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 Details
Tool to retrieve details of a specific form by its id. use when you need form metadata (fields, labels, timestamps) before processing or submitting data.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Integration Details
Tool to retrieve details of a specific integration by its id. use when you need to inspect integration settings or status after obtaining its id.
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 Profile
Tool to retrieve the authenticated user's profile information. use after obtaining valid api credentials to access user details.
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.
List Forms
Tool to retrieve a list of all forms associated with the account. use when you need to fetch form details for management or analysis.
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.
List Integrations
Tool to retrieve a list of all integrations for the account. use when you need to inspect available or active integrations before managing them.
Connect any two apps with Notis in the middle.
Notion and Cabinpanda, 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 Cabinpanda.