Follow evidence questions back to the collection
A quick comment can flag a missing source or an open question. Have Notis list files in the relevant Needle collection so the next review starts with existing material.
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 Collection Files
Tool to list all files within a specific collection by its id. use when you have a collection id and need to retrieve its files. supports pagination.
Why this helps
Research questions in comment threads can be forgotten or require a separate round of searching.
- Bring existing collection files into evidence follow-up.
- Reduce repeat searching after a comment.
- Keep a research question connected to relevant material.
Setup
Build it in a few focused steps.
- 1Connect Notion and Needle to Notis once through the portal.
- 2Create an automation through the portal or ask Notis in plain language to follow up on research comments.
- 3Give one instruction to use a comment's context to identify the relevant Needle collection and list its files for review.
- 4Select the Notion Comment Created trigger and choose a run-report channel.
- 5Test with a real comment that points to a known research collection.
Questions about this workflow
Does this work on all comments?
The workspace-level Comment Created trigger can fire for any new comment the integration can access. Your instruction should describe which research comments merit a file review.
Does listing files verify the claims in them?
No. The action lists collection files; a person can review relevant documents and assess the evidence.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Needle. A trigger fires from one place; an action lands in another.
Notion triggers
Needle actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Collection
Tool to create a new collection. use after confirming the collection name.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete files from a collection
Tool to delete files from a specific collection by providing file ids. use after confirming valid file ids to remove from the collection.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get collection stats
Tool to retrieve statistics for a specific collection by its id. use when you need document count, index size, and timestamps after confirming the collection exists.
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 Collection Files
Tool to list all files within a specific collection by its id. use when you have a collection id and need to retrieve its files. supports pagination.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Collections
Tool to list collections. use after authenticating with your api key to page through collections.
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 Needle, 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 Needle.