Skip to main content
Feedback

Workday connection

The Workday connection represents a single Workday instance. You can use your user login credentials or OAuth2.0 to create a Workday connection.

You can use the same Workday connection to connect to difference services, and pair this connection with different Workday operations to perform a unique action against a Workday instance.

When you start to build your processes, you can set up your Workday connection to point to a sandbox instance by using that URL in the connection. When you are ready to run the processes in a production environment, you only need to change the connection’s URL to point to the production URL. When the process runs, it uses the new URL.

Connection tab

URL - The URL for the Workday service, such as https://<workday host name>.workday.com/ccx/service/<tenant name>/. The trailing ‘/’ is required. Configure the bracketed Workday host name and tenant name to successfully connect to the correct instance.

Version - The web service version including point releases, such as 23.2. You do not need to enter ‘v’ because Integration inserts it for you.

Authentication Type - The Workday connector now supports two authentication methods: Basic and OAuth 2.0.
Select the authentication type at the account level or for individual ports as required:

  • Basic – Use standard username and password authentication.
    • Username - The user name for logging into the Workday service with the format username@tenantname.
    • Password - The password for logging into the Workday service.
  • OAuth 2.0 – Use the authorization code grant support. For more information, refer to OAuth 2.0.

OAuth 2.0 tab

To authenticate with OAuth 2.0 authentication, enter:

  • The callback URL - https://platform.boomi.com/account/<your_account_ID>/oauth2/callback where <your_account_ID> is your Integration account ID.

    • You can also find your account ID in the Integration platform at Settings > {conKeyRefs.AccInfo} > Account Information.

The following fields appear when you select OAuth 2.0 to authenticate your Workday session.

  • Grant Type:
    • Authorization Code — The standard, 3–Legged OAuth2 authorization, where you grant the client an authorization code that can be exchanged for an access token.
  • Client ID - The client ID obtained from the application.
  • Client Secret - The client secret obtained from the application.
  • Scope - The external authorization service client application scope. The default is openid offline_access.
  • Access Token URL - The access token URL defined in auth provider.
  • Authorization Token URL (Authorization Code) - The endpoint URL used to obtain an authorization token.
  • Add Authorization Parameter (Authorization Code) - (Optional) The name and value of extensible endpoint parameters.
  • Generate (Authorization Code) - Click to generate the access and refresh tokens. When a new window opens asking you to confirm offline access, click Accept. A second message indicates the access token was received and successfully generated.

Test Connection

You can test your connection settings before you use or save the connection in a process. The Test Connection ensures that your specified settings are correct, valid, and accessible. If the test connection is successful, you can save the connection. Otherwise, review and correct any incorrect settings, then test again.

Attention

You can only run the Test Connection against containers associated with your account (local runtimes, runtime clusters, and runtime clouds).

On this Page