Workday Financial Management and Mailchimp integration

What moves between them

Customer and payment records flow from Workday into Mailchimp. Customer accounts from Workday's AR module are synced as e-commerce customers in Mailchimp, and Workday payment transactions are mapped to Mailchimp e-commerce orders with order totals and payment status. The sync is unidirectional; Mailchimp contacts and orders remain independent of Workday journal entries. ml-connector polls Workday on a daily or weekly schedule aligned with your financial close cycle, gathering customers modified since the last run and payments processed in the period.

How ml-connector handles it

ml-connector stores both Workday and Mailchimp credentials encrypted. For Workday it handles both OAuth2 token refresh (valid for one hour) and Integration System User authentication, choosing between SOAP and REST transport based on the entity being synced. It polls Workday using date-range filters to fetch new and modified customers and payments, then transforms customer records into Mailchimp e-commerce customer objects and payment transactions into order records, mapping Workday customer ID to Mailchimp customer ID. Payment amounts and status are preserved so Mailchimp campaigns can segment by customer spend and receivables status. For Mailchimp, it uses OAuth2 or API key auth and routes to the correct data center by extracting the DC prefix from the API key. Workday rate limiting and the minimum 5-minute polling floor are respected, and every record carries audit detail for replay if a downstream sync fails.

A real-world example

A B2B SaaS company runs Workday Financial Management for accounts receivable and customer accounting. The marketing team uses Mailchimp to send customer success, renewal, and upsell campaigns, but has no visibility into customer payment patterns or AR status. With Workday and Mailchimp connected, each customer's payment status and lifetime transaction total flows into Mailchimp as part of the customer record. The marketing team can now segment renewal campaigns by customers with recent large payments, flag dormant high-value accounts with past-due AR for special handling, and track which customer cohorts convert best. The sync removes manual exports from Workday and weekly imports into spreadsheets, and ensures every campaign sees current financial data.

What you can do

• •Sync Workday customer records to Mailchimp e-commerce customers with customer IDs and AR account details.
• •Map Workday payment transactions into Mailchimp e-commerce orders with order totals, payment status, and transaction date.
• •Refresh Workday OAuth2 tokens hourly and choose between SOAP and REST transport based on the entity.
• •Poll Workday on a schedule aligned with your financial close cycle, fetching new and modified records via date-range filters.
• •Audit every synced record with full detail and support replay if a downstream Mailchimp call fails.

Questions

Which direction does data flow between Workday Financial Management and Mailchimp?

Data flows one way, from Workday into Mailchimp. Workday customers and payments are synced to Mailchimp e-commerce customers and orders so marketing campaigns can segment by payment status and customer spend. Mailchimp contacts and orders remain independent of Workday and are not written back.

How does ml-connector handle Workday's OAuth2 tokens and SOAP/REST choice?

Workday access tokens expire after one hour, so ml-connector automatically refreshes them before each poll. It stores both OAuth2 and Integration System User credentials encrypted and chooses between SOAP and REST transport at sync time based on the entity being fetched, since SOAP supports a broader set of operations.

What is the minimum polling interval and why?

Workday recommends 15 to 60 minute intervals for transactional records, but the absolute minimum safe interval is 5 minutes to avoid triggering tenant-level rate throttling. ml-connector respects that floor and, combined with date-range filtering, pulls only new and modified records since the last sync.