Start collection from a research comment
When a teammate adds a research lead in Notion, ask Notis to start the corresponding Apify collection.
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
Run Actor Asynchronously
Tool to run a specific actor asynchronously. use when you need to trigger an actor run without waiting for completion and retrieve its run details immediately.
Why this helps
Useful leads in comment threads can be missed because they are separate from the tool used to gather web information.
- Make comment-based research leads easier to act on.
- Keep the conversation that prompted collection in Notion.
- Start collection without copying the idea into a separate task.
Setup
Build it in a few focused steps.
- 1Connect Notion and Apify to Notis once in the portal, with comment access enabled for Notion.
- 2Create an automation in the portal or ask Notis conversationally to act on research comments.
- 3In one instruction, explain which comments indicate a new web research lead and which Actor to run.
- 4Select the Notion Comment Created trigger and a channel for run reports.
- 5Test by adding a real research lead comment and verify that the Actor starts.
Questions about this workflow
Does the Notion connection need a special permission?
Yes. Comment events require the Notion integration's Read comments capability. If enabled after authorization, reauthorize the connection.
Can comments trigger this anywhere?
The supplied event can fire for comments throughout the workspace the integration can access, subject to its configured trigger scope.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Apify. A trigger fires from one place; an action lands in another.
Notion triggers
Apify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Actor Task
Tool to create a new actor task with specified settings. use when you need to configure or schedule recurring actor runs programmatically.
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.
Create Task Webhook
Tool to create a webhook for an actor task. use when you need external notifications about task run events (e.g., completion or failure) in downstream systems.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
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.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook 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.
Get Actor Details
Tool to get details of a specific actor. use when you need actor metadata by id or username/actorname.
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.
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Connect any two apps with Notis in the middle.
Notion and Apify, 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 Apify.