Oracle PeopleSoft and Mailchimp integration

What moves between them

Employee records and customer contacts from Oracle PeopleSoft flow into Mailchimp as contacts in designated audiences. The integration polls the PeopleSoft employeedirectory endpoint to fetch new hires, updates, and terminated employees, and pulls customer records from CUSTOMER_CI. Contact records are upserted into Mailchimp audiences based on email address as the unique key. Terminations in PeopleSoft can trigger unsubscribe actions in Mailchimp. The flow is one-way from PeopleSoft to Mailchimp on a schedule configured by the customer, typically daily or on payroll cycles.

How ml-connector handles it

ml-connector stores both the PeopleSoft credentials and the Mailchimp API key encrypted. For PeopleSoft it handles HTTP Basic Auth credentials and the unique hostname and node configuration per customer instance. For Mailchimp it extracts the data center prefix from the API key and constructs the correct API base URL. Because PeopleSoft has no webhooks, ml-connector polls on a fixed schedule with date-range filters to capture only new or changed records since the last run, reducing load on the on-premise system. Contact fields from the PeopleSoft employeedirectory service like email, first name, and last name are mapped to Mailchimp contact fields, and custom fields in Mailchimp store the PeopleSoft person ID to prevent duplicate syncs. PeopleSoft service operations require explicit activation by the admin, so ml-connector includes documentation for the exact operations to enable. Mailchimp API calls use standard HTTP retries for rate limits and transient failures. Every record carries an audit trail tracking the sync timestamp, source ID, and action taken.

A real-world example

A mid-sized financial services firm runs Oracle PeopleSoft for HR and payroll across multiple offices and uses Mailchimp for employee newsletters and customer marketing campaigns. Before the integration, the marketing team manually exported the employee directory from PeopleSoft and imported it into Mailchimp several times a year, often with duplicate or stale email addresses that bounced. With Oracle PeopleSoft and Mailchimp connected, the employee list syncs automatically, capturing new hires within a day and removing terminated employees from email campaigns. Customer contact data from the same PeopleSoft instance populates separate Mailchimp audiences for product announcements, reducing manual list maintenance and keeping contact records current.

What you can do

• •Sync employee records from PeopleSoft's employeedirectory service into Mailchimp email audiences with email address as the unique key.
• •Map customer contact records from PeopleSoft's CUSTOMER_CI component interface into Mailchimp contact lists for targeted campaigns.
• •Handle PeopleSoft's HTTP Basic Auth or OAuth2 Bearer token authentication and Mailchimp API key setup automatically.
• •Poll PeopleSoft on a schedule with date-range filters to capture new and updated contacts without overwhelming the on-premise system.
• •Maintain an audit trail of every contact sync, including source ID, timestamp, and action taken, with full error replay on failure.

Questions

How does ml-connector handle PeopleSoft's on-premise architecture where each customer has a unique hostname and port?

ml-connector accepts the full PeopleSoft instance hostname, port, and Integration Broker node name as configuration per customer. There is no shared PeopleSoft sandbox across customers, so ml-connector uses the credentials and URL provided for that customer's specific on-premise environment or Oracle Cloud Manager instance. Testing requires access to the customer's own development environment or PUM images.

Why does ml-connector poll PeopleSoft instead of relying on webhooks?

PeopleSoft has no webhooks available for external connectors. The Integration Broker Asynchronous Publish/Subscribe feature can push XML messages to HTTP endpoints, but it requires custom configuration and returns data in PeopleSoft rowset XML format. Polling with date-range filters on the REST endpoints is the standard recommended approach, capturing new and changed records on a schedule the customer controls.

What fields are mapped from PeopleSoft employee records to Mailchimp contacts?

Core fields include email address, first name, last name, and department. ml-connector stores the PeopleSoft EMPLID in a Mailchimp custom field to track the source record and prevent duplicate syncs. Additional fields like job title or cost center can be mapped to custom fields in Mailchimp based on the customer's campaign segmentation needs.