Skip to main content
Telara

Integrations / ServiceNow

ServiceNow logo

ServiceNow

ServiceNow IT service management platform for incidents, changes, problems, CMDB, and service catalog

Basic auth
Indexes
Actions

What Telara does

Capability matrix

Before you connect

Prerequisites

A ServiceNow instance (production or developer) Telara can reach.
A user whose roles cover the ITSM records Telara should see. The token inherits that user’s access.

Vendor setup

Get the credential

1
Prefer Connect
Settings → Integrations → ServiceNow. Enter the instance URL, then approve access in ServiceNow. You do not register an OAuth app or set a callback URL.
2
Username and password when OAuth is unavailable
Some instances still paste a username and password. Use a dedicated integration user, not a personal admin login.

In Telara

Connect in Telara

Basic auth

Basic authentication — username and password. base_url is per-tenant (e.g. https://instance.service-now.com).

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Base Url
  • Username
  • Password
OAuth 2.0

OAuth 2.0 — requires base_url (per-tenant instance URL).

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Base Url

Knowledge

What gets indexed

ResourceCoverage
IncidentsPartial — not every record the vendor holds is synced
ProblemPartial — not every record the vendor holds is synced
Kb articlePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
IncidentsUp to 1 dayRemoved records disappear on the next full sync
ProblemUp to 1 dayRemoved records disappear on the next full sync
Kb articleUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Incidents, Problem, Kb article.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

The wrong instance URL (dev vs prod, or a missing https://) is the usual failed connect.
Narrow roles produce a narrow view in Telara. That is ServiceNow access, not a missing connector.