Production OAuth URLs
For the hosted Corgtex app, configure these URLs in Slack App Management:| Slack setting | URL |
|---|---|
| OAuth Redirect URL | https://app.corgtex.com/api/integrations/slack/callback |
| Slash command request URL | https://app.corgtex.com/api/integrations/slack/commands |
| Events request URL | https://app.corgtex.com/api/integrations/slack/events |
| Interactivity request URL | https://app.corgtex.com/api/integrations/slack/interactivity |
SLACK_CLIENT_ID.
Deployment Checks
Before testing an install, verify in the deployment platform that the runtime hasAPP_URL=https://app.corgtex.com and has non-empty values for SLACK_CLIENT_ID, SLACK_CLIENT_SECRET, SLACK_APP_ID, SLACK_SIGNING_SECRET, and ENCRYPTION_KEY. Do not print or paste secret values into logs, tickets, PRs, or chat.
The Slack Client ID in production must match the Slack app where the redirect URL and request URLs were configured. A common failure mode is updating a development Slack app while production still points at a different Client ID.
Install Flow
Start the install from Corgtex workspace settings with Connect Slack. Do not start from Slack App Management directly, because Corgtex generates a short-lived workspace-bound OAuth state cookie before sending the browser to Slack. After installation, verify the workspace settings page shows Slack as connected, then test/corgtex Jan should follow up tomorrow, /corgtex brief, an app mention such as @Corgtex turn this into a tension, and a message shortcut capture in Slack. Direct messages are not part of the v1 Slack surface, so do not add DM scopes or DM event subscriptions for this setup.
For hosted workspaces that use Slack as long-term context, include channels:history and channels:join in the bot scopes, and subscribe the bot to message.channels events in addition to app_mention and app_home_opened. Corgtex uses those scopes and events to join public channels, capture accessible public-channel messages, index those messages into Brain retrieval, and maintain thread/channel summaries for the Slack agent. Private channels and DMs remain out of scope.
The worker schedules communication.slack.public-archive daily for active Slack installations with channels:history. For first-time customer onboarding or a recovery import, run node /app/scripts/sync-slack-public-archive.mjs inside the customer runtime with WORKSPACE_SLUG or WORKSPACE_ID set. The command reports counts only and must not print Slack message content, channel names, or token values.
Raw Slack message text is retained according to the installation retention setting and is redacted by the communication retention worker when it expires. When raw text is redacted or a Slack delete event arrives, Corgtex removes the corresponding raw Slack knowledge chunks. Durable context summaries may remain as derived organizational memory unless the workspace disables Slack ingestion or asks for a broader deletion.
Slack’s Real-time Search API can be considered for future private-channel or DM context, but do not store data returned by that API in Corgtex. Use it only as ephemeral request-time context with the required Slack user consent and permission checks.