Configure Slack

Construct can post snapshots and roadmap summaries to Slack channels. Monitoring itself is poll-based, not webhook-driven — see ADR-0061 amendment for the architectural stance and why the slash-command endpoint below is not yet live.

Step 1: Create a Slack app

1. Go to api.slack.com/apps and click Create New App.
2. Choose From scratch.
3. Name the app (e.g. Construct) and pick your workspace.

Step 2: Add scopes

Under OAuth & Permissions → Scopes → Bot Token Scopes, add:

• channels:history
• channels:read
• chat:write
• commands

Step 3: Slash commands (not yet available)

The Slack app configuration flow allows registering a Slash Commands endpoint, but Construct does not yet run an inbound HTTP receiver for it — there is no server behind /webhooks/slack in this codebase today. Skip this step until inbound webhook receiving lands; see the ADR-0061 amendment linked above for what would justify building one.

Step 4: Install to workspace

Under OAuth & Permissions, click Install to Workspace. Copy the Bot User OAuth Token (starts with xoxb-).

Step 5: Get the signing secret

Under Basic Information → App Credentials, copy the Signing Secret.

Step 6: Add to config.env

# ~/.config/construct/config.env
SLACK_BOT_TOKEN=xoxb-your-token-here
SLACK_SIGNING_SECRET=your-signing-secret-here
SLACK_CHANNELS=#general,#incidents:risk,#decisions:decision

Channel intent format

The SLACK_CHANNELS value supports optional intent suffixes. The intent tells Construct how to categorize messages from each channel:

#channel-name:intent

Valid intents: risk, decision, insight, external, internal

Examples:

# Single channel, no intent (defaults to insight)
SLACK_CHANNELS=#eng-updates

# Multiple channels with intents
SLACK_CHANNELS=#general,#incidents:risk,#team-decisions:decision,#customer-feedback:external

Step 7: Restart the daemon

construct embed stop
construct embed start

Authority and approval

Slack posts are classified as externalPost actions, which are approval-queued in the default operating profile. This means the daemon will queue the post and wait for your approval before sending.

To allow autonomous posting, update the authority in your embed config:

# In your embed config (or override in config.env)
operatingProfile:
  authority:
    externalPost: autonomous

You can also approve queued posts from the dashboard under the Approvals tab.