Plex and Salesforce integration

What moves between them

Data flows from Plex into Salesforce. Supplier records from Plex map to Salesforce accounts, so your customer-facing teams see current supplier status, contact info, and payment terms. Customer records from Plex also sync as accounts in Salesforce, keeping customer master data synchronized between ERP and CRM. Purchase orders and sales orders from Plex can map to Salesforce opportunities or custom objects, giving sales visibility into demand and commitments. The sync runs on a polling schedule you control, typically aligned with your procurement and sales cycles. Updates to supplier payment status or new purchase orders trigger re-polling and refresh the corresponding Salesforce records.

How ml-connector handles it

ml-connector stores both Plex and Salesforce credential sets encrypted and handles OAuth token refresh for each system independently. On the Plex side, it uses the OAuth 2.0 client credentials flow to obtain a bearer token and polls the REST API on a schedule you define, filtering by modified_date to find new and changed records. On the Salesforce side, it obtains a session token via client credentials flow against your authenticated org instance URL and presents the token on each API call. Because Plex offers no native webhooks, ml-connector polls on a cadence you choose based on your business cycle (for example, daily after close of business or after inventory receipt). Supplier records (name, address, contact, payment terms) map to Salesforce account fields, and customer records follow the same pattern. Purchase orders and sales orders can map to custom Salesforce objects or opportunities depending on your CRM schema. Salesforce session tokens expire after 2 hours, so ml-connector refreshes the token on 401 responses and retries the failed request. Every record carries a full audit trail, so if a downstream call fails you can replay the sync without re-polling Plex.

A real-world example

A mid-sized discrete manufacturer runs Plex for production, procurement, and finance, and uses Salesforce to manage customer relationships and sales pipelines. Before the integration, the sales team worked from spreadsheet exports of customer and order data from Plex, manually updated weekly or whenever a deal manager asked. Account information and order status were stale, and quotes often quoted outdated lead times or inventory. With Plex and Salesforce connected, customer master data syncs automatically whenever it changes in Plex, and current purchase and sales order data flows into Salesforce as opportunities so the sales team always sees what is committed and when delivery is expected. Deals can be quoted on current data, and the handoff to operations is transparent: sales sees what Plex committed, and operations sees what sales promised.

What you can do

• •Sync Plex supplier and customer records into Salesforce accounts so your CRM reflects current ERP master data.
• •Map Plex purchase orders and sales orders into Salesforce custom objects or opportunities for supply chain visibility.
• •Authenticate Plex with OAuth 2.0 client credentials and Salesforce with its instance-specific client credentials flow.
• •Poll Plex on a schedule you control and refresh Salesforce records with every new and changed order or customer record.
• •Handle Salesforce token expiry and Plex rate limits with automatic refresh and exponential backoff, with a full audit trail on every sync.

Questions

What data moves between Plex and Salesforce?

Customer and supplier records from Plex map to Salesforce accounts. Purchase orders and sales orders from Plex map to Salesforce custom objects or opportunities. ml-connector syncs on a schedule you control, typically daily or after key business events like close of business or inventory receipt.

How does ml-connector handle Plex's lack of webhooks?

Plex offers no native webhook system, so ml-connector polls the Plex REST API on a configurable interval you define, filtering by modified_date to find only new and changed records. This reduces the load on Plex while keeping Salesforce current.

What happens when Salesforce session tokens expire?

Salesforce session tokens expire after 2 hours and cannot be refreshed in client credentials flow. ml-connector detects the 401 response, obtains a new token, and retries the failed request automatically so no data is lost.