Ask Cursor about a ticket. Its answer arrives as an internal note.
Explore 4 workflow actions for Cursor, including account permissions and operation limits.
3 read actions1 write action
WORKFLOW ACTIONS
What you can configure.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Ask Cursor about the ticket
Write
Ask a Cursor cloud agent about the run's ticket and a GitHub repository, within what the Cursor account allows. Its answer arrives later as an internal note on the ticket.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
Operation limits
Starts a Cursor run on the ticket; its answer arrives later as an internal note, which a Wait on thread.note_created can follow.
Within what the Cursor account allows, and at most three questions of a brand with Cursor at once.
A lost answer leaves the step uncertain: NodeHub checks with Cursor by reading and never starts a second agent.
A repeated request may repeat the external action. Review the previous result before retrying a write.
List repositories
Read
List the GitHub repositories Cursor can read through its GitHub app.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
Operation limits
Cursor allows 1 call a minute and 30 an hour per user, and the list can take tens of seconds; NodeHub keeps it for an hour.
Read cloud agent
Read
Read a Cursor agent: its status, address and latest run.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
Read cloud agent run
Read
Read a Cursor run: its status, its final reply and the branches it pushed.
Permissions and limits
Account permissions
Depends on the connected account and selected operation. Check the service documentation.
SETUP
Start with a controlled test.
01Connect the intended account
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
02Review inputs and access
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
03Confirm the result
Inspect step outputs and confirm the result in Cursor. A saved workflow is not a completed provider action.
