Running in DJINNCommand room
DJINN + Slack
Slack is where DJINN lives. Requests arrive as messages, work comes back as digests, and every scheduled job reports into a channel.
Live in our own instance today — ask to see it work.
How it connects
Socket Mode, not webhooks
A long-lived process holds a Socket Mode connection, so there is no public inbound endpoint and no tunnel to maintain. Reconnects are expected and filtered out of incident detection as normal noise.
Threads carry the context
A thread is the unit of work. DJINN reads it, resolves what it needs from company memory, and replies in place — so the request and its answer stay attached.
Digests post on a schedule
Separate channels for separate rhythms: a daily industry digest, a weekday engineering digest, a twice-weekly lead digest. A quiet week in one never buries a loud week in another.
Outbound stays human-gated
Scheduled digests write to channels configured up front. Posting anywhere else is proposed and waits for a person — enforced at the tool layer, not by asking the agent to remember.
Worth knowing before you wire it
Slack read methods ignore a JSON body and silently fall back to defaults. Every call is form-encoded — a JSON body once hid a private channel from discovery behind nothing more than a `missing_charset` warning.
Documents
Slack setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupSocket Mode setup and scopes
- ReferenceChannel routing and digest configuration
- PolicyHuman-approval boundaries for outbound
Want Slack wired into your own company brain?