Guides

Environments

Environments store Workday tenant URLs, credentials, variables, and execution settings for each target system.

Creating An Environment

An environment should represent a real target such as Sandbox, Preview, Production, or a customer-specific tenant. Credentials are encrypted at rest and masked in logs.

Environment configuration page
Environment settings with Workday credentials and variables.
1

Open Settings and choose Environments.

2

Create a new environment with a descriptive name.

3

Enter the Workday base URL and authorized username.

4

Store required secrets and variables.

5

Use a low-risk smoke case to verify login and navigation.

Variables

Variables keep tenant-specific details out of step code. Use them for URLs, organization names, common effective dates, default locations, or identifiers that change between tenants.

Practical Tips

  • Do not store passwords in plain variables if a secret field exists.
  • Keep variable names consistent across environments.
  • Review environment access before adding production credentials.

Validation Checklist

After creating or editing an environment, validate it with a harmless login or navigation case before running a workflow that changes Workday data.

1

Confirm the base URL opens in a browser.

2

Confirm the username belongs to the intended tenant.

3

Run a login smoke test.

4

Check MFA or device-trust behavior.

5

Run a read-only navigation or lookup case before write operations.

Troubleshooting

Environment failures often appear as login errors, tenant mismatch, missing variables, or permission errors inside Workday.

Practical Tips

  • If login fails for every case, verify credentials and MFA state.
  • If only one workflow fails, check required Workday permissions for that process.
  • If a step cannot find expected data, verify the environment variables used by that step.