Salesforce integration: accounts and opportunities

Take Prairie Foods, the customer whose lanes anchor most of Roadmark's quoting examples. Its Salesforce Account links to its Roadmark customer record, and the Mississauga → Joliet lane Prairie Foods ships sits under an Opportunity a rep already has open. When Quoting prices a request on that lane, the draft can link to that Opportunity instead of the two records drifting apart, one saying the deal's still open, the other showing it booked and paid. When the quote wins and becomes a load, Roadmark can move the Opportunity to Closed Won and set its amount from the load, so the pipeline a sales manager reviews in Salesforce already reflects it.

What links, and which way it moves

Accounts flow one way: Roadmark reads the Account and uses it to match a customer, but it doesn't rewrite what a rep has entered about who they are or how to reach them. Opportunities are the two-way part. Roadmark reads what's open on an Account so a linked quote points at the right one, and when that quote is won or lost, it can write the outcome back, closing the Opportunity and setting its amount rather than leaving a rep to update two systems by hand. Nothing about a customer's contract, rate or credit terms moves through Salesforce; those stay Roadmark's own record, the one billing and quoting price from.

Connecting it

An admin authorizes Roadmark with OAuth. Salesforce doesn't limit an OAuth grant to particular objects: every request runs with the profile and permission sets of the user who authorized it, so that user needs the API Enabled permission and access to Accounts and Opportunities, and nothing the connection doesn't need. Roadmark reads and writes only those two objects. Afterwards an admin can review, block or revoke the connection from Setup. Salesforce's app model changed in Spring '26: Salesforce no longer lets orgs create new connected apps by default and steers new integrations to external client apps, while existing connected apps keep working. API access is on by default in Enterprise, Unlimited and Performance editions; a Professional Edition org needs it added first. Once it's authorized, an admin matches each Roadmark customer to its Account, which is the step that decides which quotes and loads show up where.

Running beside your CRM

Roadmark's own quoting works without Salesforce: prospects move through lanes-first stages, from a first conversation with expected volume attached through to a signed rate. Teams that already run their pipeline in Salesforce don't have to move it. The two stay in step through the linked Account and Opportunity instead, so a rep can work from either screen and see the same numbers.

Turning it off, and what's recorded

The connection works the same as any other integration on Security: every write it makes to an Opportunity is recorded, who or what made it and when, and the connection itself can be turned off for a person, a team or the whole company at any time, from Roadmark rather than from Salesforce Setup. Nothing about the OAuth grant changes how sign-in works either; your team still signs in with the identity provider you already run.

See Quoting for how a price is built and Brokers for the inbox it starts from, and Analytics for what a linked Opportunity feeds into once the load closes.