Give every new client request a pipeline entry
Capture client requests when they enter Notion, giving you a dependable place to sort and follow up on incoming commitments.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Add Records
Tool to add records to a specified table in a Grist document. Use after confirming doc and table IDs.
Why this helps
Client requests can arrive while you are focused on delivery and become hard to recover later.
- Make new client requests visible for prioritization.
- Reduce the chance that a request stays only in a database row.
- Keep incoming work ready for a dedicated review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Grist to Notis once through the portal.
- 2Create an automation prompt asking Notis to add each new client request to your Grist pipeline.
- 3Choose New Page and scope it to the client-request data source.
- 4Pick a channel for run reports and test with one real request.
Questions about this workflow
Can I use the same pattern for another intake database?
Yes. Create a separate automation scoped to that data source and describe its purpose in the prompt.
Does this prioritize requests automatically?
The prompt can ask Notis to apply the prioritization approach you describe when adding the entry.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Grist. A trigger fires from one place; an action lands in another.
Notion triggers
Grist actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Records
Tool to add records to a specified table in a Grist document. Use after confirming doc and table IDs.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document
Tool to create a document in a workspace. Use when you need to add a new document programmatically after selecting a workspace.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create SCIM User
Tool to create a new SCIM user. Use when provisioning new user accounts via SCIM. Run after gathering all required user details.
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 Table
Tool to create tables in a document. Use after confirming the document ID. Creates one or more tables with specified columns in the given document.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Create Document Webhook
Tool to create a new webhook for a specified document. Use when you need to register webhook endpoints for document events in Grist. Run after confirming document 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.
Delete Attachment
Tool to delete a specified attachment from a Grist document. Use when you need to remove a file by providing its document and attachment IDs.
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 Column
Tool to delete a column from a Grist document table. Use after confirming document, table, and column IDs.
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 Grist Table Records
Tool to delete records from a specified Grist table. Use when you need to remove specific rows by their IDs. Use after confirming the row IDs exist.
Connect any two apps with Notis in the middle.
Notion and Grist, 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 Grist.