Resolve document account uncertainty from a Notion comment
When a Notion comment raises a question about document access, have Notis check which Docupilot account is connected so the next step is clearer.
Trigger
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.
Action
Get Authenticated User
Tool to retrieve information about the authenticated user. use after authentication to confirm identity and fetch user account details.
Why this helps
A small access question can turn into a context-switching detour when the connected document account is unclear.
- Get the connected account detail in response to a discussion cue.
- Reduce back-and-forth caused by account uncertainty.
- Keep the access question close to where it was raised.
Setup
Build it in a few focused steps.
- 1Connect Notion and Docupilot to Notis once in the portal.
- 2Create the automation in the portal or describe the account-check outcome to Notis.
- 3Use one instruction asking Notis to report the authenticated Docupilot user when a relevant Notion comment is created.
- 4Choose Notion Comment Created and select a reporting channel; the integration needs Read comments access.
- 5Test with a comment on a relevant page and verify the account check is reported.
Questions about this workflow
Does the comment event work without comment access?
No. The Notion integration needs Read comments capability, and an older connection may need re-authorization after enabling it.
Does this grant document access?
No. It reports the authenticated account identity; it does not change permissions.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Docupilot. A trigger fires from one place; an action lands in another.
Notion triggers
Docupilot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Docupilot Folder
Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Docupilot Folder
Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List all folders
Tool to list all folders. use after authentication to fetch available workspace folders.
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.
Get Authenticated User
Tool to retrieve information about the authenticated user. use after authentication to confirm identity and fetch user account details.
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 Docupilot, 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 Docupilot.