Workday HR Spoke – OAuth 2.0 (refresh token) setup

[vi_araza]

Hi Community,

I’m setting up the Workday HR Spoke in ServiceNow and need help with configuring OAuth 2.0 using a refresh token.

Here’s what I have from Workday:

• Workday REST API Endpoint

• Token Endpoint

• Authorization Endpoint

• Client ID

• Client Secret

• Refresh Token

I’m able to successfully get an access token in Postman by passing the refresh token as a body parameter. However, I don’t see a way to configure this in ServiceNow.

• In the Application Registry / OAuth 2.0 Credential, there isn’t an option to manually provide the refresh token.

• I don’t want to do it via a scripted REST Message, because I need this token to be available to the OOTB Workday HR Spoke flow actions.

My questions:

1. How can we configure ServiceNow’s OAuth setup so it can use the refresh token I already have?

2. Is there a supported way to pass the refresh token (like in Postman) so that OOTB spoke actions can automatically pick up the access token?

3. Has anyone set up Workday REST integration with the spoke using refresh token flow successfully?

Thanks in advance for any guidance!

[Sandeep Rajput]

@vi_araza 

ServiceNow does not let you directly import/paste a refresh token into an OAuth profile (unlike Postman where you can drop it in and immediately use it).

Instead, ServiceNow maintains its own OAuth Entity Profiles (sys_auth_profile) which securely store:

1. Client ID & Secret
2. Auth / Token URLs
3. Scope
4. Grant type (Auth Code, Password, Client Credentials, etc.)

When you authenticate once (via OAuth setup in the profile), ServiceNow securely stores the refresh token and will automatically use it to obtain new access tokens as needed.

This is how IntegrationHub Spokes / OOTB actions can automatically pick up valid access tokens: they are linked to an OAuth Entity Profile, and the platform rotates tokens behind the scenes.