Workday Financial Management and Marketo integration

What moves between them

Customer and opportunity records flow from Workday into Marketo on a schedule aligned to your financial close cycle. When a customer is added or modified in Workday, the company record in Marketo is created or updated with address, billing contact, and credit status. When a journal entry is posted in Workday for a delivered invoice, ml-connector creates or closes the corresponding opportunity in Marketo as won, preserving the invoice amount and customer reference. Reference data like GL accounts and worktags can seed campaign taxonomy in Marketo. The primary flow is Workday to Marketo; invoices are read-only.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Workday ISU user password and the Marketo Client Secret. On the Workday side, it accepts either SOAP or REST transport per customer configuration, refreshing the REST OAuth2 access token as needed, and uses date-range filters on Workday's Get operations to poll customers and invoices on a schedule tied to your month-end or weekly close. On the Marketo side it exchanges the Munchkin ID and Client Secret for a Bearer token on each sync cycle, then queries Marketo companies and opportunities by updatedAt. Invoiced amounts are mapped to opportunity values, customer names to company names, and journal entry dates to opportunity close dates. ml-connector retries on Marketo batch limits (300 record maximum per request) and Workday polling throttle, and tracks every record in its audit trail so a failed downstream write can be inspected and replayed.

A real-world example

A mid-market B2B software company invoices from Workday and runs marketing pipeline in Marketo. Before the integration, the sales operations team manually exported Workday customer invoices each week, then logged into Marketo to mark opportunities as closed-won and update the company credit status. This process lagged by 2-3 days and required duplicate data entry. With Workday and Marketo connected, each posted invoice automatically creates a won opportunity in Marketo with the correct amount, and the customer company record updates with payment terms and status the moment they are recorded in Workday. Pipeline accuracy is now current to the hour, and there is no re-keying step.

What you can do

• •Sync customer and company records from Workday into Marketo with address, billing contact, and credit status on your close schedule.
• •Create and close opportunities in Marketo as won whenever a customer invoice is posted in Workday, mapped to invoice amount and date.
• •Authenticate Workday with ISU credentials over SOAP or OAuth2 refresh token over REST, and Marketo with Client Credentials OAuth2.
• •Poll Workday and Marketo on a schedule aligned to your financial close and pipeline review cycles, with automatic retry on batch and rate limits.
• •Maintain a complete audit trail of every customer, company, and opportunity record so failed syncs can be inspected and replayed without data loss.

Questions

Can we sync payment status or invoice detail from Workday to Marketo campaigns?

Yes. Workday's journal entries and supplier invoices can be mapped to Marketo custom objects or activity records to give sales teams visibility into what was actually invoiced and when payment is expected. This requires custom field setup in Marketo, but ml-connector handles the polling and the data format conversion.

What happens if Marketo's 300-record batch limit is hit during a sync?

ml-connector detects the batch limit response and automatically chunks the customer and opportunity batch into smaller requests, retrying until all records are written. The audit trail logs each chunk so you can track which batches succeeded.

How does the integration handle Workday's need for either SOAP or REST, and Marketo's polling-only support?

ml-connector accepts your choice of SOAP or REST on the Workday side per tenant configuration, refreshing OAuth2 access tokens as needed. Both systems are polling-only, so ml-connector syncs on a schedule you control, typically aligned to your financial close or weekly pipeline review, with no dependency on webhooks or real-time events.