> ## 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.

# Salesforce

> Run Salesforce sales, service, campaigns, and commercial activity from your flows in Brain Studio.

**Salesforce** is an enterprise CRM designed for organizations with complex sales, service, and marketing processes. Unlike lighter CRMs such as Pipedrive or HubSpot, Salesforce runs on a highly configurable data model with SOQL, SOSL, custom objects, Knowledge Base, and native automation.

In **Brain Studio**, the integration exposes **46 tools** that let you create and update records, open cases, move opportunities, log activity, and query the CRM directly from the conversation. The pipeline, support cases, and commercial activity reflect what actually happened in the channel, with no manual re-entry.

## What Salesforce enables

When you connect **Salesforce**, you can:

* **Operate the commercial core** across accounts, contacts, leads, and opportunities
* **Manage campaigns** and contact/lead campaign membership
* **Open and track support cases** with associated comments and lookups
* **Log activity and collaboration**: tasks, events, notes, email, templates, and Chatter
* **Query and explore data** with search, SOQL, and SOSL
* **Work with objects generically** or in **bulk** when volume or flexibility requires it
* **Support knowledge and administration**: articles, categories, users, BLOB, and field metadata

***

## Installation

### Prerequisites

1. A **Salesforce organization** with the objects and permissions you will use (sales, service, campaigns, etc.).
2. Ability to **authorize a connected app** (OAuth), according to your admin policies.
3. A Salesforce edition with **API Access** enabled (Compatible with **Enterprise**, **Unlimited**, **Developer**, and **Performance** editions).
4. Clarity on whether you will connect a **Production Instance** or a **Sandbox Instance**, since the install modal asks you to choose one.

### How to connect it

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

If you prefer manual setup, follow these steps in **Marketplace**. The connection uses **Salesforce OAuth** - you choose production or sandbox instance and sign in; you do not need to copy credentials.

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

  <Step title="Find Salesforce">
    Locate the integration and click **Connect**.
  </Step>

  <Step title="Choose instance type">
    In the installation modal, choose whether you want to connect a **Production Instance** or a **Sandbox Instance**.
  </Step>

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

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

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

***

## Available tools

The integration exposes **46 tools**. We group them by Salesforce **function**; names match what you will see in Brain Studio.

<AccordionGroup>
  <Accordion title="Commercial CRM">
    Covers the **commercial lifecycle** across accounts, people, leads, and opportunities, plus **attachments** tied to records.

    **Included tools**

    * Create Account
    * Update account
    * Create contact
    * Update Contact
    * Create lead
    * Create Opportunity
    * Update Opportunity
    * Delete Opportunity
    * Create attachment

    **When to use this category**

    * When chat must **reflect** new records or changes in the **pipeline** and customer **master data**
    * When you need to **document** the relationship with **attachments** on the right record
    * When the flow **closes or discards** an opportunity explicitly
  </Accordion>

  <Accordion title="Campaigns">
    Links **contacts** and **leads** to **campaigns** and lets you **create** new campaigns.

    **Included tools**

    * Add contact to campaign
    * Add Lead to Campaign
    * Create campaign

    **When to use this category**

    * When conversation source or response must be **attributed** to a marketing or sales campaign
    * When you need to **add** an existing contact or lead to an **active campaign**
    * When the process must **create** the campaign before associating members
  </Accordion>

  <Accordion title="Cases and support">
    Operates **service** on **cases**: creation, lookup, and **comments** for follow-up.

    **Included tools**

    * Create Case
    * Get Case
    * Create case comment
    * List case comments

    **When to use this category**

    * When the user **reports** an incident or request and a Salesforce **case** must be created
    * When you need to **retrieve** the case or its **comment thread** before replying
    * When the flow must **add** a visible update on the case
  </Accordion>

  <Accordion title="Activity and collaboration">
    Leaves a **record** of commercial work and **communication**: timeline, email, templates, and **Chatter**.

    **Included tools**

    * Create Event
    * Create Note
    * Create Content Note
    * Create Task
    * Post message to Chatter feed
    * List Email Messages
    * List Email Templates
    * Update email template
    * Send email

    **When to use this category**

    * When you want Salesforce to reflect **meetings, tasks, or notes** after the conversation
    * When you need to **review or adjust templates** and **send** email from the flow
    * When the team uses **Chatter** for fast progress visibility
  </Accordion>

  <Accordion title="Query and search">
    **Explores** the CRM with search and native query languages.

    **Included tools**

    * Search records
    * Search Object Records
    * SOQL query
    * SOSL search

    **When to use this category**

    * When you need to **filter** or **retrieve record sets** with precise criteria
    * When the agent or flow must **validate** whether a record exists before creating another
    * When logic depends on **queries** aligned with Salesforce reports or business rules
  </Accordion>

  <Accordion title="Generic object operations">
    Works with **any object** supported by the tool when a specific action is not enough, plus **integration** utilities.

    **Included tools**

    * Create Record
    * Get record by ID
    * Update record
    * Delete record
    * Create or update record
    * Convert SOAP XML object to JSON

    **When to use this category**

    * When the object or fields **do not have** a dedicated tool in the list above
    * When you need generic **upsert** or **CRUD** operations with the integration's standard model
    * When you convert **SOAP responses** to continue the flow in JSON
  </Accordion>

  <Accordion title="Bulk / mass operations">
    Speeds up high-volume **create and update** operations for **accounts** and **opportunities**.

    **Included tools**

    * Create accounts (batch)
    * Update Accounts (Batch)
    * Create Opportunities (Batch)
    * Update Opportunities (Batch)

    **When to use this category**

    * When syncing **many** records from another system or from a structured conversational import
    * When the use case does **not** justify one-by-one calls due to performance or API cost
    * When your process already groups rows ready for **mass processing**
  </Accordion>

  <Accordion title="Knowledge and administration">
    Supports **knowledge base**, **users**, **BLOB**, and object **metadata**.

    **Included tools**

    * Get Knowledge Articles
    * Get Data Category Groups for Knowledge
    * List Knowledge Base Articles
    * Get user
    * Create user
    * Insert BLOB data
    * List object fields

    **When to use this category**

    * When the flow must **display or route with** knowledge articles
    * When you need to **query or create users** within your process
    * When working with **binary content** or needing object field **introspection** in the editor
  </Accordion>
</AccordionGroup>

***

## How to use in Brain

### In AI Agent

Use it when conversation is **open-ended**: the user may mix intents (run SOQL, create lead, open case). The agent chooses the tool within the subset you enable.

<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, go to the **Tools** tab.
  </Step>

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

  <Step title="Configure tools">
    Limit actions to what the agent should be allowed to do (for example, only cases and queries in a support channel).

    <Check>
      **Salesforce** appears in the agent tools list; adjust permissions from the integration settings icon.
    </Check>
  </Step>
</Steps>

### In Canvas

Use it when the process is **deterministic**: fixed steps (validate -> create record -> send email -> notify), with branches based on memory or user responses.

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

  <Step title="Select the tool">
    With the node selected, in **Tools** choose the action (for example **Create lead** or **SOQL query**).
  </Step>

  <Step title="Configure body and memory">
    Fill out the JSON in the node editor and, if needed, **Save response** in memory variables for following nodes.
  </Step>

  <Step title="Connect the flow">
    Link **Task completed** and **There was an error** to the commercial or support logic you define.

    <Check>
      Each node runs a single tool; Canvas order is your process.
    </Check>
  </Step>
</Steps>

The editor shows the expected body shape for each tool. The example below is **indicative** for **Create lead**; adjust it to your org's required fields and your memory variables.

```json theme={null}
{
  "FirstName": "{{$memory.nombre}}",
  "LastName": "{{$memory.apellido}}",
  "Email": "{{$memory.correo}}",
  "Company": "{{$memory.empresa}}",
  "LeadSource": "WhatsApp"
}
```

***

## Use cases

<AccordionGroup>
  <Accordion title="Lead capture and qualification from conversational channels">
    The contact arrives via **WhatsApp**, webchat, or an internal channel; the flow turns it into a **usable lead** inside Salesforce, with enough context for sales to continue without re-entering data.

    **Typical flow:**

    * The user starts the conversation and shares their data or commercial interest
    * The flow creates the **lead** and, if relevant, associates it to a **campaign**
    * If a related record already exists, instead of duplicating it, the flow updates it or continues on the correct object
    * The sales team receives a properly structured lead in Salesforce

    **Impact:**

    * Fewer lost leads between channel and CRM
    * Better traceability of commercial source
    * Less operational load for SDRs, account executives, or revenue ops

    **Ideal for:**
    Commercial teams that capture demand from conversational channels and use Salesforce as their central follow-up system.
  </Accordion>

  <Accordion title="Pipeline progression without leaving the channel">
    Every relevant conversation milestone can be reflected in **opportunities, tasks, notes, or activity**, making the pipeline show the real negotiation status instead of a delayed snapshot.

    **Typical flow:**

    * The prospect confirms interest, agrees to move forward, or provides key information
    * The flow creates or updates the **opportunity**
    * It adds a **note**, **task**, or **event** to leave traceability for the next step
    * The team sees progress directly in Salesforce, without waiting for manual updates

    **Impact:**

    * More reliable pipeline for forecasting and commercial management
    * Less lag between what was discussed and what was recorded
    * Better visibility for managers and sales leaders

    **Ideal for:**
    Enterprise teams with more structured commercial processes, multiple stages, and need for operational discipline.
  </Accordion>

  <Accordion title="Case creation and follow-up from the same flow">
    When a customer reports an issue or request, the flow can **open the case**, enrich it with comments, and retrieve its history to continue support without breaking context.

    **Typical flow:**

    * The user describes the issue in the conversation
    * The flow creates the **case** in Salesforce
    * It adds **comments** or retrieves existing comments if the ticket is ongoing
    * The support team works on a documented case while the customer keeps continuity in the channel

    **Impact:**

    * Fewer lost or poorly documented cases
    * Better continuity between conversation and Service Cloud
    * Less friction for support and customer success

    **Ideal for:**
    Organizations already running support in Salesforce that want the same level of control in conversational channels.
  </Accordion>

  <Accordion title="Internal CRM lookup by chat for sales or support teams">
    Executives, managers, or internal agents can query the status of **accounts, contacts, opportunities, cases, or campaigns** by chat without entering the Salesforce console first.

    **Typical flow:**

    * An internal user asks about an account, opportunity, or case
    * The flow uses **search**, **SOQL**, **SOSL**, or ID lookup depending on required precision
    * It returns current status, relevant context, or the exact record to take action
    * If needed, the same flow continues with an update, note, task, or email

    **Impact:**

    * Faster access to critical CRM information
    * Less context switching for the team
    * Salesforce becomes more useful as an operational source of truth, not just a system of record

    **Ideal for:**
    Sales, support, or leadership teams making quick decisions from internal or mobile channels.
  </Accordion>
</AccordionGroup>

***

## Integrations that pair well with Salesforce

<AccordionGroup>
  <Accordion title="Gmail">
    After creating a lead, moving an opportunity, or opening a case in Salesforce, the flow can automatically send a follow-up or confirmation email from the connected Gmail account.

    **Combined flow:** case opened in Salesforce -> confirmation email to customer with case number and next steps.

    [Gmail documentation](/en/guides/integraciones/productividad/gmail)
  </Accordion>

  <Accordion title="Calendly">
    When the commercial flow needs to move an opportunity and book a meeting at the same time, Salesforce keeps pipeline context and Calendly handles booking with real availability.

    **Combined flow:** lead qualified in Salesforce -> Calendly link for discovery call -> activity logged in Salesforce when appointment is confirmed.

    [Calendly documentation](/en/guides/integraciones/agendamiento/calendly)
  </Accordion>

  <Accordion title="Slack">
    Brain can update Salesforce and notify the team in Slack in the same flow. Every enterprise lead, urgent case, or critical opportunity change becomes an immediate alert.

    **Combined flow:** opportunity moved to "Negotiation" in Salesforce -> alert to #enterprise-sales in Slack with amount and account.

    [Slack documentation](/en/guides/integraciones/productividad/slack)
  </Accordion>

  <Accordion title="Google Sheets">
    For committees, QA, or forecasting, the flow can export pipeline or case extracts to a shared sheet without giving direct Salesforce access.

    **Combined flow:** SOQL query of opportunities in Salesforce -> update weekly forecast sheet in Sheets.

    [Google Sheets documentation](/en/guides/integraciones/productividad/google-sheets)
  </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 to install and use integrations in Brain Studio.
  </Card>
</CardGroup>