Bring paperwork into client approval follow-up
A client approval comment can prompt Notis to retrieve the Boloforms document list, helping you gather context before deciding what to do next.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Why this helps
Client approvals create time-sensitive follow-up, and tracking down documents can turn one clear next step into several interrupted searches.
- Start a document check from the client approval discussion.
- Keep follow-up closer to the comment that prompted it.
- Lower the effort involved in resuming an approval review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Boloforms to Notis once through the portal and enable Notion comment access.
- 2Create an automation in the portal, or ask Notis to retrieve Boloforms documents when a comment is added to the client approval page.
- 3Select New Comment for the specific page or block and choose a channel for run reports.
- 4Test with one real client approval comment and review the returned list.
Questions about this workflow
Can the trigger be tied to one approval page?
Yes. New Comment is scoped to a specified Notion block or page.
Can Boloforms send the client a request here?
No. The only supplied Boloforms action gets the account document list.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Boloforms. A trigger fires from one place; an action lands in another.
Notion triggers
Boloforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Documents List
Tool to retrieve a list of documents associated with the account. use when you need to list all documents.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Boloforms, 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 Boloforms.