Turn file access questions into a clear check
A comment asking who can see a file can prompt Notis to look up its Files.com permissions and report the answer.
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
List Permissions
Tool to retrieve permissions for a specified resource. Use when you need to inspect who has access and what level for a given file or folder.
Why this helps
Access questions buried in page discussions can go unanswered when they require a separate permissions lookup.
- Notice access questions while they are being discussed.
- Get a current permission list for the referenced resource.
- Keep any access change as a deliberate human decision.
Setup
Build it in a few focused steps.
- 1Connect Notion and Files.com to Notis once in the portal, and ensure the Notion integration has Read comments enabled.
- 2Create an automation with a plain-language instruction to inspect and report Files.com permissions when a comment asks about access to a referenced file.
- 3Select the Notion Comment Created trigger and scope it to the relevant page if appropriate.
- 4Choose a channel for run reports and test with one real comment that names a resource.
Questions about this workflow
Does this work without comment access?
No. The Notion integration needs the Read comments capability, and may need re-authorization if that capability was enabled later.
Will the automation grant access?
No. It only lists permissions and reports them for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Files com. A trigger fires from one place; an action lands in another.
Notion triggers
Files com actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete API Key
Tool to delete an API key. Use when you need to revoke an API key after confirming its identifier.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Permission
Tool to delete a specified permission. Use when you need to remove a permission by its ID after verifying the identifier.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Share
Tool to delete a specified share link. Use when you need to revoke access to a shared item after confirming its share ID.
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 S3 Key for Upload
Tool to generate a temporary key for file uploads by uploading the file to Files.com. Useful when you need to host a local file temporarily before importing or sharing.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Folders
Tool to list folders. Use when you need to retrieve folders under a parent with pagination.
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.
List Groups
Tool to list groups. Use when you need to retrieve a paginated list of all groups before performing group-related operations.
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.
List Permissions
Tool to retrieve permissions for a specified resource. Use when you need to inspect who has access and what level for a given file or folder.
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 Files com, 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 Files com.