Naarvin reads Salesforce through a read-only sign-in. Won opportunities become customer contracts with their products as obligations, subscriptions come from Salesforce CPQ or Revenue Cloud where the org has them, and open opportunities can feed planning once someone switches the pipeline on. Nothing is written back to Salesforce.
What does Naarvin read from Salesforce?
Salesforce brings the sales side of the picture: what customers signed, for how much and when. Your ERP still brings the ledger. Naarvin reads four kinds of record, and only the first two on every connection.
| In Salesforce | In Naarvin | When it is read |
|---|---|---|
| Won opportunities and their accounts | Customer contracts: the account is the customer, the close date the signing date, the amount the price | Every sync |
| Opportunity products | The contract's obligations, each delivered on its service date, or on the close date when it has none | Every sync |
| Salesforce CPQ subscriptions or Revenue Cloud asset state periods | Subscriptions with their monthly recurring revenue (MRR) and its changes | Only where the org has CPQ or Revenue Cloud |
| Open opportunities, and those closed in the last three years | Pipeline deals: stage, probability, amount, currency, close date, owner and created date | Only after the sales pipeline is switched on |
An opportunity counts as won when Salesforce marks it won and its close date falls on or before the day of the sync. An opportunity without products becomes a contract with one obligation for its full amount, delivered on the close date.
How are subscriptions read?
Naarvin reads subscriptions only where the org has Salesforce CPQ or Revenue Cloud. It finds them in the org's own list of objects and never guesses. Where the org has neither, or the signed-in user may not read them, the sync says no subscriptions were read, and won opportunities still become contracts.
- Salesforce CPQ: one subscription per subscribed product, with later amendments folded into it. Its MRR is the net price times the quantity, spread over the months of its term. A change in quantity becomes an expansion or a contraction on the day it takes effect.
- Revenue Cloud: one subscription per asset, with the MRR of each period applied from its start to its end.
- Left out and counted in a warning: one-time and usage charges, and CPQ records with no end date, because their price per period is not stated.
Where an org has both and CPQ holds subscriptions, only CPQ's are read, so no subscription is counted twice. Subscriptions are read in full on every sync.
What does the sales pipeline add?
The pipeline is off by default. Someone who manages connections switches it on from the connection card, under Sales pipeline, and the change is written to the audit log. Nothing extra is read until the next sync.
With it on, Naarvin also reads open opportunities and those closed in the last three years: the stage, Salesforce's probability, the amount and currency, the expected close date, the owner's name and the created date. Each sync notes when a deal first appears or changes stage, so conversion by stage builds up as deals move.
In FP&A AI, a plan's revenue model can then show three sources from this connection: revenue already contracted and still to be recognised, subscriptions carried forward from today's MRR, and open deals weighted by their stage probability. Each is shown on its own, and a plan includes it only when someone chooses to.
How often does it sync?
On the schedule you set: every 15 or 30 minutes, every 1, 2, 4, 6 or 12 hours, daily or weekly at a time in your own time zone, or only when someone runs a sync. The first sync reads every won opportunity. Later syncs read the opportunities changed since the last one. A full sync, which anyone allowed to sync can run, also marks an opportunity that is no longer won as removed, so its contract stops counting.
Which companies and currencies does it handle?
One Salesforce org links to one company in Naarvin: the company that sells through it, usually one your ERP connection already loads. The org's currency must match that company's currency. In a multi-currency org each opportunity keeps its own currency; in a single-currency org every opportunity takes the org's currency.
What does the connection not do?
- It never writes to Salesforce. No stage, field or record is changed.
- It brings no ledger. Invoices, payments and balances come from your ERP.
- It reads opportunities, their products and accounts, the organization record and the subscription objects above. Leads, quotes and cases are not read.
- In the pipeline, owners are read by name; nobody's Salesforce login or profile is read.
How do you connect Salesforce?
- Choose the companyDecide which Naarvin company sells through the org. If your ERP connection already loads it, you link to that company.
- Sign in to SalesforceUse a user who can read opportunities, accounts and products, and CPQ subscriptions or asset state periods if you use them. Nothing is typed first: Salesforce returns the org address with the sign-in. The tokens are encrypted when saved and never shown again.
- Link the orgLink the org to the company. Naarvin checks that the two use the same currency.
- Set the schedule and run the first syncCompare a few won opportunities and their products with Salesforce, and read the warnings, such as subscriptions that were left out.
- Switch on the pipeline if you plan with itFrom the connection card, under Sales pipeline. The next sync reads open and recently closed opportunities.
Questions people ask
Does Naarvin change anything in Salesforce?
No. Every request it makes is a read. Approvals, postings and payments in Naarvin never reach Salesforce.
Do we need Salesforce CPQ or Revenue Cloud?
No. Won opportunities become contracts in any org. Subscriptions and their MRR are read only where the org has CPQ or Revenue Cloud, and the sync says when it found neither.
Is the pipeline read from the start?
No. It stays off until someone who manages connections switches it on from the connection card. Until then only won opportunities are read, as contracts.
Can we connect more than one Salesforce org?
Yes, as separate connections, each linked to the company that sells through it. The same org cannot be connected twice, because that would count every contract twice.