Workday Financial Management and Slack integration

What moves between them

Data flows from Workday Financial Management into Slack. ml-connector polls Workday Financial Management for supplier invoices, payments, and GL journal entries at intervals tied to your business process (hourly for transactional events, daily for reference entities), and formats each into a Slack message summarizing the key fields - invoice number, amount, supplier, GL account, approval status, due date. These messages post to channel subscriptions you control (e.g. Finance Alerts for high-value invoices, Approvals for payment runs, Reconciliation for GL discrepancies). Workday Financial Management is read-only from Slack; ml-connector never writes back into Workday Financial Management from Slack messages.

How ml-connector handles it

ml-connector stores the Workday Financial Management Integration System User credentials encrypted and exchanges the OAuth2 refresh token for access tokens at startup and on 401 responses, keeping SOAP and REST requests authenticated. On the Slack side it uses the OAuth2 bot token to call chat.postMessage, respecting the one-per-second rate limit per channel by queuing messages and spacing sends. Polling windows are tuned to your business - hourly for transactional entities (invoices, payments) and daily for slower-moving reference data (suppliers, GL accounts) - with date-range filters to avoid duplicates. Because Workday Financial Management has no change-data-capture, ml-connector tracks the last poll time and requests only records modified after that point, reducing API load. Every poll cycle is audited with the timestamp, records retrieved, and messages posted to Slack, so replays are possible if downstream Slack delivery fails. SOAP calls are retried with exponential backoff on transient errors, and the integration alerts your team via Slack when Workday Financial Management polling falls behind schedule.

A real-world example

A mid-sized financial services firm manages vendor payments and intercompany journal entries through Workday Financial Management across three business units, with approvals required at the group finance level. Before the integration, the finance director monitored invoices by logging into Workday Financial Management each morning and reviewing the GL aging report manually, then emailing approvals to the accounting team, which manually keyed approvals back into Workday Financial Management. With Workday Financial Management and Slack connected, high-value supplier invoices post automatically to a Finance Alerts channel the moment they arrive, GL month-end discrepancies surface in the Reconciliation channel with details, and payment approval summaries post after each run. The director approves invoices in Slack (triggering a downstream flow to update Workday Financial Management status), month-end reconciliation starts with accurate numbers already queried from Workday Financial Management, and the email-based approval loop is gone.

What you can do

• •Post supplier invoices, payments, and GL journal entries from Workday Financial Management to Slack channels on a schedule tied to your business process.
• •Summarize invoice amounts, suppliers, GL accounts, approval status, and due dates in Slack messages for fast review without logging into Workday Financial Management.
• •Deliver financial alerts to channel subscriptions you control - high-value invoices, overdue payments, GL reconciliation discrepancies - in real time.
• •Authenticate Workday Financial Management using SOAP WS-Security UsernameToken or REST OAuth2, and Slack using OAuth2 bot tokens, with encrypted credential storage.
• •Track every poll cycle with a full audit trail, including timestamp, records retrieved, and Slack messages posted, for compliance and replay.

Questions

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

Data flows from Workday Financial Management into Slack. ml-connector polls Workday Financial Management for invoices, payments, and GL entries and posts summaries to Slack channels. Slack is write-only for notifications; ml-connector does not write financial data back into Workday Financial Management from Slack.

How does ml-connector handle Workday Financial Management's lack of webhooks?

ml-connector polls Workday Financial Management using date-range filters at intervals you control (5 minutes to 60 minutes depending on entity type and rate-limit tolerance), with the last poll time tracked to avoid duplicates. Polling windows are tuned to your business - hourly for transactional entities like invoices and daily for reference data like suppliers - so the integration stays in sync without relying on native webhooks.

What are the authentication requirements for both Slack and Workday Financial Management?

Workday Financial Management requires an Integration System User account with WS-Security UsernameToken for SOAP calls or an OAuth2 refresh token for REST calls, both supplied by your tenant admin. Slack requires an OAuth2 bot token generated via the Slack app workspace, which gives ml-connector permission to post messages to channels you authorize. ml-connector stores all credentials encrypted and rotates tokens as needed.