Get cited context for a chosen Notion thread
Keep a useful discussion moving by asking Copilot for a sourced response when a new comment appears in the thread you care about.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
Ask Copilot
Get Copilot's consumer-app answer to a prompt, with cited sources, in a chosen country.
Why this helps
A focused discussion can lose momentum when a new question requires leaving the thread to research.
- Focus research on one important discussion.
- Get citations to help evaluate a response.
- Avoid re-entering the topic in a separate chat.
Setup
Build it in a few focused steps.
- 1Connect Notion and cloro to Notis once in the portal and enable comment access.
- 2Create an automation or ask Notis in plain language to get Copilot context for comments in a specified thread.
- 3Select New Comment for the chosen page or block and choose a report channel.
- 4Add a real comment to that discussion and review the answer and cited sources.
Questions about this workflow
How do I keep it focused?
Use the New Comment trigger for the specific page or block that matters.
Will Copilot publish a reply?
No. Notis returns the answer and citations for your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to cloro. A trigger fires from one place; an action lands in another.
Notion triggers
cloro actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search Google
Search Google as a user in a chosen country and get the results page as JSON.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Ask Copilot
Get Copilot's consumer-app answer to a prompt, with cited sources, in a chosen country.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Ask Google AI Mode
Get Google AI Mode's answer to a prompt, with cited sources and product cards.
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.
Ask Gemini
Get Gemini's consumer-app answer to a prompt, with cited sources, in a chosen country.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Ask ChatGPT
Get ChatGPT's consumer-app answer to a prompt, with cited sources, in a chosen country.
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.
Search Google News
Search Google News as a user in a chosen country and get the articles as JSON.
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 cloro, 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 cloro.