I have an automation that hooked up to every new message in a slack channel but it only runs when I send a message, no one else. It does not even start the run for other people when they copy paste my message, and i have no criteria for sending, just any message. Also to clarify the screenshots show 1 run, i added and removed the bot many times to try to get it to work. Probably 15-20 tests.
The automation ID is 8b0239ed-f96f-4617-b1d8-e934a8d2c7b4.
Steps to Reproduce
Create slack automation listening for all messages
Our team found out that the user in slack needs to 1) have a cursor account and 2) have that cursor account linked to slack for the automation to work. Obviously it says “every new message” so we were not aware of that. The channel was public.
It would be great if this would work for any user!
Following up on Josh’s finding — it seems automations only trigger on messages from Slack users who have a Cursor account linked to Slack. This also means:
1. Messages from team members without Cursor accounts don’t trigger automations
2. Messages posted by bots/apps (e.g. from a previous automation using “Send to Slack”) also don’t trigger
For our use case, we have a two-stage automation: Automation 1 triages a bug and posts [fix-ready] to Slack, which should trigger Automation 2 to fix it. But since the [fix-ready] message comes from the automation (not a linked user), the second automation never fires.
Is the “linked Cursor account” requirement intended behavior, or is this part of the bug you’re investigating? Any timeline on a fix?
Since the original report, we added a “from” option in the Slack trigger settings with two choices:
“Anyone in the channel” (default): the automation triggers on messages from any user in the channel, no Cursor account linking needed
“Authenticated Cursor users”: it only triggers for users who have linked a Cursor account
@Josh_Andrews, @Andrew_Bianchi: please check that your trigger is set to “Anyone in the channel”, then test again. This should fix it for regular users without Cursor accounts.
@Mateusz_Kwasny: about the automation chain where Automation 1 posts to Slack and that should trigger Automation 2, that is a separate limitation. Messages from bots or apps might not be recognized as normal channel messages. I shared this with the team. There is no exact timeline yet, but your report helps us prioritize it.
One important note: if users are using @Cursor mentions instead of a normal message, that is a different mechanism and it does require account linking. Automations trigger on normal messages, not on mentions.
Let me know if changing the “from” setting helped.
