Docs/Integrations/Integrations

    Slack

    Last updated · MAR 2026·Read as Markdown

    Slack Integration

    Drop your AVCodex agent into the channels where the work already happens. The programmer team channel asking about a Crestron error. The bid team coordinating an RFP response. The ops manager paging dispatch about a downed conference room.

    Deploy your AVCodex agent to Slack so team members can interact with it directly in Slack channels and direct messages. No tab switching, no logins. Ask in the channel, get an answer in a thread.

    Once connected, your agent becomes a Slack bot that:

    • Responds to mentions: @AVCodex what's the SIMPL# syntax for a multi-array string parser?
    • Uses threads: Replies in threads to keep #av-programming clean
    • Maintains context: Remembers conversation history within each thread
    • Works everywhere: Public channels, private channels, and DMs
    Feature Description
    Threaded Conversations Every response goes in a thread, keeping channels clean
    Multi-user Support A programmer, an estimator, and a PM can all weigh in on the same thread
    Context Retention Your agent remembers what was discussed earlier in each thread
    Direct Messages Chat privately with the bot in DMs

    The Slack integration requires creating your own Slack app. AVCodex provides a pre-configured manifest to make this easy.

    1. Open Slack Configuration in AVCodex

    Go to your AVCodex agent and click Share in the navigation. Select the Deploy tab and find the Deploy to Slack card. Click Add Deployment.

    2. Create a Slack App

    1. Go to api.slack.com/apps in a new tab 2. Click Create New App 3. Select From manifest 4. Choose your Slack workspace

    3. Copy the Manifest from AVCodex

    In the AVCodex dialog, you'll see a JSON manifest section. Click Copy to copy the entire manifest to your clipboard.

    This manifest is pre-configured with: - Your agent's name and branding - Required bot permissions - Event subscriptions - Webhook URLs pointing to AVCodex

    4. Paste and Create the App

    1. In Slack's app creation flow, select JSON format 2. Delete any existing content and paste your copied manifest 3. Click Next, then Create

    5. Get Your App Credentials

    After creating the app, go to Basic Information under Settings in the left sidebar. You'll need three values:

    - Client ID: Found in "App Credentials" section - Client Secret: Click "Show" to reveal it - Signing Secret: Found below the Client Secret

    6. Enter Credentials in AVCodex

    Back in the AVCodex dialog, enter all three credentials:

    - Client ID: The app's Client ID - Client Secret: The app's Client Secret - Signing Secret: The app's Signing Secret

    Click Save Configuration.

    7. Install to Slack

    After saving credentials, click Install to Slack. You'll be redirected to authorize the bot in your workspace.

    > Warning: Only Slack workspace admins can install apps. If you're not an admin, ask your Slack administrator to complete the installation.

    8. Invite to Channels

    After installation, invite the bot to channels where you want to use it:

    `` /invite @YourBotName ``

    Replace YourBotName with your AVCodex agent's name. Common channels: #av-programming, #bid-team, #dispatch, #field-ops.

    Basic Usage#

    Mention the bot followed by your question:

    code
    @AVCodex what's the default subnet mask we use for Crestron control networks?

    The bot replies in a thread so the main channel stays clean.

    Following Up#

    Continue the conversation in the same thread, the bot remembers context:

    code
    @AVCodex our Q-SYS Core 510i is throwing a "design did not load" error after firmware update
└── Bot: Most common cause is a Lua module compiled against a newer Designer version. Check the design's required version in...
    └── You: where do I see that in Designer?
        └── Bot: File > Design Properties > Required Version. If your Core firmware is older...

    Multiple Users#

    Team members can jump into threads. The bot considers all messages:

    code
    @AVCodex draft an RFP response section about our Crestron NVX redundancy approach
└── Bot: Here's a draft section...
    └── Alice (BD): make it more aligned to higher-ed verticals
    └── Bob (Engineering): and reference our two-Core failover topology
        └── Bot: Here's the revised version incorporating both points...

    Direct Messages#

    DM the bot for private conversations:

    1. Find the bot in your Apps or search for it
    2. Send a direct message
    3. No need to @mention in DMs

    Channel Organization#

    • Create dedicated channels for AI assistance (#ask-avcodex, #programming-help, #commissioning-q-and-a)
    • Use private channels for client-sensitive deal info or commercial topics
    • Set channel topics explaining what the bot can help with

    Prompt Engineering for Slack#

    Optimize your system prompt for team use:

    code
    You are an AVCodex assistant for the Acme AV team in Slack.

When responding:
- Keep answers concise (Slack conversations should be quick)
- Use bullet points for lists of error codes or pin assignments
- If a tech is troubleshooting, ask which room and which manufacturer
- For sensitive client-deal info, suggest moving to a private channel
- When citing a manufacturer doc, link the page section

    Thread Management#

    • One topic per thread: Start a new message for different questions
    • Don't resurrect old threads: Context has limits, start fresh for new topics
    • Use reactions: Thumbs up or check to mark a fix that worked, useful for the dispatch log

    Editing Credentials#

    If you need to update your Slack app credentials:

    1. Go to Share > Deploy > Deploy to Slack
    2. Click Manage Deployment
    3. Click Edit Credentials
    4. Enter the new values and save

    Reinstalling#

    If you need to reinstall to a different workspace or fix permission issues:

    1. Open the Slack deployment dialog
    2. Click Install to Slack
    3. Select the workspace and authorize

    Bot Not Responding#

    1. Make sure the bot is invited to the channel (/invite @YourBotName)
    2. Check that you're @mentioning the bot correctly
    3. Verify your AVCodex agent is active and published

    "I don't have permission" Error#

    The bot needs to be installed by a workspace admin. Contact your Slack administrator to install the app.

    Bot Responding Slowly#

    1. Check your AI model, faster models respond quicker
    2. Complex queries with custom actions take longer (e.g., scanning a folder of Biamp Tesira files)
    3. High workspace usage can cause brief delays

    Installation Failed#

    1. Verify all three credentials are entered correctly
    2. Make sure the Slack app was created with the correct manifest
    3. Check that your Slack app is not restricted by workspace policies

    What the Bot Can Access#

    • Messages where it's mentioned
    • Messages in threads it's participating in
    • DMs sent directly to the bot

    What the Bot Cannot Access#

    • Messages in channels where it's not invited
    • Private messages between other users
    • Files or messages it wasn't mentioned in

    Data Handling#

    • Conversations are processed through AVCodex's secure infrastructure
    • Messages are not stored beyond what's needed for context
    • You can view conversation logs in your AVCodex dashboard under Chats

    You can manage Slack deployments programmatically using the AVCodex MCP Server.

    Available Tools#

    Tool Description
    list_slack_deployments List all Slack workspace connections
    get_slack_deployment Get details about a specific deployment
    disconnect_slack_deployment Remove a Slack connection

    Example Prompts#

    code
    "Show me all Slack deployments for my programming bot"
"Which Slack workspaces is my agent connected to?"
"Disconnect the Slack deployment for my test workspace"

    Workflow: Deployment Overview#

    code
    You: Show me all Slack deployments for my agents

AI: [Calls list_slack_deployments]

Agent: Programming Assistant (ID 123)
- Slack Workspace: "Acme AV"
  - Status: Connected
  - Channels: #av-programming, #bid-team, #dispatch
  - Last activity: 2 hours ago

Agent: Commissioning Bot (ID 456)
- No Slack deployments configured
    Note: MCP server access requires a Builder plan or higher. See the MCP Setup Guide to get started.

    *AVCodex · Your AV expertise. Amplified by AI.*

    Was this helpful?
    Edit this page →