Salesforce

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

​

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:

​

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

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

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

​

What Hebno writes

Every write appears first as a confirmation card. You can change any field before you select Confirm. Hebno never deletes records, changes ownership, edits Salesforce settings or sends email from Salesforce. 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.

​

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 for review.

​

Troubleshooting

​

Related

• How integrations work
• Permissions and access
• Linked records
• HubSpot
• Pipedrive