[Slack] app_mention events silently dropped by silo — @Plane AI does not respond in Slack
@henit-chobisa is already working on this.
Since Jul 1, 2026.
- Dominant language
- TypeScript
- Stars
- 59.6k
- Forks
- 5.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 49
Description
Summary
When a user mentions @Plane in a Slack channel, the app_mention event is delivered to /silo/api/slack/events and silo logs that it received the payload — but silo never dispatches the event internally, so Plane AI never produces a reply.
Environment
- Self-hosted Plane with
makeplane/silo-commercialimage - GovSlack (Slack for Government) — Socket Mode integration
- A lightweight Socket Mode adapter forwards all payloads to silo over HTTP, re-signing requests with
SLACK_SIGNING_SECRET
Steps to reproduce
- Configure the Slack app with the
app_mentionbot event subscription. - Mention
@Planein any channel where the bot is present. - Observe silo logs.
Expected behavior
Silo dispatches the app_mention event to its internal handler and Plane AI replies in the Slack thread.
Actual behavior
Silo logs [SLACK_EVENTS] Received payload for the app_mention event but never emits the subsequent [SLACK][EVENT] Received webhook event from slack 🐱 --------- [slack-interaction] log line that appears for other event types.
Other event types (link_shared, message.channels, message.im) are received and dispatched correctly.
app_mention events appear to be silently dropped after receipt — no error is logged.
Silo log comparison
link_shared (working):
[SLACK_EVENTS] Received payload
[SLACK][EVENT] Received webhook event from slack 🐱 --------- [slack-interaction]
app_mention (not working):
[SLACK_EVENTS] Received payload
(nothing further)
Questions
- Does silo's
/silo/api/slack/eventsendpoint handleapp_mentionevents, or does the Plane AI / @Plane mention feature require a different endpoint? - Is there additional configuration (environment variables, feature flags, AI provider API keys) required to enable the @Plane AI Slack feature?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.