Find existing context when a decision needs it
A decision can stall when its context is scattered. Use a Notion comment as a cue to list Needle collections and see which knowledge base may help.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
List Collections
Tool to list collections. use after authenticating with your api key to page through collections.
Why this helps
Founders can lose time switching from a decision thread to a broad search for prior context.
- Keep decision follow-up close to the discussion.
- See available knowledge collections before searching from scratch.
- Reduce context switching during a decision.
Setup
Build it in a few focused steps.
- 1Connect Notion and Needle to Notis once through the portal.
- 2Create an automation in the portal or tell Notis in plain language to support decision comments.
- 3Write one instruction asking Notis to list Needle collections when a comment calls for background context and explain likely matches briefly.
- 4Select the Notion New Comment trigger for the relevant page or block and choose a reporting channel.
- 5Test by adding a real decision comment and checking the collection suggestions.
Questions about this workflow
How is this different from a workspace-wide comment trigger?
New Comment is intended for a specified Notion block or page, while Comment Created can cover comments across the accessible workspace.
Does it decide which option is correct?
No. It presents available collections as context for a human decision.
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.