Can Gotify and Cursor talk in both directions?

Yes. Build one flow that starts in Gotify and acts in Cursor, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect Gotify to Cursor

Move data between Gotify and Cursor the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore Gotify Explore Cursor

Gotify triggers: 0
Gotify actions: 1
Cursor triggers: 5
Cursor actions: 4

Automation ideas

What you can build with Gotify and Cursor

A few flows teams run between Gotify and Cursor. Use one as a starting point, or build your own from scratch.

New Agent in Cursor creates Send Notification in Gotify
Triggers when a new Cursor agent is created or when agent status changes
Agent Status Equals in Cursor creates Send Notification in Gotify
Triggers when a Cursor agent has the specified status (e.g., "FINISHED", "FAILED")
Agent Pull Request Created in Cursor creates Send Notification in Gotify
Triggers when a background agent creates a pull request