ml-connector
Workday Financial ManagementTableau

Workday Financial Management and Tableau integration

Workday Financial Management and Tableau work well together when your accounting data flows into your dashboards automatically. Tableau surfaces procurement, payables, and ledger activity in real-time without manual export-and-upload cycles. Workday Financial Management holds the source of truth for suppliers, invoices, purchase orders, and general ledger activity, while Tableau turns those records into dashboards and reports that finance teams and executives use for visibility and decision-making. ml-connector bridges the two, moving financial records on a schedule you set.

How Workday Financial Management works

Workday Financial Management exposes suppliers, supplier invoices, purchase orders, GL accounts, worktags, customers, payments, and journal entries through two API surfaces: SOAP at https://{hostname}.myworkday.com/ccx/service/{tenant}/Financial_Management/v46.1 with WS-Security UsernameToken authentication, and REST at https://{hostname}.workday.com/ccx/api/v1/{tenant}/ with OAuth2 refresh-token flow. Complex financial operations such as journal submission and bulk invoice creation require SOAP, while simpler queries run on REST. Workday Financial Management has no native webhooks for data changes, so ml-connector polls on a schedule you control, querying GL accounts, invoices, and payments with date-range filters.

How Tableau works

Tableau is a REST API-driven analytics platform available as Tableau Cloud (SaaS) and Tableau Server (self-hosted). It manages workbooks, data sources, views, users, and extract refresh schedules through REST endpoints at https://{pod}.online.tableau.com/api/{version}/ on Cloud or https://{your-server}/api/{version}/ on Server. Authentication uses Personal Access Token (PAT) exchanged for a session token lasting 240 minutes by default, or a Connected App with JWT. Tableau data sources are how dashboards and views consume external data, and ml-connector pushes financial records into Tableau data sources to keep them current. Views are read-only derived objects, so ml-connector publishes data into reusable data sources that views then query.

What moves between them

Financial records flow from Workday Financial Management into Tableau. ml-connector polls GL accounts, supplier invoices, purchase orders, and payments from Workday Financial Management at intervals you define (typically 15 minutes to 1 hour for transactional data), transforms them to match your Tableau data source schema, and publishes them into Tableau data sources via the REST extract API. Workbook and dashboard views then query those refreshed data sources, so your finance dashboards show current payables, procurement status, and ledger activity without manual intervention. The flow is read-only into Tableau; ml-connector does not write back to Workday Financial Management.

How ml-connector handles it

ml-connector handles the different authentication models on each side. On the Workday Financial Management side, it uses either the SOAP WS-Security UsernameToken (for complex operations) or the REST OAuth2 refresh-token flow (for lighter reads), and it respects Workday's polling limits by spacing requests at least 5 minutes apart to avoid tenant-level rate throttling. On the Tableau side, it exchanges a Personal Access Token for a session token valid for 240 minutes, refreshing the token before expiry. Because Workday Financial Management offers no webhooks, ml-connector polls on a schedule tied to your business cycle - typical intervals are every 15 minutes for invoices and payments, daily for suppliers and GL account masters. It transforms Workday entities (GL accounts, invoice line items, purchase order headers) into rows that Tableau data sources expect, batches them into efficient extract uploads, and tracks which records have already been sent to avoid duplicates. If a Tableau refresh fails, it retries with exponential backoff and maintains an audit log so you can see exactly which records moved and when.

A real-world example

A mid-market financial services firm runs Workday Financial Management for AP, AR, procurement, and accounting. The finance team builds Tableau dashboards to track cash outflows, supplier spending by category, and monthly close metrics for executives. Before the integration, the accounting team exported GL and invoice data from Workday manually each week and imported it into Tableau data sources by hand, a process prone to stale data and human error. With Workday Financial Management and Tableau connected, invoices, PO activity, and GL summaries flow into Tableau automatically on a 15-minute schedule. Finance dashboards now refresh throughout the day, showing real-time payables aging, supplier concentration, and spend trends. Month-end close no longer waits for manual data pulls.

What you can do

  • Sync GL accounts, suppliers, and customer master data from Workday Financial Management into Tableau on a schedule you control.
  • Publish supplier invoices, purchase orders, and payment records into Tableau data sources so financial dashboards reflect current payables and procurement status.
  • Map Workday Financial Management entities (GL accounts, worktags, cost centers from invoice line items) to Tableau data source columns, transforming SOAP or REST responses into extract-ready rows.
  • Authenticate Workday Financial Management with OAuth2 or WS-Security credentials and Tableau with Personal Access Token, managing token expiry and refresh automatically.
  • Poll Workday Financial Management at safe intervals that respect tenant-level rate limits, with retries and a complete audit trail on every record pushed to Tableau.

Questions

Which direction does data move between Workday Financial Management and Tableau?
Data flows from Workday Financial Management into Tableau only. GL accounts, suppliers, invoices, purchase orders, and payments are read from Workday Financial Management and published into Tableau data sources so dashboards and views reflect current financial activity. ml-connector does not write back to Workday Financial Management; Tableau views are also read-only, so all updates originate from Workday Financial Management.
How does ml-connector handle Workday Financial Management's lack of native webhooks?
ml-connector polls Workday Financial Management on a schedule you define, using date-range filters to fetch new or modified records since the last poll. Typical intervals are 15 minutes to 1 hour for transactional data like invoices and payments, daily for master data like suppliers and GL accounts. ml-connector respects Workday's minimum safe polling interval of 5 minutes per tenant to avoid triggering rate throttling.
What authentication does ml-connector use for each system?
For Workday Financial Management, ml-connector uses either SOAP WS-Security UsernameToken (for complex financial operations) or REST OAuth2 refresh-token flow (for simpler queries), based on which API surface the operation requires. For Tableau, it exchanges a Personal Access Token for a session token valid for 240 minutes and refreshes the token automatically before expiry, supporting both Tableau Cloud and Tableau Server deployments.

Related integrations

Connect Workday Financial Management and Tableau

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started