Bring document visibility into your workday
For teams that benefit from a lightweight document check-in, Notion page activity can cue a fresh look at Documint's document list.
Trigger
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Action
List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
Why this helps
Documents can become hard to track when work is spread across many pages and attention is moving between projects.
- Create a document visibility cue around existing Notion activity.
- Make available outputs easier to inspect in context.
- Support a lightweight review habit across active work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Documint to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to list Documint documents when a Notion page is created or updated.
- 3Pick All Page Events and choose a channel for run reports.
- 4Test with a real page event and confirm the document list is useful at this frequency.
Questions about this workflow
Will this run often?
All Page Events can fire for page creation and updates across the workspace the integration can access. Consider whether that breadth fits your workflow.
Can the action filter documents by page?
The supplied List Documents action lists documents in the authenticated account; page-specific matching is not specified.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Documint. A trigger fires from one place; an action lands in another.
Notion triggers
Documint actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Template
Tool to permanently delete a single template by its id. use when you need to remove an outdated or unused template; ensure the template id is correct before calling.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Template
Tool to retrieve a single template by its id. use when you need to fetch details of a specific template before generating documents.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Documents
Tool to list all documents in the authenticated user's account. use after obtaining a valid api key.
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.
List Templates
Tool to list all templates in the authenticated user's account. use after obtaining a valid api key.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Template
Tool to update a single template by its id. use when you need to modify an existing template's settings or layout after fetching its current details.
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 Documint, 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 Documint.