Faster delivery
Ship integrations weeks faster with visual orchestration.
Workday Connector
Build native Workday integrations inside your product to sync employee and finance data, automate onboarding and payroll exports, and expose governed actions as MCP tools using Cyclr’s low-code orchestration and reusable templates.
Reusable templates
Publish standardized integration templates for customers to deploy.
Governed MCP tooling
Expose selected methods as controlled MCP tools to customers.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Cyclr’s Workday connector lets B2B SaaS teams build customer-facing, reusable integrations that connect to Workday REST and SOAP endpoints. Use visual orchestration, templates and policy-driven MCP tooling to embed HR and finance workflows in your UI, handle tenant-specific endpoints, and deploy governed integrations at scale.
PRODUCT USE CASES
Top Use Cases for Workday Integrations
Design, build and test reusable Workday automations in minutes with Cyclr’s workflow builder. Publish templates and customer-specific integrations to your SaaS UI, then manage them centrally with versioning, access control and audit trails.
Employee record synchronization
Automatically sync hires, terminations and profile changes from Workday to your application to keep user accounts current.
Automated user provisioning
Provision accounts, assign roles and update access based on Workday job and org changes.
Payroll and reporting exports
Extract payroll and finance reports or push payroll notifications to downstream payroll systems or vendors.
ORCHESTRATION
How Workday works with Cyclr
Cyclr sits between your SaaS product and Workday to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Workday
Workday processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Workday methods you can orchestrate through Cyclr.
Reports2
Get Report
ActionGet a report in JSON.
Get CSV Report (Plain Text)
ActionGet a CSV report as plain text.
Common1
List Inbox Tasks by User
ActionRetrieves a list of all Inbox Tasks for the selected User ID.
Recruiting1
List Job Postings
ActionRetrieves all job postings.
TECHNICAL DETAILS
Workday integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Workday integrations in Cyclr.
API and authentication
- API host
Tenant-specific Workday base URL and regional API gateway (examples provided in tenant REST API Explorer).- Authentication
- OAuth 2.0 and WS-Security/ISU
- Credentials
Tenant base URL, OAuth client ID and secret or ISU username and password, optional API gateway region.
- Method categories
Workers, Organizations, Payroll, Reports (RaaS), Business processes, Attachments, Graph API endpoints.
Pagination and rate limits
Pagination
REST uses offset-based pagination with limit and offset; Graph API default page 20, max 100; SOAP supports paged Get with response filters.
Rate limits
Workday applies tenant-level throttling and returns 429 on overload. Implement exponential backoff, caching and pagination; numeric limits are not publicly published.
IMPLEMENTATION
Authentication at a glance
Workday REST uses OAuth 2.0 API clients; SOAP/Web Services use WS-Security with an Integration System User (ISU). Tenant allowlisting and proper scopes are required.
- Authentication method
- OAuth 2.0 and WS-Security/ISU
- Credential required
Tenant base URL, OAuth client ID and secret or ISU username and password, optional API gateway region.
Before you begin:
View setup guideWorkday tenants require admin privileges to create API clients and configure ISUs and allowlists.
COMMON QUESTIONS
Frequently asked questions
Cyclr supports both Workday REST endpoints (modern JSON-based APIs and Graph) and the traditional SOAP Workday Web Services. Use REST where available for user-initiated flows and SOAP for legacy or bulk operations.
For REST you register an API client in the customer’s tenant and supply client ID and secret; for SOAP provide an Integration System User (ISU) with WS-Security credentials and required domain permissions.
Workday does not offer universal webhooks. Some modules provide Notifications or Events REST endpoints; otherwise scheduled RaaS/report polling is commonly used for near-real-time updates.
Design for tenant-level throttling: paginate all list calls, implement exponential backoff on 429 responses and cache results to reduce repeat queries.
KEEP EXPLORING
Related resources and connectors
Documentation
Key Enterprise Integration Considerations: Data Processing and Compliance
Read more →ProductCRM Integrations you should be using
Read more →ProductMCP PaaS
Read more →Related connectorExact
Related ERP connector for customer-facing integration workflows.
Related connectorNew Connector Request
Related ERP connector for customer-facing integration workflows.
Related connectorSage 200
Related ERP connector for customer-facing integration workflows.