List Cursor agents when a Notion data source is created
Adding a data source usually means a new stream of work is starting. Notis catches the event and lists your Cursor cloud agents so the new structure begins with full context.
Trigger
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.
Action
List Agents
Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents with pagination.
Why this helps
New data sources appear as your workspace grows, but you have no quick sense of the agent activity around them, so context gets lost early.
- New structures start with build context in view
- No manual agent check as the workspace grows
- Catch relevant activity from the very start
- Keeps expanding workspaces coherent
Setup
Build it in a few focused steps.
- 1Connect Notion and Cursor to Notis once from the portal.
- 2Write the instruction: 'When a new Notion data source is created, list my Cursor cloud agents and send them to me.'
- 3Select the Notion Data Source Created trigger and set the report channel.
- 4Create a test data source and confirm the agent list arrives.
Questions about this workflow
How is this different from the database created trigger?
A data source is added inside a database container. This trigger fires per data source, which can be multiple at once for template-based creation.
Can I filter by teamspace?
Describe the teamspace in your instruction and Notis uses the payload parent to scope the run downstream.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Cursor. A trigger fires from one place; an action lands in another.
Notion triggers
Cursor actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Agent Conversation
Tool to retrieve the conversation history for a specific cloud agent. Use when you need to view the messages exchanged between the user and the agent. Returns error with status 404 if the agent is not found or access is denied.
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 API Key Info
Tool to retrieve API key information including the key name, creation date, and owner email. Use when you need to verify API key details or validate authentication.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
List Agents
Tool to retrieve a paginated list of all Cursor Cloud agents. Use when you need to view existing agents, their status, or iterate through agents 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 Available Models
Tool to retrieve the list of available AI models in Cursor. Use when you need to discover which models are available for API requests.
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 GitHub Repositories
Tool to list GitHub repositories accessible to the authenticated user. Use when you need to retrieve all repositories the user has access to through their Cursor account.
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.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Cursor. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Cursor.