Bring Basin form details into support handoffs
Start support documentation with the relevant form metadata close at hand.
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
Get Form Details
Tool to retrieve detailed information about a specific form. use when you have a form id and need its metadata.
Why this helps
Support notes lose momentum when someone has to stop and search Basin for the form's details.
- Reduce lookup time while documenting a support issue.
- Give the handoff a more complete starting point.
Setup
Build it in a few focused steps.
- 1Connect Notion and Basin to Notis once.
- 2Create an automation with a plain-language instruction to retrieve the referenced form's details for a new support page.
- 3Choose the Notion Page Created trigger and a channel for run reports.
- 4Test with one real support page that identifies a Basin form and inspect the returned details.
Questions about this workflow
Does the action find a form from any page text?
The prompt should explain how the relevant Basin form is identified in the support page so Notis can interpret it.
Can this change the form?
No. Get Form Details retrieves information about the identified form.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Basin. A trigger fires from one place; an action lands in another.
Notion triggers
Basin 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 in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
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 Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Form
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
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 Integration
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
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 Project
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
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 Webhook
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
Connect any two apps with Notis in the middle.
Notion and Basin, 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 Basin.