# Connect ServiceNow to EasyMorph **URL:** \ **Category:** Articles\ **Created:** [October 12, 2026, 9:39am UTC](https://community.easymorph.com/t/connect-servicenow-to-easymorph/6815 "2026-10-12T09:39:57Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![roberto](https://community.easymorph.com/user_avatar/community.easymorph.com/roberto/32/8595_2.png) [@roberto](https://community.easymorph.com/u/roberto)\ **Post date:** [October 12, 2026, 9:39am UTC](https://community.easymorph.com/t/connect-servicenow-to-easymorph/6815/1 "2026-10-12T09:39:57Z")
# Connect ServiceNow to EasyMorph This guide explains how to register a ServiceNow OAuth application for EasyMorph and configure the connector. It also covers Basic authentication as an alternative. This feature is available starting from version `6.2.0`. ## OAuth2: Authorization Code With this method, you register an application in your ServiceNow instance, then sign in through the browser to authorize EasyMorph. ### 1. Create an OAuth application in ServiceNow 1. Sign in to your ServiceNow instance with an administrator account that can manage OAuth integrations. 2. Open **Inbound integrations** under **System OAuth** or **Machine Identity Console** , depending on your ServiceNow version. 3. Select **New integration** , then **OAuth - Authorization code grant**. 4. Complete the application settings: | Setting | Value | | --- | --- | | Name | `EasyMorph` | | Provider name, if requested | `EasyMorph` | | Client ID | Keep the generated value. | | Client Secret | Keep the generated value. | | Redirect URL | `http://localhost:1234` | | Active | Enabled | The form may vary by ServiceNow version. See [ServiceNow's authorization code setup instructions](https://www.servicenow.com/docs/r/platform-security/authentication/configure-an-oauth-authorization-code-grant.html). > **Redirect URL:** Use exactly `http://localhost:1234`, without a trailing slash. This matches the default redirect URI used by EasyMorph. ### 2. Configure API scopes You can assign specific API scopes to the application or use the broader `useraccount` scope, depending on your instance's configuration. **Specific API scopes** In the application's scopes section, create or select scopes and associate them with the APIs used by EasyMorph: | Example scope name | API | | --- | --- | | `easymorph_table_api` | Table API | | `easymorph_batch_api` | Batch API, which may appear as Table Batch API | These scope names are examples; use the names configured in your instance. Assign the scopes to the OAuth application and enter those same names in EasyMorph. Creating a scope name alone does not link it to an API. See [ServiceNow's REST API Auth Scope documentation](https://www.servicenow.com/docs/r/platform-security/authentication/rest-api-auth-scope.html). **Broader access with `useraccount`** Alternatively, associate the built-in `useraccount` scope with the application. This scope is not limited to the two APIs above; access to data still depends on the signed-in user's permissions. See [ServiceNow's scope behavior](https://www.servicenow.com/docs/r/platform-security/authentication/rest-api-auth-scope.html). Save the application and copy its **Client ID** and **Client Secret** for the next step. ### 3. Configure and authorize the EasyMorph connector Create or open a **ServiceNow** connector in EasyMorph and enter: | EasyMorph setting | Value | | --- | --- | | Authentication Type | **OAuth2** | | Instance URL | `https://your-instance.service-now.com` | | Client ID | The Client ID from your ServiceNow application. | | Client Secret | The Client Secret from your ServiceNow application. | | Permission scopes | The scopes assigned in step 2, entered separately, or `useraccount` if configured. | If you leave **Permission scopes** empty, EasyMorph does not request explicit scopes. Use this option only when your ServiceNow application's default scope configuration provides the required access; do not assume that every instance defaults to `useraccount`. Authorize the connector, complete the ServiceNow sign-in and consent prompts in your browser, then test the connection and save the connector. ## Basic authentication Basic authentication uses a ServiceNow username and password. It does not require an OAuth application. 1. Make sure the ServiceNow account is permitted to use Basic authentication and has access to the required tables. 2. If the instance enforces Basic authentication restrictions, ask its administrator to confirm the account's access. The `snc_basic_auth_api_access` role is one supported exception; a **Web service access only** account is another. See [ServiceNow's Basic authentication restrictions](https://www.servicenow.com/docs/r/platform-security/authentication/basic-auth-restriction.html). 3. Configure the EasyMorph connector: | EasyMorph setting | Value | | --- | --- | | Authentication Type | **Basic** | | Instance URL | `https://your-instance.service-now.com` | | Username | The ServiceNow account's username. | | Password | The ServiceNow account's password. | 1. Test the connection and save the connector. ---
**Author:** ![andrew.rybka](https://community.easymorph.com/user_avatar/community.easymorph.com/andrew.rybka/32/13_2.png) [@andrew.rybka](https://community.easymorph.com/u/andrew.rybka)\ **Post date:** [October 12, 2026, 10:21pm UTC](https://community.easymorph.com/t/connect-servicenow-to-easymorph/6815/2 "2026-10-12T22:21:51Z")