Oracle Fusion Cloud ERP and Mailchimp integration

What moves between them

The primary flow moves from Oracle Fusion Cloud ERP into Mailchimp. Customer records from Oracle Fusion are polled on a schedule you define (typically every 5-15 minutes), filtered by last update timestamp to capture only new or modified customers. Each customer maps to a Mailchimp list member, with Oracle customer name, email address, billing address, and related attributes populating the Mailchimp member record. Inactive or deleted customers in Oracle can trigger unsubscribe or list removal in Mailchimp. Reference data such as customer segments or account types can tag members in Mailchimp for campaign targeting. The flow is read-only from Mailchimp back to Oracle; email campaign metrics or unsubscribe events may be logged for audit purposes but do not write back into Oracle Fusion.

How ml-connector handles it

ml-connector stores both the Oracle Fusion OAuth credentials and the Mailchimp API key encrypted in its database and retrieves them per request. For Oracle Fusion, it generates an OAuth 2.0 bearer token using the client credentials grant, caches it for the full one-hour lifetime to avoid unnecessary token calls, and refreshes automatically when a call returns 401 Unauthorized. The Oracle pod URL is stored per customer since Oracle publishes no shared base hostname. ml-connector polls Oracle Fusion on your schedule, applying a LastUpdateDate filter to fetch only customer records modified since the last run. It maps each Oracle customer record to the Mailchimp list member schema, looking up the Mailchimp data center prefix from the API key suffix or via OAuth metadata if needed. When a customer in Oracle Fusion has an email address, ml-connector upserts the member in Mailchimp; when a customer is marked inactive, it can remove or tag the member based on your configuration. Mailchimp's lack of webhook signature verification means the connection relies on HTTPS transport security and secret URL obscurity for receive paths, if any. Rate limits are not documented by Oracle, so ml-connector applies conservative backoff and retry logic. Every customer record carries an audit trail and can be replayed if a downstream sync fails.

A real-world example

A B2B software company uses Oracle Fusion Cloud ERP to manage customers, invoices, and payments across multiple regions. The marketing team manually exports the customer list from Oracle every few weeks and uploads it to Mailchimp to send product announcements and renewal reminders. Without automation, the Mailchimp list drifts from Oracle as new customers sign up, existing customers change billing addresses, or inactive accounts are archived. With Oracle Fusion and Mailchimp connected, new customer records automatically appear in the Mailchimp list within minutes, address changes propagate on the next sync cycle, and churned or inactive accounts are unsubscribed without manual intervention. Marketing campaigns now target current customers with up-to-date contact information, and the finance team no longer maintains dual master records.

What you can do

• •Poll Oracle Fusion Cloud ERP on a schedule you control and sync customer records into Mailchimp lists, filtering by last update timestamp to capture incremental changes.
• •Map Oracle customer names, email addresses, and billing details to Mailchimp list member attributes, handling data type conversions and required field validation.
• •Authenticate Oracle Fusion with OAuth 2.0 client credentials, cache the bearer token for its full one-hour lifetime, and refresh automatically on 401 responses.
• •Mark inactive or deleted customers in Oracle Fusion as unsubscribed or removed in Mailchimp, keeping both systems aligned as customers churn.
• •Track every customer sync in an audit log with full replay capability, so missed or failed records can be recovered without manual rework.

Questions

Why does Oracle Fusion need polling instead of webhooks?

Oracle Fusion Cloud ERP has no direct webhook system for external connectors without Oracle Integration Cloud middleware. The recommended pattern is polling the REST API every 5-15 minutes, filtering by LastUpdateDate to retrieve only new or modified records. This avoids the need for expensive middleware while keeping data fresh.

How does ml-connector handle Oracle's one-hour OAuth tokens?

ml-connector generates an OAuth 2.0 bearer token using client credentials, caches it for the full one-hour lifetime, and reuses it across multiple API calls to reduce overhead. When a call returns 401 Unauthorized, it automatically refreshes the token and retries the request without disrupting the sync.

What happens if a customer email address changes in Oracle Fusion?

ml-connector detects the change on the next polling cycle because Oracle includes the customer record in the LastUpdateDate filter. It updates the Mailchimp list member with the new email address so future campaigns reach the correct contact.