For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/integrations/slack.md.
Docs

Slack

Slack connects Flezise to your workspace so the builder agent can receive tasks as @mentions, post replies in the thread where the work arrived, and deliver approval and escalation alerts to a channel you choose.

The Slack integration detail page: Connect and Connect with token buttons, an Inbound events card with the Allow work-item triggers toggle, and a Write-back card with Auto-respond and Approval notifications toggles

Connect

Go to Project Settings → Integrations → Slack. If OAuth is available on your deployment, press Connect to open the authorization popup. The app requests these scopes:

ScopePurpose
app_mentions:readReceive events when the bot is @mentioned
chat:writePost reply messages
channels:readList channels for the notification target picker
channels:historyRead channel message history

Scopes are comma-separated in the Slack OAuth request. After authorization, the platform calls the Slack API to record the bot token and the workspace team_id (the post-exchange step). Subsequent events from that workspace are routed to this project using the stored team_id, so one set of credentials covers the whole workspace.

If OAuth is not available on your deployment, press Connect with token and supply the credentials directly:

FieldValue
Bot TokenBot user OAuth token from your Slack app, starting xoxb-
Signing SecretFrom Basic Information in the Slack API console

Set up event delivery

The platform generates a webhook URL once the connection is saved. Use that URL as your Slack app Event Subscriptions Request URL. Complete these steps in order:

  1. Open your Slack app at api.slack.com/apps.
  2. Go to Basic Information and copy the Signing Secret into this connection.
  3. Go to OAuth & Permissions and copy the Bot User OAuth Token into this connection.
  4. Save this connection, then copy the generated webhook URL from the saved-connection panel.
  5. Go to Event Subscriptions, turn events on, and paste the webhook URL as the Request URL.
  6. Under Subscribe to bot events, add app_mention and message.channels. Reinstall the app if Slack asks, then @mention the bot in a channel to confirm delivery.

Capabilities

CapabilityWhat Flezise does
WebhooksReceives and verifies events using HMAC-SHA256 over the x-slack-signature header
ReplyPosts replies in the thread where the @mention or message arrived

Configuration

The Write-back card on the integration detail page controls what the builder agent sends back to Slack after each event.

Auto-respond to tickets is on by default. The builder agent replies to the mention and posts the pull-request link back in the same thread once work is done. Each reply runs an AI research pass and uses credits.

Approval and escalation notifications is off by default. Enable it and a Notification target (channel/conversation ID) field appears. Enter the Slack channel ID (for example C01ABCDEF) where the platform should post pending-approval and escalation messages.

The Inbound events card carries an Allow work-item triggers toggle. When it is on, events from Slack can create work items on the project board, subject to the project automation policy.

Events

EventWhen it fires
app_mentionThe bot is @mentioned in any channel or thread
messageA message is posted in a channel the bot belongs to

Both events pass through the event classifier. The classifier extracts intent and, if the automation policy allows it and Allow work-item triggers is on, creates a work item and starts agent triage.

Next steps