Skip to content

Slack monitor automation should support the botname as a trigger by default #431

Description

@DevinVinson

Creating a slackbot when everything goes right looks like this:

Image Image

But when I tried it out on a first run I didn't see any response. I asked the agent to figure out why:

I found the issue.

The automation is successfully polling the channel and reading your messages, but it is matching the literal text @openhands. Slack stores an app mention in message text as its user-ID form instead:

<@U0B6US8S0DP> Are you awake?

The debug log shows these messages reached the evaluator, but were rejected:

trigger=False
text='<@U0B6US8S0DP> Are you awake?'

So no conversation is created because the current matcher only looks for the configured literal @openhands; it does not recognize Slack’s mention token <@U0B6US8S0DP>.

The automation itself is healthy: runs are completing, Slack authentication succeeds, state is persisting in KV storage, and channel polling is working.

I can update and redeploy it to treat both @openhands and the Slack mention token as the same trigger, preserving the intended user-facing trigger phrase.


This could asking the user for the bot name or asking them to test the connection to find out the name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions