> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Slack

> Send notifications, escalate cases, and coordinate operations in Slack from your conversational flows in Brain Studio.

**Slack** is where teams coordinate daily operations. Unlike email integrations such as Gmail (which handle formal and asynchronous communication), Slack is designed for internal real-time response: the team gets informed, decides, and acts in the same channel.

In **Brain Studio**, this integration turns Slack into the immediate reaction point for your flows: context-rich escalations, operational alerts, channel creation by customer or project, executive summaries, and approvals, all inside the workspace where the team already works.

## What Slack enables

When you connect **Slack**, you can:

* **Escalate cases to the right team immediately** — enriched messages, threads, or Block Kit to the right channel, group, or person
* **Create channels for each customer, project, or incident** with topic, description, and preconfigured members
* **Get operational visibility without dashboards** — alerts for leads, payments, errors, or milestones delivered where the team already talks
* **Trigger approvals and reminders** as part of processes requiring human validation before continuing
* **Work with users, groups, and files** to identify people, update memberships, or share documents

***

## Installation

### Prerequisites

1. An **active Slack account** with access to the target workspace.
2. Permissions to connect applications in your Slack workspace.

### How to connect it

The most direct way is using [**Jelou Agent**](/en/guides/getting-started/jelou-agent): describe what you need and the agent connects **Slack** automatically inside the flow.

If you prefer manual installation, follow these steps in **Marketplace**. The connection uses **Slack OAuth**; you do not need to copy credentials.

<Steps>
  <Step title="Open Marketplace">
    In Brain Studio, open **Marketplace** from the side menu.
  </Step>

  <Step title="Search Slack">
    Find the integration and click **Connect**.
  </Step>

  <Step title="Authorize with Slack">
    Complete the OAuth authentication flow with your Slack account.
  </Step>

  <Step title="Confirm installation">
    The integration will appear as **connected**.

    <Check>
      You can use it in **Canvas** or add it as a tool in **AI Agent**.
    </Check>
  </Step>
</Steps>

***

## Available tools

This integration exposes **33 tools** in Brain Studio. We group them by **Slack operation type**; names match what you see in the product.

<AccordionGroup>
  <Accordion title="Messaging and conversation">
    Centralizes message sending, editing, and reading in Slack, both in channels and direct messages and threads.

    **Included tools**

    * Send message
    * Send message (Advanced)
    * Send message to channel
    * Send message to user or group
    * Send a large message (3000+ characters)
    * Create and send a Block Kit message
    * Reply to a message thread
    * Update message
    * Delete message
    * Find message
    * List replies
    * Add emoji reaction

    **When to use this category**

    * When the flow needs to **notify**, **reply**, or **escalate** something in Slack
    * When you want to send richer messages with **Block Kit** or handle long text without truncation
    * When you need to work on an existing conversation, for example **reply in thread**, **edit**, or **delete** a message
    * When the agent must find a previous message or react with emoji as part of an internal workflow
  </Accordion>

  <Accordion title="Channels">
    Lets you create, configure, and manage channels in the workspace.

    **Included tools**

    * List channels
    * Create channel
    * Archive channel
    * Set channel description
    * Set channel topic
    * List channel members
    * Invite user to channel
    * Remove user

    **When to use this category**

    * When you need to **open a new channel** for a project, incident, customer, or squad
    * When you want to keep channel **topic**, **description**, or **membership** up to date
    * When the flow should orchestrate internal onboarding, for example by creating a channel and automatically inviting the right team
    * When you need to inspect channel composition before acting
  </Accordion>

  <Accordion title="Users and presence">
    Works with workspace users and authenticated member context.

    **Included tools**

    * List users
    * Find user by email
    * Get current user
    * Update profile
    * Set status

    **When to use this category**

    * When the flow needs to identify a specific person in Slack before messaging or inviting them to a channel
    * When you want to adapt logic to the **authenticated user**, profile, or connected workspace
    * When you need to update name, title, or status as part of an internal process
    * When users enter via email and you need to resolve their Slack identity
  </Accordion>

  <Accordion title="User groups">
    Manages user groups and members for internal coordination.

    **Included tools**

    * List group members
    * Update group members

    **When to use this category**

    * When your operation is organized by **user groups** and you need to query or update group composition
    * When the flow should route communication or alerts to pre-defined functional groups
    * When you want to automate membership changes in internal groups based on business events
  </Accordion>

  <Accordion title="Files">
    Lets you upload, get, list, and delete files in Slack.

    **Included tools**

    * Upload file
    * Get file
    * List files
    * Delete file

    **When to use this category**

    * When the flow needs to share documents, reports, or evidence in Slack
    * When you want to retrieve context about a file already uploaded to the workspace
    * When the process needs to list recent files or clean up files that should no longer remain available
  </Accordion>

  <Accordion title="Automation and internal coordination">
    Supports reminders and simple approval mechanisms inside Slack.

    **Included tools**

    * Create reminder
    * Approve workflow

    **When to use this category**

    * When you want a flow to leave an **operational reminder** to a person or team
    * When you need to introduce **human approval** in an automated process
    * When Slack acts as the coordination layer before executing a sensitive action in another integration
  </Accordion>
</AccordionGroup>

***

## How to use in Brain

Once connected, you can use **Slack** in two surfaces:

### In AI Agent

Ideal when the agent needs to notify the team or find a workspace member autonomously during conversation.

<Steps>
  <Step title="Open the AI Agent node">
    In Canvas, select or add the **AI Agent** node.
  </Step>

  <Step title="Open Tools">
    In the right panel, open the **Tools** tab.
  </Step>

  <Step title="Add Slack">
    Use **Add tool**, search for **Slack**, and enable it.
  </Step>

  <Step title="Configure tools">
    Choose the full integration or enable only the actions you need.

    <Check>
      **Slack** appears in the agent tools list and you can open its settings using the gear icon.
    </Check>
  </Step>
</Steps>

The agent will automatically decide when to send a message, find a user, or check a channel depending on the conversation context.

### In Canvas

Ideal when you need full flow control (for example: detect event → format message → send notification to the responsible channel).

<Steps>
  <Step title="Drag Slack into Canvas">
    In the side panel, open **Marketplace** and drag **Slack** into the flow.
  </Step>

  <Step title="Select the tool">
    With the node selected, in **Tools** choose the action (for example **Send message**).
  </Step>

  <Step title="Configure request body and memory">
    Fill in the request body JSON and, if needed, **Save response** to a memory variable.
  </Step>

  <Step title="Connect the flow">
    Link the **Task completed** and **An error occurred** outputs to the next nodes.

    <Check>
      The node is ready to run in the order defined by your flow.
    </Check>
  </Step>
</Steps>

**Configuration example:**

The node editor shows a JSON body aligned with the **Send message** tool. Use `channelId` for channels or `email` for DMs. Blocks allow rich-formatted messages.

```json theme={null}
{
  "channelId": "{{$memory.slack_channel_id}}",
  "text": "New lead registered: {{$memory.customer_name}} — {{$memory.company}}",
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "*New lead registered*\n*Name:* {{$memory.customer_name}}\n*Company:* {{$memory.company}}\n*Source:* WhatsApp"
      }
    }
  ]
}
```

***

## Use cases

<AccordionGroup>
  <Accordion title="Case escalation from WhatsApp to internal team">
    When a conversation needs human intervention, the flow escalates it to Slack with the right context, in the right channel, without copy-paste.

    **Specific example:** an e-commerce customer requests a refund via WhatsApp. The channel cannot process refunds directly. The flow sends a Block Kit message to #refund-support with customer name, amount, order number, and a conversation excerpt. The team receives full context and acts without asking for details again.

    **Ideal for:** support, sales, or incident teams operating in conversational channels and coordinating in Slack.
  </Accordion>

  <Accordion title="Real-time operational alerts without checking dashboards">
    Instead of monitoring systems manually, critical events arrive directly in the responsible team's channel.

    **Specific example:** a SaaS company connects lead capture flow to Slack. Each time an enterprise lead arrives, the flow sends an alert to #enterprise-leads with name, company, source channel, and first expressed intent. The sales director sees it and assigns an executive in the same thread.

    **Ideal for:** revenue ops, support, operations, and management that need immediate response to critical events.
  </Accordion>

  <Accordion title="Automatic channel creation by customer or project">
    Every new customer, project, or incident gets a Slack channel ready to operate, with topic, description, and members invited automatically.

    **Specific example:** an implementation agency uses Brain Studio for onboarding. When a new customer is confirmed, the flow creates #cli-customer-name, sets the topic with kick-off date and owner, and invites the implementation team. The channel exists before the first meeting.

    **Ideal for:** agencies, consultancies, customer success, and organizations that open channels by customer or initiative.
  </Accordion>

  <Accordion title="Executive summaries without manual reporting">
    Instead of checking multiple systems, the flow consolidates what matters and delivers periodic summaries in Slack.

    **Specific example:** every Monday, a commercial team gets a message in #sales-summary with new leads of the week, deals that changed stage, and scheduled meetings. The message is built from HubSpot, Calendly, and flow data. Nobody manually compiles the report.

    **Ideal for:** founders, managers, and leaders who use Slack as a tracking and decision center.
  </Accordion>
</AccordionGroup>

***

## Integrations that combine well with Slack

<AccordionGroup>
  <Accordion title="HubSpot">
    When a qualified lead enters the CRM or a deal changes stage, the flow can notify the corresponding Slack channel. The sales team sees the milestone without opening HubSpot.

    **Combined flow:** lead created in HubSpot → alert to #sales in Slack with name, company, and stage.

    [HubSpot documentation](/en/guides/integraciones/crm/hubspot)
  </Accordion>

  <Accordion title="Salesforce">
    In organizations with complex Salesforce operations, Slack is the immediate reaction surface. Each critical opportunity, urgent case, or relevant CRM change can trigger an alert to the responsible team channel.

    **Combined flow:** urgent case created in Salesforce → alert to #urgent-support with case number and priority.

    [Salesforce documentation](/en/guides/integraciones/crm/salesforce)
  </Accordion>

  <Accordion title="Google Calendar">
    When a relevant meeting is created, rescheduled, or canceled, the flow can notify the team channel so everyone is aware without checking calendar manually.

    **Combined flow:** event created in Google Calendar → message to #team with date, time, and attendees.

    [Google Calendar documentation](/en/guides/integraciones/agendamiento/google-calendar)
  </Accordion>

  <Accordion title="Supabase">
    Each insertion or critical status change in the database can become an operational alert in Slack. Technical or operations teams react without monitoring the database directly.

    **Combined flow:** record updated to "error" in Supabase → alert to #ops-incidents with table, ID, and status.

    [Supabase documentation](/en/guides/integraciones/infraestructura/supabase)
  </Accordion>
</AccordionGroup>

***

## Related articles

<CardGroup cols={2}>
  <Card title="Integrations" href="/en/guides/integraciones/integraciones" icon="grid">
    Catalog of integrations available in Marketplace.
  </Card>

  <Card title="How to use integrations in Brain" href="/en/guides/integraciones/como-usar-integraciones-en-brain" icon="book-open">
    General flow for installing and using integrations in Brain Studio.
  </Card>
</CardGroup>