PR Label Automation Not Triggering When Added by Other Team Members

[Yash_Choudhary]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I created an automation that triggers based on a PR label. It seems to be working correctly when I add the label myself, but it doesn’t appear to trigger when other members of the team add the same label. Has anyone run into this before, or is there some

Steps to Reproduce

Sharing the json for the automation (removed prompt and repo link)

{
“name”: “Code Insight",
“triggers”: [
{
“git”: {
“label”: {
“repos”: [
"github link”
],
“labelName”: “ai-code-review”,
“onAdded”: true,
“onRemoved”: false,
“pullRequests”: true,
“issues”: false
}
}
}
],
“actions”: [
{
“prComment”: {
“allowApprove”: true
}
}
],
“prompts”: [
{
“prompt”: “Full-prompt”
}
],
“model”: “claude-opus-4-8-thinking-high”,
“memoryEnabled”: true,
“scope”: “private”,
“gitConfig”: {
“repo”: “github-link”,
“repos”: [
“github-link”
],
“branch”: “development”
}
}

Operating System

MacOS

Version Information

Cursor Web

Does this stop you from using Cursor

No - Cursor works, but with this issue

[kevinn (Kevin Neilson)]

Hi @Yash_Choudhary Thanks for the forum post, and thank you for sharing the config, that’s the key detail here.

The cause is that your automation is set to “Private” (scope: private). A label automation only runs for people who can access it, and a private automation is owned by you alone, so it only fires when you add the label. When a teammate adds it, nothing matches your private automation.

To fix it:

1. Change the automation’s sharing from “Private” to “Members can view”. This keeps it running as you, but lets it trigger when any teammate adds the label.

2. Make sure each teammate who adds the label has connected their GitHub account in Settings > Integrations, so their action can be matched to the automation.

One heads-up: switching an existing automation from Private to a team scope doesn’t always save the team association correctly right now. If teammates still don’t see it trigger after the change, recreate the automation with “Members can view” selected from the start.

If it still doesn’t fire, send me the automation ID, the repo, a teammate’s GitHub username, and a rough timestamp, and I’ll take a closer look!