Skip to main content

About ServiceNow

The TruU Identity Verification app lets help desk agents verify a caller from the record they are already working, before a password reset, MFA reset, or account recovery. The agent chooses Verify Identity, TruU sends the caller a verification link, and progress and the final result come back to the record as work notes. This connector starts verifications, both for agents working a record and for employees through your own catalog items (see Self-service with Flow Designer). The app is a scoped application (x_truu_idv). It adds:
ServiceNow Interaction record with the Verify identity dialog open, showing Send to, Delivery method set to email, and a Reason field, with TruU work notes on the right

An agent chooses Verify Identity on an Interaction. The link goes to the contact on file, and progress comes back as work notes.

  • A Verify Identity action on Incident, Interaction, and Requested Item records.
  • A Verification Requests list.
  • A TruU: Verify Identity and Wait subflow and a TruU: Create Verification Request action for Flow Designer.
  • Privacy Policy and Contact Support links in the app menu.
  • Three roles for people, plus an integration role that Connect assigns to the app’s own integration user.

Prerequisites

  • ServiceNow: ITSM with Incident, Interaction Management, or Service Catalog, depending on the records you want the action on.
  • TruU: an Owner or Admin seat, a connected directory (Entra ID or Okta), and email or SMS delivery for the people agents will verify.
  • Network: see Network. No MID Server is needed.

Install and assign roles

1

Get the app

Email idv@truu.ai for the TruU Identity Verification update set (XML), then load, preview and commit it in your instance under System Update Sets → Retrieved Update Sets.
2

Assign roles

The app also ships x_truu_idv.integration. Connect assigns it to the app’s integration user (see How TruU authenticates to your instance). Don’t assign it to people.

Connect to TruU

ServiceNow connector page with the ServiceNow tenant field, Generate connect link, and the Prefer manual setup stepsServiceNow connector page with the ServiceNow tenant field, Generate connect link, and the Prefer manual setup steps
You do not copy credentials by hand. A one-time connect link sets up the connection in both directions.
1

Generate a connect link

In the IDV Console, go to Settings → Connectors → ServiceNow, enter your ServiceNow tenant (the subdomain of your instance URL, for example dev123123), and choose Generate connect link. The link works once and expires after 15 minutes.
2

Open it in your instance

Open the link while signed in to your instance with the x_truu_idv.admin role. It opens the app’s Connect to TruU page with the linking code filled in.
3

Connect

Accept the TruU Terms of Service and Privacy Statement, then select Connect. The page does not connect until you do. Connect:
  1. Creates a web-service-only user, truu.idv.integration, with the x_truu_idv.integration role.
  2. Creates an OAuth client named TruU Identity Verification that runs as that user, with a new random secret. On a reconnect, it replaces the previous client only once TruU has accepted the new one.
  3. Checks that your instance issues a client-credentials token to that client, before the linking code is used.
  4. Sends TruU the OAuth client ID and secret, and stores the TruU API key in an encrypted property that only x_truu_idv.admin can read or change.
Nothing is shown to you or copied by hand. The Verify Identity action appears once the connection is complete.
One time per instance: turn on OAuth client credentials. ServiceNow turns the client-credentials grant off by default. If it is off, Connect stops before it uses the linking code and shows Open the property to turn it on. That opens a new system property, glide.oauth.inbound.client.credential.grant_type.enabled, already set to true. Save it, return to the Connect page and select Connect again. The setting only affects OAuth clients configured for client credentials. See ServiceNow’s Client Credentials documentation.
Connect from the Global application. The OAuth client is a Global record, and ServiceNow won’t save it while the application picker is set to a scoped app. Connect tells you if this happens.
If you aren’t the ServiceNow admin, send them the connect link. They open it while signed in with the x_truu_idv.admin role and select Connect. The link still works once and expires after 15 minutes.
To replace the app’s credentials at any time, generate a new connect link and connect again. Connecting again reuses the integration user and creates a new OAuth client. Only after TruU accepts the new client does the app delete the previous one, which revokes what TruU held before. If the attempt fails (for example, the code expired), the existing connection keeps working. The connection stays tied to the instance it was made from: TruU won’t send its OAuth credentials anywhere else, and the events endpoint can’t be moved to another instance in the console. To move to a different instance, connect from that instance with a new connect link.

How TruU authenticates to your instance

The app’s events endpoint, /api/x_truu_idv/truu_idv/events, is not public. ServiceNow accepts a call to it only when it is authenticated and the caller holds x_truu_idv.integration.
  • TruU to your instance: TruU requests an access token from your instance’s /oauth_token.do with the OAuth client created at Connect (client-credentials grant) and sends it as a bearer token with each event. The token runs as truu.idv.integration, which can’t sign in to the UI and has no password. TruU reuses a token until shortly before it expires and requests a new one when your instance rejects it.
  • Your instance to TruU: the app calls the TruU API with its API key, stored as an encrypted property that only x_truu_idv.admin can read or change.
  • Rate limit: the endpoint allows 3,600 requests per hour for the integration role. Find it under System Web Services → REST → Rate Limit Rules as TruU IDV events.
To cut TruU off from your instance, deactivate the TruU Identity Verification OAuth client (System OAuth → Application Registry) or the truu.idv.integration user. Connecting again turns both back on.

What the app reads and writes

TruU does not read ServiceNow tables. The only calls TruU makes into your instance are requesting an OAuth token and delivering verification events to the app.

Network

No MID Server, VPN, or inbound firewall change on your own network is needed.

Settings admins change

The app’s settings are under its Properties module and require x_truu_idv.admin. Leave the API base URL property blank. Blank means the app uses the TruU API at agent.truu.ai; change it only if TruU support asks you to.

Flow Designer

Use the app’s Flow Designer content to require verification inside your own catalog items or automations.
Publish the TruU: Verify Identity and Wait subflow after you install or upgrade the app. It installs as a draft, and flows that call it fail until it is published.

Self-service with Flow Designer

Employees can verify themselves from the ServiceNow portal, with no agent involved: put verification in front of a catalog item such as “Reset my MFA”.
1

Create a flow on the catalog item

In Flow Designer, create a flow with the Service Catalog trigger for your catalog item.
2

Add the subflow

Add TruU: Verify Identity and Wait as the first action and set its inputs:
3

Act on the result

The subflow returns Verified (true or false) and the Verification Request record. Add a flow condition so the fulfillment steps run only when Verified is true.
ServiceNow Flow Designer with a Service Catalog trigger and the TruU: Verify Identity and Wait subflow, showing Subject User, Use Case, Reason, Source Table and Source Record inputs

A Service Catalog flow that verifies the requester before fulfillment.

The use case you pick decides the flow and what happens after, so a Password reset catalog item can also issue a Windows Temporary Access Pass or reset PingOne MFA automatically. See How use cases work.

Verifying the connection

  1. In the IDV Console, run Test connection on the ServiceNow connector. It sends a test event to your instance and reports the result.
  2. Open a test Incident, choose Verify Identity, and send a link to a test user by email.
  3. Complete the verification on the test user’s phone.
  4. Confirm the work notes and status field update on the Incident and a row appears in Verification Requests.

Troubleshooting

Known issues

  • Upgrading the app clears its credentials. After any upgrade, generate a new connect link and connect again, then publish the subflow.
  • Upgrading to 1.1.3 or later needs a reconnect. Earlier versions authenticated events with a shared secret, which 1.1.3 removes. Connect again to create the integration user and OAuth client; until you do, results don’t reach your records.
  • Which use case is used. The Verify Identity action sends Helpdesk. Flow Designer content sends the use case you pick: Help desk (Helpdesk), Pre-hire (Onboarding) or Password reset (Credential reset). See How use cases work.

Solution guide: verified help desk

Roll out verified resets end to end.

Creating verification requests

The agent workflow the app mirrors.

Network and allowlists

Every host TruU uses.

Permissions and roles

Why the app cannot change your TruU configuration.