Search Salesforcenotes and histories in your AI knowledge base.

The plan is that notes, activities, logged emails and files on accounts, contacts and opportunities come into the knowledge base — the history behind every customer and every project. Master data such as address, stage or amount remain authoritative in Salesforce; access is read-only.

Request a demo Cost check

Salesforce

One click · included in the setup

Example question

“What was agreed with Hofer Kunststofftechnik at the last meeting on the price adjustment?”

1 Answer with source

Connection

How the connection is designed

The plan is to grant access through Salesforce itself: you connect junova via a Salesforce account and define which areas are read — such as accounts, contacts, opportunities, notes and files. Access is read-only; nothing is created, changed or sent in Salesforce. Only what the connected account itself is allowed to see can be read; that is why a dedicated user with read-only permissions is often advisable. Whether your Salesforce edition allows access via the API and whether your administrator has to approve the connection is something we check with you before we start.

Once set up, synchronisation runs automatically: new and changed documents from Salesforce are added by themselves, without anyone having to upload anything.

Set-upThe connection is made with a click through your Salesforce account and is included in the setup. We agree beforehand which areas are read — ideally together with your Salesforce administrator. The user for the connection, custom objects and service cases are included in that discussion.

Documents

Which documents may be stored in Salesforce

Notes on visits and calls — on the account, on the contact or directly on the opportunity
Logged emails and completed activities that together make up the history of a project
Files on opportunities: quotes, technical drawings, requirement specifications, signed order confirmations
Older notes and attachments still attached to the record in the old format from the Salesforce Classic days
Several contacts at one account — purchasing, engineering, management — each with their own notes
Service cases with complaints and queries, if Salesforce is also used in customer service

Example questions

Examples of questions to your documents

“What was agreed with Hofer Kunststofftechnik at the last meeting on the price adjustment?”
1 Answer with source
“Which technical question did Steiner Maschinenbau’s purchasing department have on the opportunity Press Line 3?”
2 Answer with source
“Which drawing is attached to the opportunity for the lift modernisation in Lerchenfelder Straße, and which revision applies?”
3 Answer with source

Start

Before a connection is set up

The connection is made in one click via the account and is included in the setup. Every source comes with its own logins, permissions and folder logic — we check the prerequisites at your company together beforehand.

Until then, and independently of it, you can upload files, whole folders, emails, photos and voice memos. Before we start, we go through real questions with you to see how the answers look.

Preliminary check

What we check in advance

Master data such as address, stage, amount or close date remain authoritative in Salesforce; the plan is that the knowledge base names them as attributes but does not maintain them. Beforehand, we clarify which edition you use, whether API access is included in it and which user the connection should run under — what this user is not allowed to see cannot be read either. We check whether notes are in the new or the older format and which emails are logged in Salesforce rather than only in the mailbox. Whether service cases, Chatter posts or custom objects are needed is something we discuss; open tasks, events and reports are not documents and are not included.

FAQ

Frequently asked questions about this connection

We have a small Salesforce edition. Will it still work?

That depends on the edition and on add-ons: not every Salesforce edition includes API access as standard. Whether and how the connection works for you is something we check with you before we start — ideally together with your administrator or your Salesforce partner. Regardless of that, notes and files can also be uploaded as an export.

Our sales reps only see their own accounts. How does the knowledge base reflect that?

The plan takes a different route from Salesforce: in the knowledge base, permissions depend on document types and roles, not on sharing rules, role hierarchy or record owner. Meeting notes, for example, can be visible to the whole sales team, while quotes with terms and framework agreements are visible only to management. Your settings in Salesforce remain untouched. We discuss before we start how your logic can be mapped onto this.

Our notes go back to 2014, some still from Salesforce Classic. Will they come along?

The plan is to include them for the areas you select. Older notes and attachments are often in a different format from the newer ones; whether and how both are read is something we check beforehand. The date is attached to every note as an attribute, so the answer shows whether a piece of information is from 2014 or from last month. Before we start, we go through the answers on real questions.

We keep reworking fields and page layouts. Will that break the connection?

The plan is that reading takes place via the authorisation of the connected account; a changed page layout does not affect that. Changes to this account itself are the critical part: revoked read permissions, a deactivated user or a withdrawn authorisation. In that case the knowledge base stays as of the last sync, and the date on the source shows this. Ideally, tell us in advance about new objects or fields that should be read — then we will update the selection.

Industries

Typical for these industries

Request a demo — and clarify how Salesforce fits in

In thirty minutes by video we show what answers with sources look like, and clarify whether and how Salesforce can be connected at your company.