Since ServiceNow requires OAuth configuration in your instance, you need to manually configure two OAuth apps in your ServiceNow instance to grant access tokens and authenticate requests to the REST API.Please follow the steps below to set up the required OAuth applications.
Create External Client OAuth App
1
Access ServiceNow Developer Portal
Sign into your ServiceNow Developer Portal account to create or access an instance.
2
Navigate to Application Registry
Go to System OAuth > Application Registry.

3
Create New Application
Create a new app by selecting New in the top right corner.

4
Select OAuth API Endpoint
Choose Create an OAuth API endpoint for external clients.

5
Configure Application Settings
Name your app
Pipedream. Use the default settings but specify the Redirect URL:6
Create and Verify
Click Create. The app will appear in the Application Registry once created.

Create OAuth Validator App
1
Copy Credentials
Copy the client ID and secret from the
Pipedream app you created above.2
Create OAuth Provider App
Go back to System OAuth > Application Registry > New and select Connect to an OAuth Provider (simplified).
3
Configure Validator Settings
Name this app
Pipedream OAuth Validator and add the previously copied client ID and secret.4
Set Authorization Details
Set the grant type to Authorization Code and the Token URL to
oauth_token.do.5
Add Redirect URL
Use the same Redirect URL as before:
Connect to Pipedream
1
Access Pipedream Accounts
Visit Pipedream’s account page, and click Click Here to Connect An App.
2
Search for ServiceNow
Search for ServiceNow and select it.
3
Enter Connection Details
Enter the client ID, client secret, and your instance name (e.g.,
dev98042 from https://dev98042.service-now.com/).4
Authorize Connection
Press Connect. A new window will prompt you to login to your ServiceNow instance, authorizing Pipedream’s access to the ServiceNow REST API.
Troubleshooting
For Hardened or Mature Instances: The standard instructions may not apply perfectly to customized or hardened ServiceNow instances. If you face a 504 Gateway Time-out error or similar issues, consider these additional steps:
- Assign a dedicated role and service account for this integration
- Ensure the role has ACLs configured for the
oauth_credentialtable and other necessary tables