📣 Connect automation rules with Workday using new authentication method

[#1]

Hi Atlassian Community! 👋

We’re excited to announce a new way to connect Automation rules to Workday using API client for integrations (2LO Authentication)! Using this authentication method, you can securely establish a connection between your automation rules and Workday, enabling system-to-system communication without requiring user intervention for authentication.

What’s New?

Previously, connecting to Workday using API Client (3LO) method required each user to log in with their own Workday account or use an Integrated System User (ISU). While secure, this connection is established on the user’s behalf, creating additional dependency and complicating the setup process. Now, with the API Client with Integrations (2LO) authentication, you can connect to Workday using a dedicated API client with no dependencies on individual user accounts.

Check out our documentation for how to get started.

Note that each automation rule maintains its own connection with Workday which is not shared or managed globally or at the project/instance level.

What are the Benefits?

This authentication method is designed for organisations with strict security requirements or those who wanted to avoid user-based connections.

• Security: No need to use real user accounts and authenticate in the browser.

• Config: Fewer steps to get started.

• Maintenance: No need to edit or change the connection if the integration owner changes.

API Client vs API Client with Integrations

API Client vs API Client with Integrations are two common authentication methods for connecting with Workday. API Client authentication enables user-consented access, allowing integrations to act on behalf of an individual user (real person or an ISU) within Workday. In contrast, API Client with Integrations uses system-to-system authentication that does not require explicit user consent. It relies on a refresh token and does not require user login or permission grants.

To switch to API Client authentication, select it from the dropdown and follow the prompts. Note that this connection requires logging into Workday with a user or ISU account.

Get Started

• Go to Automation in Jira Service Management and add a Workday trigger or action.

• Click “Connect” and choose API client for integrations (default option).

• Follow our documentation to complete the setup.

We want your feedback!

Have questions or want to share how you’re using the API Client vs API Client with Integrations authentication with Workday? Drop your thoughts in the comments below. Your feedback helps us shape future improvements.

Kind regards,
Michael Fedulov
Product Manager, Jira Service Management