Workday Financial Management and Zendesk integration

What moves between them

Supplier and invoice data flows from Workday Financial Management into Zendesk. ml-connector polls Workday on a schedule (typically 30-60 minutes) for active suppliers, recent invoices, and payments. The supplier name, status, contact details, and recent invoice count are synced into Zendesk organization records so the support team can see vendor context. When a ticket is created or updated mentioning a supplier or invoice, custom fields on the Zendesk ticket are populated with Workday financial details like PO reference, invoice amount, due date, and payment status. The integration is read-only from Workday; no financial records are written back.

How ml-connector handles it

ml-connector maintains separate credentials for Workday Financial Management and Zendesk, encrypting both at rest. On the Workday side, it uses the Integration System User (ISU) account and WS-Security credentials for SOAP reads of suppliers and invoices, or OAuth2 refresh-token for REST queries, switching between transport layers based on data complexity. It polls on a schedule tied to your AP/AR processes rather than relying on webhooks since Workday has no native event stream. On the Zendesk side, it uses OAuth2 or API token auth to write enriched data into organization records via PATCH and into ticket custom fields. Since Zendesk has no finance schema, the integration maps Workday supplier fields into Zendesk organization custom fields and invoice details into ticket custom fields using a configuration-driven mapper. ml-connector deduplicates by Workday supplier ID and invoice document ID so repeated reads do not create duplicate organizations or fields. Workday rate throttling is rare but returns 429 on heavy concurrent polling, so ml-connector backs off and retries; Zendesk API rate limits per official docs and ml-connector respects those limits on writes. Every record carries an audit trail of when it was synced and from which Workday source.

A real-world example

A mid-market manufacturing company uses Workday Financial Management for procurement and AP and Zendesk to manage vendor support tickets alongside customer tickets. When a supplier calls about an unpaid invoice or disputes a payment, the support agent opens a Zendesk ticket and sees the invoice amount, PO reference, due date, and payment status already populated from Workday without switching systems. The agent can resolve the ticket faster and respond accurately because the financial details are contextual. When a new supplier is added in Workday, it automatically appears as an organization in Zendesk so tickets can be linked to the right vendor record. The AP team spends less time on email threads asking support to look up invoice details, and support closes vendor tickets faster with better information.

What you can do

• •Sync active suppliers from Workday Financial Management into Zendesk organization records with vendor status and contact information.
• •Enrich Zendesk tickets with invoice amount, purchase order reference, due date, and payment status from Workday.
• •Map recent invoices and payments from Workday to Zendesk ticket custom fields for visibility without manual lookup.
• •Authenticate Workday via ISU account and WS-Security or OAuth2 refresh-token, and Zendesk via OAuth2 or API token.
• •Poll Workday on a configurable schedule tied to your AP/AR cycle with full audit trail on every supplier and invoice sync.

Questions

Which direction does data move between Workday Financial Management and Zendesk?

Data flows from Workday Financial Management into Zendesk. Supplier records, invoices, and payment status are read from Workday and synced into Zendesk organization records and ticket custom fields. The integration is read-only from Workday; no financial records are written back to Workday from Zendesk.

Why does ml-connector poll Workday instead of using webhooks?

Workday Financial Management has no native webhooks or event stream for financial entities. Instead, ml-connector polls suppliers and invoices on a 30-60 minute schedule aligned with your AP/AR cycle. Outbound Messaging can be enabled in Workday if you need real-time push, but polling is the standard approach.

How does ml-connector handle Workday's SOAP and REST APIs?

ml-connector uses the SOAP API at https://{hostname}.myworkday.com/ccx/service/{tenant}/Financial_Management/v46.1 for complex reads of invoices and suppliers because REST v46.1 has narrower breadth. It authenticates with the Integration System User (ISU) account and WS-Security UsernameToken, maintaining the credentials encrypted. On the Zendesk side, it uses OAuth2 or API token to write enriched data into organization and ticket custom fields without touching Workday financial records.