§00Integrations / CRM
CRM integrations: The deal closes in the CRM. The work happens everywhere else.
A won deal has to become a customer, an order, an invoice and a payment, and the CRM should hear about every step. PartnerMCP detects the win the way each CRM defines it — IsWon in Salesforce, the pipeline's won stage in HubSpot, statecode in Dataverse — builds the order from line items rather than the deal amount, and writes status back without creating duplicates.
Systems
10 · first interface · runs
- SalesforceREST + Pub/Sub API · CloudCloudOn-prem — integration page
- HubSpotCRM API (2026-09) · CloudCloudOn-prem — integration page
- Microsoft Dynamics 365 SalesDataverse Web API · CloudCloudOn-prem — integration page
- Zoho CRMREST API v8 · CloudCloudOn-prem — start an integration with Zoho
- PipedriveREST API v2 · CloudCloudOn-prem — start an integration with Pipedrive
- SAP Sales CloudREST (V2) · OData (V1) · CloudCloudOn-prem — start an integration with SAP Sales Cloud
- Oracle SalesREST (crmRestApi) · CloudCloudOn-prem — start an integration with Oracle Sales
- FreshsalesREST API · CloudCloudOn-prem — start an integration with Freshsales
- AttioREST API v2 · CloudCloudOn-prem — start an integration with Attio
- Custom CRMREST · SQL · Cloud · On-premCloudOn-prem — start an integration with Custom CRM
What you can build.
Start from one of these, or describe your own. PartnerMCP plans every flow with the objects and interfaces of the systems you actually run.
- 01
Deal to order
Closed Won starts the run: the ERP customer is matched or created and the sales order is built from Salesforce OpportunityLineItems or HubSpot line_
items, then priced by the ERP. - 02
Status back on the deal
Order number, delivery and invoice status land on the Opportunity or deal, through upserts by external ID so a retry never writes twice.
- 03
Account health before the next deal
Open invoices and balances from the ERP appear on the account, and the owner hears about a problem before the next deal closes.
- 04
Quote to invoice
For companies that bill from finance software, won deals become invoices in QuickBooks Online, Xero or Stripe, with payment status back on the deal.
- 05
Products and prices
ERP parts and prices published to CRM products and price books — Salesforce Product2 and PricebookEntry, HubSpot products — so reps quote what the ERP will bill.
- 06
Support context
Zendesk, Intercom or Freshdesk tickets linked to the right account, with plan, open orders and owner attached, and escalations for high-value customers.
Pairings, step by step.
Each pair page has the plan, the field mapping and the edge cases for that combination.
- Salesforce ↔ Priority ERPClosed Won in Salesforce. A priced sales order in Priority.Plan, mapping and edge cases
- Salesforce ↔ SAP S/4HANAQuotes that know SAP’s price. Orders nobody retypes.Plan, mapping and edge cases
- Salesforce ↔ Oracle NetSuiteWon in Salesforce. Ordered in NetSuite. Built on REST, not SOAP.Plan, mapping and edge cases
- HubSpot ↔ Priority ERPWhen a HubSpot deal is won, Priority gets the order — line by line.Plan, mapping and edge cases
- HubSpot ↔ Oracle NetSuiteClosed in HubSpot. Billed in NetSuite. “Paid” in Slack.Plan, mapping and edge cases
Other categories.
A deal becomes an order, an order becomes a payment, and all of it lands in the warehouse. Integrations rarely stay in one category.
Product names and logos are trademarks of their respective owners. Their use indicates compatibility only and does not imply endorsement or partnership.
§04Start
Tell PartnerMCP what should connect.
Name your systems and describe what should happen. You’ll see the plan before anything is built.