Bring a document inventory into approval follow-up
A comment on an approval block can be the cue to retrieve the Boloforms document list, helping you gather paperwork context before responding.
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
Approval discussions can stall when someone has to leave the thread to figure out which documents are available.
- Prompt a paperwork inventory at the point of reviewer feedback.
- Keep approval follow-up closer to the discussion.
- Reduce interruptions from searching a separate document tool.
Setup
Build it in a few focused steps.
- 1Connect Notion and Boloforms to Notis once through the portal and authorize Notion comment access.
- 2Create an automation in the portal, or ask Notis to retrieve Boloforms documents when a comment is added to the approval block or page.
- 3Select New Comment and specify the relevant block or page; choose a channel for run reports.
- 4Test with one real approval comment and check the document list.
Questions about this workflow
How is this different from a workspace-wide comment trigger?
New Comment is scoped to a specified Notion block or page. Comment Created can optionally filter by page and otherwise applies workspace-wide.
Does the workflow approve or sign anything?
No. Its Boloforms action retrieves 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.