Workday RaaS integration summary

Stitch’s Workday RaaS integration replicates data from your defined reports using the Workday RaaS Public Web Services API. For more information on this integration’s table creation, refer to the Schema section.

Workday RaaS feature snapshot

A high-level look at Stitch's Workday RaaS (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Beta

Supported by

Stitch

Stitch plan

Enterprise

API availability

Available

Singer GitHub repository

singer-io/tap-workday-raas

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Supported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Table-level reset

Unsupported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Connecting Workday RaaS

Workday RaaS setup requirements

To set up Workday RaaS in Stitch, you need:

  • An Enterprise Stitch plan. Workday RaaS integrations can be added on as part of an Enterprise plan. Reach out to Stitch support for more info.

Step 1: Retrieve your report URL

  1. Login to your Workday RaaS account.
  2. Navigate to your reports.
  3. Select the report you want to replicate and ensure that the Enable As Web Service box is checked.
  4. Copy the Workday XML REST link and keep it available for the next step.

    Workday XML REST link highlighted on the URLs Web Service page in Workday RaaS

To replicate multiple reports, repeat steps 3 and 4 as needed.

Step 2: Add Workday RaaS as a Stitch data source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Workday RaaS icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Workday RaaS” would create a schema called stitch_workday_raas in the destination. Note: Schema names cannot be changed after you save the integration.

  5. In the Username field, enter the username for your Workday RaaS account.
  6. In the Password field, enter the password for your Workday RaaS account.
  7. In the Report Name field, enter a name for the report. Note: This will be used to create the name of the corresponding destination table.
  8. In the Report URL field, enter the report URL you obtained in step 1.

To replicate additional reports, click Configure another report and repeat steps 6 and 7.

Step 3: Define the historical sync

The Sync Historical Data setting will define the starting date for your Workday RaaS integration. This means that data equal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Workday RaaS’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Workday RaaS integrations support the following replication scheduling methods:

To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Step 5: Set tables and columns to replicate

To complete the setup, you’ll need to select the tables and columns you want to replicate to your data warehouse.

Check out the Schema section to learn more about the available tables in Workday RaaS and how they replicate.

  1. In the list of tables that displays - or in the Tables to Replicate tab, if you skipped this step during setup - locate a table you want to replicate.
  2. To track a table, click the checkbox next to the table’s name. A green checkmark means the table is set to replicate.

  3. To track a column, click the checkbox next to the column’s name. A green checkmark means the column is set to replicate.

  4. Repeat this process for all the tables and columns you want to replicate.
  5. When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.

Note: If you change these settings while a replication job is still in progress, they will not be used until the next job starts.

Initial and historical replication jobs

After you finish setting up Workday RaaS, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Workday RaaS replication

Stitch uses Full Table Replication to replicate report data from Workday RaaS. This means that during every replication job, every report configured in the integration’s settings will be replicated in full.


Workday RaaS table schemas

Stitch’s Workday RaaS integration replicates data from existing reports in your Workday RaaS account. For every report you configure while setting up the integration, Stitch will create a corresponding table in your destination.

The fields available for selection are dependent on the data points that exist in the report in Workday RaaS. If you don’t see a field you want to select in Stitch, verify that the report in Workday RaaS contains the field.



Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.