Add a trigger to a journey

Every journey starts with a trigger which listens out for a specific event to occur. Once this event takes place, your journey will begin to run. The trigger for a journey will always be pre-set as when your chosen parent request type is created, although you can change this to be triggered by Workday using an Automation rule if desired.

Trigger a journey using Workday via Automation

Register an API client in Workday

1. Sign in to your Workday account.

2. In the search box at the top of the page, enter "Register API client".

3. Select Register API Client.

4. Complete the form. For more information, search for “Register API client” in the Workday community. Form field instructions:

   1. Client Grant Type: select Authorisation Code Grant

   2. Access Token Type: select Bearer

   3. Redirection URI: https://id.atlassian.com/outboundAuth/finish

   4. Non-Expiring Refresh Tokens: select Yes

   5. Scope (Functional Areas): search for and select Staffing

5. Select OK.

On the next screen, you will see all the details you need to connect Jira to Workday. You can access these details in Workday later but the “Client Secret” will only be shown once. We recommend you save this somewhere safe.

Set Workday as your trigger in a journey

1. In the journey you wish to add a Workday trigger to, select Edit on trigger.

2. Select the Worker added to Workday trigger as the event that causes the journey to run.

3. To retrieve the rule ID, select the template link provide to create an Automation rule.

   1. You’ll be taken to Automation where you can begin setting up your rule. This will include creating a connection with Workday.

Connect to Workday via Automation

Using the details you received when you registered the API client in Workday, you’ll be able to connect to Workday via the Automation template link provided.

1. Select the Worker added to Workday trigger and select Connect.

2. Complete the form with the details you received when you registered the API client in Workday.

3. Select Connect.

4. You will be taken to Workday for authorization.

   1. Sign in to Workday.

   2. When prompted to “Authorize Workday”, select Allow.

5. If you created the connection for a trigger, you need to create an API token and copy it into Workday.

   1. Select Generate API token. You will be taken to your Atlassian API tokens.

   2. Select Create API token.

   3. Give the token a label and select Create.

   4. Select Copy.

   5. In Workday, go to your integration system and in the External Endpoints section, paste your Webhook URL into the Notification URL field and your API token into the Notification Password field.

   6. Select OK.

Finish setting up Workday Automation rule

Once Workday has been connected, you’ll be able to retrieve data and use it in Jira. To retrieve worker details from Workday, you’ll need to access smart values and populate the Workday ID field with

1. Select the Retrieve worker details from Workday card.

2. Select the smart values icon { } to populate the Workday ID field.

3. Select Workday, then Workday - Worker details.

4. Copy the {{workday.worker.employeeID}} smart value and paste it in the Workday ID field.

5. Select the Create issue with a request type card.

6. Select the project and request type you wish to use as the parent issue the journey will be built upon.

7. Either manually enter values or use Workday smart values to populate the fields on the request type.

8. Select Turn on rule to enable it for the journey.

   1. This rule won’t be triggered until your journey is published.

9. Once your rule is enabled, it will produce a unique rule ID that can be found in the URL. Copy this number and navigate back to your journey.

10. Paste the ID into the Rule ID field and select Confirm.