DevCom.AgenticRuntime.Plugin.Slack 1.0.1

DAP Slack Plugin

Trigger a DevCom Agentic Platform (DAP) agent by @mentioning a Slack bot in a channel, and get the agent's reply back in the same channel — threaded under the message that mentioned it.

Unlike the Telegram plugin (which long-polls), Slack pushes events to DAP over HTTPS via the Events API, so the plugin exposes a single public endpoint and does no polling.

Features

• slack-mention trigger — pairs a Slack app to an agent; an app_mention fires the agent with the message text (mention stripped) plus Slack context (channel, user, thread).
• Threaded, streamed replies — the agent's answer is posted back and edited in place as it streams, threaded under the triggering message by default (chat.update, debounced to respect Slack's ~1 msg/sec/channel limit).
• Session continuity — follow-up @mentions in the same thread continue the same agent conversation (session keyed by channel + thread).
• Per-agent pairing / multi-tenant — bot token, signing secret, and channel allow-list live on the per-agent trigger config, so one DAP deployment can pair multiple agents to multiple Slack apps/workspaces, each routed independently.
• Request authenticity — every inbound event is verified (X-Slack-Signature HMAC-SHA256 + X-Slack-Request-Timestamp ±5-minute replay window); unverifiable requests get 401 and fire nothing. Redeliveries are de-duplicated by event_id.

Configuration

The plugin has no plugin-wide settings. Configure each agent's Slack trigger with:

Slack app setup

1. Create an app at https://api.slack.com/apps → Create New App → From scratch.

2. Add scopes — OAuth & Permissions → Bot Token Scopes: add app_mentions:read and chat:write.

3. Install to workspace — Install App → copy the Bot User OAuth Token (xoxb-…).

4. Copy the Signing Secret — Basic Information → App Credentials → Signing Secret.

5. Create the DAP credential — in DAP, create a slack-mention credential with the bot token and signing secret, and click Test (runs auth.test) to confirm it connects.

6. Enable Event Subscriptions — Event Subscriptions → toggle on → Request URL:

   https://<your-dap-host>/api/x/DevCom.AgenticRuntime.Plugin.Slack/events
   

   Slack sends a one-time url_verification challenge; the endpoint answers it, so the URL shows Verified. The URL must be publicly reachable and registered per environment.

7. Subscribe to the event — Subscribe to bot events → add app_mention → Save Changes (reinstall the app if Slack prompts you to).

8. Bind the agent — add a slack-mention trigger to the agent, referencing the credential and (optionally) an allowed-channels list. Invite the bot to the channel (/invite @yourbot) and @mention it.

Out of scope (v1)

Slash commands, interactive components (buttons/modals), Socket Mode, direct messages, non-mention channel listening, file/attachment ingestion, and HITL notify/resolve over Slack — see the follow-up tickets.

Changelog

1.0.1

• fix(DAP-251, slack): resolve a plugin-install failure — SlackEventProcessor (a bootstrapper singleton) can't have ITriggerContext constructor-injected because the plugin's inner DI container doesn't resolve it; it is now passed per-dispatch from the events endpoint.

1.0.0

• feat(DAP-251, slack): slack-mention trigger via the Slack Events API — signed app_mention events fire the bound agent and stream a threaded reply back into the channel; per-config credentials (bot token + signing secret), channel allow-list, thread session continuity, and event_id dedupe.