Oracle E-Business Suite and Mailchimp integration

What moves between them

Customer and contact data flows one direction: from Oracle E-Business Suite into Mailchimp. ml-connector polls EBS for customer accounts and associated contacts, maps them to Mailchimp list members by email address, and upserts them into a designated Mailchimp list. Contact name, company name, email, phone, and custom attributes like customer type and status flow to Mailchimp as standard and custom fields. Mailchimp has no financial or transaction data, so purchase orders, invoices, and GL accounts remain in EBS only.

How ml-connector handles it

ml-connector stores the EBS ISG hostname, port, and credentials encrypted and maintains an authenticated session, refreshing the access token before it expires and re-authenticating on a 401 response. The EBS account context headers (responsibility, application, security group, organization) are configured per customer and passed on every request. On the Mailchimp side, ml-connector extracts the data center prefix from the API key and builds the correct regional endpoint URL. Customer records are read from the EBS HZ_CUST_ACCOUNTS and HZ_PARTIES tables via ISG REST calls with limit/offset pagination, filtered by LAST_UPDATE_DATE to capture only recent changes. Each contact is matched to a Mailchimp list member by email address; if found, the member is updated; if not found, a new member is created. Rate limiting returns HTTP 429, so ml-connector backs off with exponential retry. The integration is fully auditable, and each customer upsert is logged with its source and target record IDs.

A real-world example

A B2B software company uses Oracle E-Business Suite for customer accounts, contracts, and invoicing, and runs Mailchimp for product announcement campaigns and customer newsletters. Before the integration, the marketing operations team manually exported customer contact lists from EBS every month and imported them into Mailchimp, a process that took hours and often missed recent additions and customer name changes. After new customers were added in EBS, marketing campaigns went to outdated contact information until the next manual sync. With Oracle E-Business Suite and Mailchimp connected, customer accounts added or modified in EBS flow to Mailchimp automatically on a daily schedule. New customers appear in the subscriber list within hours, and contact changes like name and email updates are reflected without manual intervention. The marketing team can now spend time on campaign content instead of list maintenance.

What you can do

• •Sync customer accounts and contact records from Oracle E-Business Suite to Mailchimp list members automatically on a schedule you define.
• •Map EBS customer name, email, phone, and custom attributes to Mailchimp profile fields.
• •Authenticate EBS with Basic Auth or token login and maintain session token refresh before timeout.
• •Extract the Mailchimp data center prefix from the API key and route calls to the correct regional endpoint.
• •Handle HTTP 429 rate limits with exponential backoff and retry until successful.

Questions

Which direction does data flow between Oracle E-Business Suite and Mailchimp?

Data flows one direction: from Oracle E-Business Suite into Mailchimp. ml-connector polls EBS for new and updated customer accounts and contacts, and upserts them as list members in Mailchimp. Mailchimp has no purchase orders, invoices, or GL accounts, so financial data remains in EBS.

How does ml-connector handle the ISG session token timeout in Oracle E-Business Suite?

ml-connector stores the EBS ISG hostname, port, and credentials encrypted and maintains an active session. It refreshes the access token before it expires (typically before 30-60 minutes elapse) and automatically re-authenticates on a 401 response without pausing the integration.

What custom attributes can be synced from EBS to Mailchimp?

Any customer attribute stored in the EBS HZ_CUST_ACCOUNTS and HZ_PARTIES tables can be mapped to a custom field in Mailchimp. Common attributes include customer type, status, industry, address, and phone. ml-connector stores the mappings encrypted so they persist across syncs without reconfiguration.