Plex and Mailchimp integration

What moves between them

The primary flow moves Plex customers into Mailchimp lists and e-commerce customer records, so campaigns can segment and target based on Plex customer attributes (location, industry, order frequency). Plex sales orders sync into Mailchimp e-commerce orders with order totals and fulfillment status. Mailchimp campaign engagement events (opens, clicks, unsubscribes) flow back into Plex customer records as interaction history for the sales team. The cadence is tied to your manufacturing and marketing calendar: Plex data is polled after order entry or shipment; Mailchimp webhooks trigger on campaign sends and opens in near-real-time.

How ml-connector handles it

ml-connector stores both credential sets encrypted and bridges the authentication gap: on the Plex side, it holds either the OAuth 2.0 client credentials (with token refresh on expiry) or the SOAP Basic Auth credentials plus PCN, and polls the REST API on your configured interval, implementing exponential backoff on HTTP 429 rate limits. On the Mailchimp side, it authenticates with Basic Auth (API key) or OAuth 2.0 and extracts the data center prefix from the API key to route requests to the correct regional endpoint. Plex customers are mapped to Mailchimp list members by email or phone number; sales orders become e-commerce order records with order total and fulfillment status. Mailchimp webhooks are registered for list member changes and campaign events, verified against the secret URL, and written back into Plex customer records as read-only interaction notes. Because Plex has no webhook support, the integration polls Plex on a fixed schedule and receives Mailchimp engagement in near-real-time via webhooks. Every record carries an audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized discrete manufacturer in automotive supplies runs Plex for production, inventory, and customer management, and uses Mailchimp for customer newsletters and promotional campaigns. Before the integration, the marketing team manually exported customer lists from Plex and imported them into Mailchimp, losing purchase history and recent order data in the transfer. Campaign segments could not be based on actual order recency or product category. With Plex and Mailchimp connected, each new customer in Plex appears in Mailchimp within minutes, campaigns segment by order history and product shipments, and engagement metrics flow back into Plex so the sales team can see which customers opened product announcements. Month-end customer reviews are faster because recent campaign activity is already in the customer record.

What you can do

• •Sync Plex customers into Mailchimp lists and e-commerce customer records, with attributes like location and industry for segmentation.
• •Map Plex sales orders to Mailchimp e-commerce orders, including order totals and fulfillment status for financial tracking in campaigns.
• •Receive Mailchimp campaign engagement events (opens, clicks, unsubscribes) via webhooks and write them back into Plex customer records as interaction history.
• •Bridge Plex OAuth 2.0 or SOAP Basic Auth with Mailchimp Basic Auth or OAuth 2.0, refreshing tokens and handling rate limits automatically.
• •Poll Plex on a configurable schedule, retry failed syncs with exponential backoff, and maintain a full audit trail for every record.

Questions

Which direction does data move between Plex and Mailchimp?

Customers and orders flow from Plex into Mailchimp for campaign targeting. Mailchimp campaign engagement events (opens, clicks, unsubscribes) flow back into Plex customer records as interaction history for the sales team. Mailchimp has no financial or manufacturing entities to send back into Plex's ERP.

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

ml-connector polls the Plex REST API on a configurable interval (5 to 15 minutes recommended) and filters by modified_date to detect new and changed customers and orders. Mailchimp engagement is received in near-real-time via webhooks, creating an asymmetric but responsive flow.

What authentication setup is needed?

On the Plex side, ml-connector can use either OAuth 2.0 client credentials or SOAP Basic Auth with the company code (PCN). On the Mailchimp side, it uses Basic Auth with the API key (data center prefix extracted automatically) or OAuth 2.0. Both sets of credentials are stored encrypted.