Does Procurement VMS integrate with Salesforce?
Procurement VMS has not yet confirmed its Salesforce integration, so treat this page as a draft. A Salesforce integration links purchase requests and spend to Salesforce records such as accounts and opportunities, authorizing through an external client app or connected app with OAuth 2.0 1, so spend can be traced to the work it supports.confirm
When a services team buys subcontractors or equipment for a customer project, the spend lives in procurement and the project lives in Salesforce. Connecting the two is left to a spreadsheet.
A link between the purchase and the Salesforce record lets finance see what a deal or project actually cost, and lets sales see committed spend before it is invoiced.
What syncs between Salesforce and Procurement VMS?
Salesforce is the system of record for customers and projects, and the procurement platform owns purchases. The table shows what a link between them typically covers.
| Data | Salesforce record | Direction | When | Notes |
|---|---|---|---|---|
| Accountsconfirm | Account | Salesforce → Procurement VMS | On a schedule | Used to tag a purchase with the customer it supports. |
| Opportunities or projectsconfirm | Opportunity, or a custom project object | Salesforce → Procurement VMS | On a schedule | Used to tag a purchase with the deal or project it supports. |
| Purchase linksconfirm | custom field or custom object | Procurement VMS → Salesforce | When a request is approved | Writes approved spend back to the Salesforce record, if you want it visible there. |
| Change notificationsconfirm | Change Data Capture or Platform Events | Salesforce → Procurement VMS | When records change | Lets the procurement platform react to changes instead of polling 2. |
How the Salesforce connection works, step by step
Setup is split between a Salesforce administrator and the Procurement VMS team. Salesforce recommends external client apps for new integrations 1.
- Create an external client appSalesforce recommends external client apps rather than connected apps for new integrations, and both authorize through OAuth 2.0 12.Salesforce administrator
- Choose scopes and a callback URLverify sourceRequest only the scopes the sync needs.Salesforce administrator with the Procurement VMS team
- Use your My Domain endpointsSalesforce recommends org-specific My Domain OAuth endpoints rather than the older generic ones 2.Procurement VMS team
- Decide which objects carry the linkverify sourceAccount and Opportunity are common. A custom object is common for projects.Salesforce administrator
- Plan for eventsPub/Sub API is Salesforce's recommended route for new integrations that react to Change Data Capture or Platform Events 2.Procurement VMS team
- Test in a sandboxRun the link end to end in a sandbox before production, and use a separate app per environment 2.Everyone above
Who this fits
Salesforce is used by mid-sized and large organizations, and how projects are modeled decides how the link works.
SMB
Very small teams are usually better served by the HubSpot page.
Mid-market · fits
Accounts and Opportunities as the link. Sync them on a schedule and tag purchases at request time.
Enterprise · fits
Several orgs or a heavily customized project model. Plan the link per org, and keep events and limits in mind.
Who does what
What to plan for in Salesforce
The first three come from Salesforce's documentation and a third-party guide to its 2026 API choices. Check all of them before the first sync.
Use an external client app for new work
Salesforce recommends external client apps over connected apps, and both use OAuth 2.0 1. A third-party guide notes the shift became standard from Spring '26 2.
Use your My Domain endpoints
A third-party guide says Salesforce recommends org-specific My Domain OAuth endpoints and separate apps per environment 2.
Limits are per org
Salesforce enforces per-org API limits, and the REST Limits resource reports current allocations 2. Plan call volume against them.
Prefer events to polling
Pub/Sub API is the recommended route for subscribing to Change Data Capture and Platform Events 2. Salesforce does not push outbound HTTP webhooks for these, so the platform has to subscribe.
Do not write spend into the wrong placeverify source
Decide whether spend is written back to Salesforce at all, and to which object, before building.
Security and access
Salesforce authorizes integrations through OAuth 2.0 and an app definition, so access is granted explicitly.
- Access runs through an external client app or connected app and OAuth 2.0 1.
- Use a separate app for each environment, such as sandbox and production 2.
- Request only the scopes the link needs, and keep write access limited to the fields it uses.verify source
- Procurement VMS describes its own security posture as SOC 2 Type II aligned and CCPA compliant, with role-based access control 3. Ask for current security documentation during scoping.
Related integrations and guides
Other systems in the same category, and the workflow guides that explain the processes this connection touches.
Salesforce integration FAQ
Procurement VMS has not yet confirmed its Salesforce integration, so there is no published support to point to. Use the form on this page and we'll tell you the current status for your setup.
Through the Salesforce REST API, authorized with OAuth 2.0 through an external client app or connected app 1. The integration reads accounts and opportunities, and can write spend back to a field or custom object.
Typically accounts, opportunities or projects, purchase links and change notifications. Direction is set per record type. The table above shows the proposed split.
Scope sets the timeline: what moves, whether it moves one way or both, and how much mapping your Salesforce setup needs. Procurement VMS states that the platform as a whole typically goes live in 4 to 8 weeks 3. The Salesforce connection is scoped within that timeline.
Salesforce recommends external client apps for new integrations, and both authorize through OAuth 2.0 1.
Yes, by subscribing to Change Data Capture or Platform Events through Pub/Sub API 2.
Salesforce enforces per-org limits, and the Limits resource reports what is left 2. Plan call volume against it.
Sources and how this page was verified
Facts about Salesforce on this page were checked against Salesforce's documentation on the date shown. Where only third-party integration documentation covers a behavior, the source is labelled third-party. Statements about Procurement VMS come from the company's published integration list; anything beyond that is confirmed with the product team before publishing. The Salesforce integration has not been confirmed for publication, so this page is a review draft.
- Salesforce Developers: Authorization through external client apps or connected apps and OAuth 2.0vendor documentation
- Unified: How to integrate with the Salesforce API (limits, events, OAuth clients)third-party documentation
- Procurement VMS: platform overview and integration listProcurement VMS
Salesforce is a trademark of Salesforce or its affiliates. Procurement VMS is not affiliated with, sponsored by or endorsed by Salesforce. Platform names are used only to describe compatibility.