Bring Cursor activity into Coherence
Start from a supported Cursor event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Agent
Finishes with
Create or update a Coherence record

AI-powered code editor with cloud agents that can work on your repositories. Launch agents, monitor their status, and automate code-related tasks.
Cursor currently provides 5 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New Agent
Triggers when a new Cursor agent is created or when agent status changes
Agent Status Equals
Triggers when a Cursor agent has the specified status (e.g., "FINISHED", "FAILED")
Agent Pull Request Created
Triggers when a background agent creates a pull request
New Agent Conversation Message
Triggers when a new message appears in a specific agent's conversation
Agent Status Changed (Webhook)
Triggers when an agent status changes (ERROR or FINISHED). Configure this webhook URL when launching an agent.
Launch Agent
Start a new cloud agent to work on your repository
Add Followup Instruction to Agent
Adds follow-up instructions to a running cloud agent
Find Agent Status
Retrieve the current status and results of a cloud agent
Delete Agent
Delete a cloud agent. This action is permanent and cannot be undone.
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Cursor event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Agent
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Cursor action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Launch Agent
Combine Cursor with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Agent
Finishes with
Launch Agent, then preserve the outcome in Coherence
The exact authentication fields depend on Cursor. The workflow structure stays straightforward:
Authorize the Cursor account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Cursor or provide a complementary trigger or action.
Cursor currently provides 5 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
Cursor currently lists 5 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Cursor triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.