Pull a Cursor agent conversation from an incoming webhook
When a pipeline finishes and you want to know what the agent did, a webhook is the fastest trigger. Notis takes the call and delivers the Cursor conversation to you.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Your CI or deploy tooling knows exactly when to check an agent, but you still open Cursor by hand to read the conversation after each run.
- Agent conversation arrives right after a run
- Any tool can trigger the pull, not just Notion
- No manual Cursor visit to read the thread
- Fits CI, deploy, and custom pipelines
Setup
Build it in a few focused steps.
- 1Connect Cursor to Notis once in the portal.
- 2Ask Notis for your portal link, open Automations, then New Automation.
- 3Write the instruction: 'When my webhook is called with an agent reference, get that Cursor agent's conversation and send it to me.'
- 4Pick the incoming webhook as the trigger and set the report channel.
- 5Send one test request and confirm the conversation returns.
Questions about this workflow
How does Notis know which agent to fetch?
Include the agent reference in your webhook payload and describe it in your instruction. Notis uses it for the Get Agent Conversation call.
What if the agent is not found?
The action returns a not-found result and Notis reports it to your channel so you know the reference was wrong.
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.