Connector
Workday Connector
Bring Workday HR data into your ERP or CRM without writing code, and add new Workday fields yourself when your reports change.
Rapidi connects to Workday through a standard REST web service, paired with a JSON schema that describes the fields in your Workday reports. Workday is the source: employee records, positions and reporting lines move into an ERP or CRM such as Microsoft Dynamics 365. When a report gains a field, you update the schema, with no code change.
- What it connects to
- Workday, through any Workday REST endpoint you expose, with Workday reports as the common choice.
- Which way the data moves
- One way. Workday is the source, and HR data moves from it into your ERP or CRM.
- What you need
- A Workday integration system user with access to the endpoints, and a hosted JSON schema describing them.
What does this connector actually do?
The short version: Workday exposes a report or endpoint over REST, a JSON schema tells Rapidi which fields it holds, and you map those fields into the target system.
| What it syncs | HR data: employee master data, positions and the organisational hierarchy. The most common set is employees, positions, worker assignments and reporting lines. |
|---|---|
| Direction | One way, from Workday. Workday is the source system, and its report output is read-only. |
| How it connects | A standard REST web service pointed at a Workday endpoint, plus a Metadata URL that points to the JSON schema describing the fields. |
| What it can point at | Any Workday REST endpoint you choose to expose. Workday reports (RaaS) are a common choice because your team can build and adjust them, but other Workday tables and endpoints work the same way. |
| How it signs in | Usually basic authentication, with the user ID and password of a Workday integration system user. SSL is always enabled. |
| How often it runs | On a schedule you set. The shortest interval depends on your plan, from one hour on Entry down to one minute on Unlimited. |
| What you set up once | A Workday integration system user with access to the endpoints, the endpoint URL and credentials in MyRapidi, and a hosted JSON schema. |
How does the Workday schema work?
Workday customers add custom fields to their reports over time, such as a new cost center attribute or a new custom ID. If the field mappings were hardcoded, every one of those changes would need a developer. Instead, a JSON schema acts as a live contract: once the schema says a field exists, it is available to map.
- Your Workday admin adds a new field to the relevant custom report in Workday.
- A matching field definition goes into the JSON schema, with its name, description, type, format and an example value.
- The schema is saved back to where it is hosted, the address in the connection's Metadata URL.
- On its next read of the schema, the integration picks up the new field, ready to map. No code change, no new release, no ticket to Rapidi.
There is one schema per Workday tenant, with a definition for every endpoint in use, so the whole integration runs through a single REST web service connection. The schema is typically hosted as a static JSON file, for example on GitHub Pages, which keeps it version-controlled and easy for your technical team to edit. The one rule is that it stays in step with the real report output: a field removed from the report but left in the schema, or the other way round, makes mapping fail or return unexpected results.
What does a typical Workday integration move?
The most common pattern so far syncs employee master data, positions and the reporting hierarchy from Workday into Microsoft Dynamics 365, with Workday as the system of record for HR. It uses four report-based objects.
| Object | What it holds | Typical fields |
|---|---|---|
| Employee | The core employee record | Employee ID, company, cost center, hire date, preferred name, work email, active status and termination date |
| Position | Detail for the employee's current role | Position ID, business title, management level, effective date of the current position, most recent position change |
| Worker assignment | Which worker fills which position, over time | Employee ID, position ID, the date the position was filled, last update |
| Position hierarchy | The reporting and management lines | Position ID, the manager's position ID, hierarchy type, and valid-from and valid-to dates that keep the history |
Together they cover active and inactive employees, where each person sits in the company and cost centers, their current position and title, and the manager hierarchy with its history. The same four shapes apply when the target is Salesforce, HubSpot or another ERP. Only the report names and a few target-specific fields change.
Where can Workday data go?
Every Rapidi integration with Workday on one side runs through this connection. These are target systems Rapidi already connects to.
ERP connector
Dynamics 365 Finance and Operations
Microsoft Dynamics 365 is the most common target for Workday employee data so far.
ERP and Accounting
ERP connector
Dynamics 365 Business Central
Another Dynamics 365 ERP Rapidi connects to, in the cloud or on your own server.
ERP and Accounting
CRM connector
Salesforce
The employee, position and hierarchy pattern applies here too.
CRM
CRM connector
HubSpot
Another CRM target the same four-object pattern fits.
CRM
Where do you go next?
Connectors
Every system Rapidi connects to
The full connector list, from Dynamics and Salesforce to SQL Server, Oracle and plain REST.
All connectors
Connector
REST Web Service
The generic REST connection the Workday connector is built on, for any system with a REST API.
APIs and Protocols
Pricing
What Rapidi costs
Four plans, priced per subscription rather than per connector. Adding Workday does not change the licence.
Plans
Your setup
Ask about your own Workday
Tell us which Workday data you need and where it has to go, and we will say plainly how Rapidi covers it.
Talk to a consultant
Frequently asked questions
Can Rapidi connect to Workday?
Yes. Rapidi reaches Workday through its standard REST web service connection, the same generic REST connection type it uses for other REST-based systems, together with a JSON schema that describes the objects and fields available for mapping.
Which way does the data move?
Workday is the source. Rapidi reads Workday report output, which is read-only, and moves it into the target system, most commonly an ERP or CRM such as Microsoft Dynamics 365.
What happens when we add a field in Workday?
Your Workday admin adds the field to the report, and a matching field definition is added to the JSON schema and saved to where the schema is hosted. The integration picks up the new field on its next read of the schema, with no code change, no new release and no ticket to Rapidi.
Who builds and maintains the schema?
Rapidi builds the schema, and your team can extend it without development work. The schema has to stay in step with the real report output, so keeping it current is a shared discipline rather than a one-time setup step.
What does Rapidi need from our Workday?
A Workday integration system user with access to the endpoints being connected, those endpoints reachable over HTTPS, and a hosted, reachable JSON schema that describes them.
Do we need a separate connection for each Workday report?
No. There is one schema per Workday tenant, with a definition for every endpoint in use, so the whole integration runs through a single REST web service connection.
How often does the data move?
On a schedule you set. The shortest interval comes from your plan, from one hour on Entry down to one minute on Unlimited.
What does the Workday connector cost?
Nothing on its own. Rapidi is priced per subscription plan rather than per connector, so adding Workday does not change the licence.
Is Workday one of your systems?
Tell us which Workday data you need and which system it has to reach, and we will tell you plainly what the setup involves.