Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Cursor

AI-powered code editor with cloud agents that can work on your repositories. Launch agents, monitor their status, and automate code-related tasks.

CategoryDeveloper Tools
Authenticationcustom
Version0.1.7
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Cursor with Flows360

AI-powered code editor with cloud agents that can work on your repositories. Launch agents, monitor their status, and automate code-related tasks.

Use the Cursor connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 5 triggers.

Available actions

  • Launch Agent
  • Add Followup Instruction to Agent
  • Find Agent Status
  • Delete Agent

Available triggers

  • New Agent
  • Agent Status Equals
  • Agent Pull Request Created
  • New Agent Conversation Message
  • Agent Status Changed (Webhook)

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Cursor
  • Package: @activepieces/piece-cursor@0.1.7
  • Exact artifact digest: sha256:daa900dcea1c55711e4df6b8dc18dc39f796e46cf7a65cdbf3b105dfce7649ee
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Launch Agent (launch_agent), Start a new cloud agent to work on your repository Classification: read.
  • Add Followup Instruction to Agent (add_followup_instruction), Adds follow-up instructions to a running cloud agent Classification: read.
  • Find Agent Status (find_agent_status), Retrieve the current status and results of a cloud agent Classification: read.
  • Delete Agent (delete_agent), Delete a cloud agent. This action is permanent and cannot be undone. Classification: read.

Trigger contracts

  • New Agent, polling.
  • Agent Status Equals, polling.
  • Agent Pull Request Created, polling.
  • New Agent Conversation Message, polling.
  • Agent Status Changed (Webhook), webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Launch Agent Yes No Start a new cloud agent to work on your repository
Add Followup Instruction to Agent Yes No Adds follow-up instructions to a running cloud agent
Find Agent Status Yes No Retrieve the current status and results of a cloud agent
Delete Agent Yes No Delete a cloud agent. This action is permanent and cannot be undone.
New Agent Yes No polling trigger declared by the pinned package.
Agent Status Equals Yes No polling trigger declared by the pinned package.
Agent Pull Request Created Yes No polling trigger declared by the pinned package.
New Agent Conversation Message Yes No polling trigger declared by the pinned package.
Agent Status Changed (Webhook) Yes No webhook trigger declared by the pinned package.

Supported actions

Launch Agent · Read

Start a new cloud agent to work on your repository

launch_agent · Risk: low · Retry: safe

Inputs

  • promptText · string · Required, The instruction text for the agent
  • images · array · Optional, Optional images to include with the prompt (max 5)
  • model · string · Optional, The LLM to use (e.g., claude-4-sonnet). Leave empty to use the default model.
  • repository · string · Required, GitHub repository URL (e.g., https://github.com/your-org/your-repo)
  • ref · string · Optional, Git ref (branch name, tag, or commit hash) to use as the base branch
  • autoCreatePr · boolean · Optional, Automatically create a pull request when the agent completes
  • openAsCursorGithubApp · boolean · Optional, Open the pull request as the Cursor GitHub App instead of as the user. Only applies if auto-create PR is enabled.
  • skipReviewerRequest · boolean · Optional, Skip adding the user as a reviewer to the pull request. Only applies if auto-create PR is enabled and opened as Cursor GitHub App.
  • branchName · string · Optional, Custom branch name for the agent to create
  • webhookUrl · string · Optional, URL to receive webhook notifications about agent status changes
  • webhookSecret · string · Optional, Secret key for webhook payload verification (minimum 32 characters)
Add Followup Instruction to Agent · Read

Adds follow-up instructions to a running cloud agent

add_followup_instruction · Risk: low · Retry: safe

Inputs

  • agentId · string · Required, Select a cloud agent
  • text · string · Required, The follow-up instruction text for the agent
  • images · array · Optional, Optional images to include with the instruction (max 5)
Find Agent Status · Read

Retrieve the current status and results of a cloud agent

find_agent_status · Risk: low · Retry: safe

Inputs

  • agentId · string · Required, Select a cloud agent
Delete Agent · Read

Delete a cloud agent. This action is permanent and cannot be undone.

delete_agent · Risk: low · Retry: safe

Inputs

  • agentId · string · Required, Select a cloud agent

Setup

Setup

  1. Add the Cursor connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-cursor@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Cursor connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-cursor@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com