Automation not triggering when Slack workflow creates Linear ticket

[Rohit_Sudhir]

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hi,

I have an automation set up to monitor Linear for created tickets in a specific team space. However, right now it is not triggering when a Slack workflow creates a ticket, but does trigger when I create a ticket manually. This leads me to believe that the issue is something to do with tickets created by other bots (Slack in my case).

Steps to Reproduce

1. Create a new automation and connect Linear and Github MCP
2. Trigger the automation when an issue is created in Linear
3. Observe difference in behavior when user creates a ticket in Linear vs when a Slack workflow or other bot creates a ticket in Linear

Expected Behavior

I’m expecting that any ticket created, regardless of owner/source should trigger this automation

Operating System

MacOS

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, this is a known limitation right now. Automations require the ticket creator in Linear to have an authorized connection to Cursor. When a ticket is created by a Slack workflow or any other bot, the system can’t match it to a Cursor user, so the trigger is silently skipped.

The same issue was discussed here: Linear Integration not working with new Automations Feature. A few users ran into the same situation.

For now, the only workaround is to create or duplicate the ticket manually as a user who has an authorized Cursor connection. Not ideal, I know.

The team is aware of this limitation.

Let me know if you have any questions.