Cursor automations with github PR merge event is not triggering

Support Help
,
1

Hi team,

I’ve created a cursor automation with trigger of github PR merge

I’ve installed cursor github-app, I’ve merged 2,5 PR to staging branch but automation haven’t triggered.

My repository has main default branch, does cursor automations only work on repository default branch?

5

The cursor automation ran once PR merged to main branch (which was the default branch of repository), but automation haven’t ran on merging PR’s to non default repository branch

6

Hey, thanks for the report.

To answer the main question first, no, automations aren’t limited to the default branch. The Pull request merged trigger fires for a merge into any branch in the selected repository, so merging into staging should work the same as main.

When a merge doesn’t start a run, the most common reason is that the merge event couldn’t be linked to the Cursor account that owns the automation. Here’s a quick checklist:

  1. Open cursor.com/dashboard > Automations, open your automation, and check Run history. Is it empty, or do you see failed runs? If there are failures, what’s the error message?
  2. In the trigger settings, confirm the event is exactly Pull request merged, and the repository selected is the one you merged into.
  3. On GitHub, open the account or org that owns the repo. Go to Settings > Applications. For orgs, go to Third-party Access > GitHub Apps. Click Configure next to Cursor and make sure the repo is included under Repository access. If it’s set to Only select repositories, the repo must be in the list.
  4. On cursor.com/dashboard, open Integrations and confirm GitHub is connected, and that the GitHub user who merged the PR is the same one linked to this Cursor account. If a teammate merged it, a bot merged it, or GitHub auto-merge did it, that’s the most likely reason nothing ran.
  5. Go back to the automation and click Run Test to confirm a test run starts. This checks the automation itself.
  6. Then merge a small PR into staging yourself, and check Run history a couple minutes later.

One more thing. automations run on Cloud Agents, which aren’t available on Free and Pro Trial. If the account that owns the automation is on Free, a matching merge should show up as a failed run, not as silence. So an empty Run history still points to the items above.

If it still doesn’t fire after step 6, send this info: the email for the Cursor account where the automation was created, the automation link, the repo owner/repo, who merged the PR, and the approximate time of the last merge with timezone. With that, we can check what happened to those events.