You can setup ServiceNow connector to Enterpret Agent in two parts:

Who	What	When
Your ServiceNow admin	Create a user for Enterpret and register an OAuth app	Once per organisation (one-time setup)
Each Enterpret user	Connect ServiceNow from the Enterpret UI	Once per person

The first person to connect needs a Client ID from the admin (or let the admin do it themselves). Everyone after that just needs the instance name (subdomain).

Part 1 — ServiceNow admin setup (one time, ~10 minutes)

Step 1: Create a ServiceNow user for Enterpret

Incidents are created by whoever is signed in. Create a dedicated user so automated incidents show up as Enterpret, not as a person on your team.

Go to User Administration → Users → New.

Fill in:
- User ID — for example enterpret.agent. This is what you sign in with later, and it is not the email address.
- First name / Last name — for example Enterpret / Agent.
- Email — any mailbox you control.
Click Submit.
Open the user you just created, scroll to Roles, click Edit, add the itil role (or any role that gives this user permission to read, create and update incidents), and save.
Also add sn_incident_write. Without it ServiceNow silently ignores the Urgency value, and incidents come out as Priority 4 instead of P1.
Back on the user record, click Set Password → Generate. Save the User ID and password in your password manager — you need them in Part 2.

itil is a broad role. If your security policy requires it, trim it down to just what is needed to create and update incidents.

Step 2: Register the Enterpret OAuth app

Go to System OAuth → Application Registry → New.

Choose OAuth - Authorization code grant.
Fill in:
- Name — Enterpret
- Provider name — Enterpret
- Client ID — leave it, ServiceNow generates one.
- Client Secret — leave blank. Enterpret uses a public (PKCE) client, so there is no secret to create, share, or store.
- Client Type — leave as -- None --.
- OAuth Application User — leave blank.
- Redirect URL — https://api-v2.enterpret.com/connectors/oauth/oauth/callback
You have two options:
1. Leave Auth Scopes empty and leave Scope Restriction on the broad option (no restrictions on the client layer).
2. Explicitly pick the list of scopes (permissions) that requests through this client have access to. More secure and restrictive.
Click Submit, then open the app and copy the Client ID.
Send the Client ID to whoever will connect first. It is not a secret.

Step 3: Check the fields you plan to write

ServiceNow accepts a create request and silently drops any field or choice value it does not recognise, so the incident looks successful but comes back incomplete.

Before going live, confirm that any custom field or choice value you want Enterpret to set (for example Channel / contact type, or a business application field) already exists on your instance.

Part 2 — Connect ServiceNow in Enterpret (~1 minute per person)

If you are the first person from your company

In Enterpret, go to Settings → Connectors → ServiceNow → Connect.
Your ServiceNow instance — enter the subdomain only. If your URL is acme.service-now.com, enter acme. No https://, no .service-now.com, no trailing slash.
OAuth client ID — paste the Client ID from your admin.
Sign in with a ServiceNow User ID and password, then approve the access request.
You are connected. The connector page will list the ServiceNow tools (16 of them) that the agent can now use.

Everyone after that

Same flow, but Enterpret only asks for the instance subdomain — the Client ID is already saved for your workspace. Sign in with your own ServiceNow account.

The account you sign in with matters. The connector acts as that ServiceNow user and inherits their permissions. Sign in as the Enterpret agent user if this connection will drive an automation; sign in as yourself for your own ad-hoc use. The connector page does not yet show which ServiceNow identity is connected, so make a note of which one you used.