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

> ## Agent Instructions
> Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems.
> Use British English (organisation, not organization).
> Every feature and integration described in these docs is available. Describe it as documented.
> Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only.
> Do not discuss commercial terms. Direct commercial questions to support@hebno.com.
> Start with /index and /get-started/quickstart.

# Salesforce

> Read Salesforce accounts, contacts, opportunities and activity history in Hebno, and add notes, tasks and stage changes after you confirm.

The Salesforce integration shows your pipeline next to your client work. Ask for the history on an account, what is open with a contact, or where an opportunity stands, and Hebno answers from Salesforce with each record cited. When a request implies a change, such as adding a note or moving an opportunity to a new stage, Hebno shows a confirmation card and writes to Salesforce only after you confirm.

## At a glance

| | |
| - | - |
| **Connection** | Personal connection. Each member connects their own Salesforce user. |
| **Default access** | Read and write |
| **Attach** | Accounts, contacts, opportunities |
| **Search** | Hebno searches Salesforce when a request mentions a client, contact, deal, stage, close date or past activity |
| **Link** | A project links to a Salesforce account and to one or more opportunities |
| **Write** | Add a note, create a task, log a call or meeting, update an opportunity, create a contact. Every write needs a person to confirm. |

## Before you start

You need:

* A Salesforce user with API access enabled on their profile or permission set.
* Your Salesforce login address if your firm uses My Domain, for example `https://northwind.my.salesforce.com`. Members of a sandbox use the sandbox login address.
* An allowed integration. An owner or admin sets **Salesforce** to **Allow** under **Admin → Connectors → Catalogue**.

Hebno requests these OAuth scopes:

| Scope | Why Hebno needs it |
| - | - |
| `api` | Read and write records through the Salesforce REST API as the connected user |
| `refresh_token` | Renews access so you are not asked to sign in again |

### For Salesforce administrators

Hebno connects through an OAuth app in your Salesforce org. If your org restricts which users can authorise apps, a Salesforce administrator opens **Setup → Manage Connected Apps** (or **External Client App Manager**), finds the Hebno app and sets **Permitted Users** to **Admin approved users are pre-authorized**. Then assign the permission sets or profiles of the members who should connect. Members outside that list see an authorisation error when they select **Connect**.

## Connect Salesforce

**1. Start the connection**

Open **Settings → Connections**, find **Salesforce** and select **Connect**. You can also select **Connect** from the prompt in a chat.

**2. Sign in to Salesforce**

Enter your Salesforce login address if asked, sign in, and approve the access Hebno requests.

**3. Return to Hebno**

The card shows **Connected** with your Salesforce username.

Hebno reads and writes with your own permissions, so you see only the accounts, opportunities and fields that your Salesforce profile, sharing rules and field-level security allow. Tokens are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**.

## What Hebno reads

| Salesforce object | Fields Hebno uses | Typical questions |
| - | - | - |
| **Account** | Name, industry, owner, annual revenue, website, parent account | "What do we know about Contoso Retail?" |
| **Contact** | Name, title, email, phone, account | "Who are our contacts at Contoso, and what are their roles?" |
| **Opportunity** | Name, stage, amount, close date, probability, account, owner, next step | "Which Contoso opportunities are open, and when do they close?" |
| **Task and Event** | Subject, due date, status, related account or opportunity, owner | "What was the last meeting we logged with Contoso?" |
| **Note** | Title, body, related record | "What did we note after the discovery call?" |
| **Owner** | Name, email, role | "Who owns the Contoso account?" |

Reads are live. Hebno queries Salesforce when a request needs it. Only what a reply used is stored with the conversation as its sources.

> [!WARNING]
>
> Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including notes and contact details from Salesforce.

## What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select **Confirm**.

| Action | Salesforce object | Fields on the card |
| - | - | - |
| **Add a note** | Note | Related account, contact or opportunity, title, body |
| **Create a task** | Task | Subject, related record, due date, assigned user, status |
| **Log a call or meeting** | Task or Event | Subject, type, date and time, related record, notes |
| **Update an opportunity** | Opportunity | Stage, amount, close date, next step |
| **Create a contact** | Contact | Name, title, email, phone, account |

![Confirmation card for Salesforce with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-salesforce.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=f649923e3deeac23b5a3e8724e8fafdb)

A Salesforce change pending confirmation. Nothing is written until you confirm.

Hebno never deletes records, changes ownership, edits Salesforce settings or sends email from Salesforce.

```mermaid theme={"system"}
sequenceDiagram
  participant You
  participant Hebno
  participant Salesforce
  You->>Hebno: Move the Contoso renewal to Negotiation and add a note
  Hebno->>Salesforce: Find the Contoso renewal opportunity
  Salesforce-->>Hebno: Opportunity, stage Proposal, amount, close date
  Hebno-->>You: Confirmation cards for the stage change and the note
  You->>Hebno: Confirm
  Hebno->>Salesforce: Update opportunity and create note as you
  Salesforce-->>Hebno: Records saved
  Hebno-->>You: Done, with links to the records
```

Writes are made as your Salesforce user, so Salesforce shows you as the author and applies its own validation rules. If a rule rejects a change, the card shows Salesforce's message and your edits are preserved.

## Link a project to an account

Linking marks which Salesforce records belong to a project, so you can ask "where does the deal stand?" without naming the opportunity.

1. Open the project and select **Brain**.
2. Under **Linked records**, select **Link record**, then **Salesforce**.
3. Search for the account and select it. Repeat to add the opportunities that belong to the engagement.

In chats tagged to the project, Hebno starts with the linked account and opportunities for any client or pipeline question, and cards for notes and tasks default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md).

## Use Salesforce in chat

* **Attach**: open the **+** menu, choose **Sources → Salesforce**, and pick an account, contact or opportunity. Or type `/` and choose **Salesforce**.

* **Ask**: name the client, contact or deal in your request. For example:

  > Prep me for Thursday's pitch meeting with Contoso Retail: open opportunities, who we have met, and what we proposed last time.

  > Summarise the account history for Contoso since January and flag anything that went quiet.

  > Add a note to the Contoso renewal: Priya wants fixed-fee pricing for phase 2. Create a follow-up task for me for Monday.

* **Research runs** show a **Reviewing Salesforce** step, with a chip for each account, opportunity and activity it read.

* **Agents** can read Salesforce on a schedule, for example a Friday summary of opportunities with a close date in the next 30 days. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review.

## Troubleshooting

| Symptom | Fix |
| - | - |
| Salesforce shows an error saying the app is not approved for your user | A Salesforce administrator needs to add your profile or permission set to the Hebno app's permitted users. See [For Salesforce administrators](#for-salesforce-administrators). |
| Hebno cannot find an account you can open in Salesforce | Check that you connected the right org (production or sandbox). Disconnect and reconnect with the correct login address. |
| A field is missing from answers | Your Salesforce field-level security hides it from your user. Hebno cannot read what you cannot read. |
| A write fails with a Salesforce validation message | Fix the field the message names on the card and select **Confirm** again. |
| **Reconnect Salesforce** appears | The refresh token was revoked or expired. Select **Connect** to sign in again. |
| Requests fail with an API limit message | Your org has used its daily Salesforce API allowance. Retry after it resets, or ask your Salesforce administrator. |

## Related

* [How integrations work](https://hebno.com/docs/integrations/index.md)
* [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md)
* [Linked records](https://hebno.com/docs/projects/linked-records.md)
* [HubSpot](https://hebno.com/docs/integrations/hubspot.md)
* [Pipedrive](https://hebno.com/docs/integrations/pipedrive.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.