Skip to main content
Telara

Integrations / PagerDuty

PagerDuty logo

PagerDuty

PagerDuty incident management and on-call platform

API key
Indexes
Actions
Events

What Telara does

Capability matrix

Before you connect

Prerequisites

A PagerDuty account.
Account owner or an admin who can create API access keys.

Vendor setup

Get the credential

1
Open API Access
In PagerDuty, open Integrations → API Access Keys (or Account → API Access, depending on the plan).
2
Create a key
Create an API key for Telara. Paste it under Settings → Integrations → PagerDuty.

Permissions Telara requests

  • analytics.read
    OAuth 2.0
  • audit_records.read
    OAuth 2.0
  • change_events.read
    OAuth 2.0
  • custom_fields.read
    OAuth 2.0
  • escalation_policies.read
    OAuth 2.0
  • escalation_policies.write
    OAuth 2.0
  • event_orchestrations.read
    OAuth 2.0
  • event_rules.read
    OAuth 2.0
  • extension_schemas.read
    OAuth 2.0
  • extensions.read
    OAuth 2.0
  • incident_types.read
    OAuth 2.0
  • incident_workflows.read
    OAuth 2.0
  • incidents.read
    OAuth 2.0
  • incidents.write
    OAuth 2.0
  • notifications.read
    OAuth 2.0
  • oncalls.read
    OAuth 2.0
  • priorities.read
    OAuth 2.0
  • schedules.read
    OAuth 2.0
  • schedules.write
    OAuth 2.0
  • services.read
    OAuth 2.0
  • services.write
    OAuth 2.0
  • session_configurations.read
    OAuth 2.0
  • standards.read
    OAuth 2.0
  • status_dashboards.read
    OAuth 2.0
  • status_pages.read
    OAuth 2.0
  • tags.read
    OAuth 2.0
  • teams.read
    OAuth 2.0
  • teams.write
    OAuth 2.0
  • templates.read
    OAuth 2.0
  • users.read
    OAuth 2.0
  • users.write
    OAuth 2.0

In Telara

Connect in Telara

API key

REST API Key (Personal Access Token or Global Access Token)

In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.

Fields Telara asks for
  • API token
OAuth 2.0

OAuth2 for third-party app integrations

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.

Knowledge

What gets indexed

ResourceCoverage
ServicePartial — not every record the vendor holds is synced
SchedulePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
ServiceUp to 1 dayRemoved records disappear on the next full sync
ScheduleUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

Excluded from semantic search: Service, Schedule.

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

User-level keys only see what that user can see. Prefer an account-level key for operations coverage.
Classic vs REST key types are easy to mix up — if Connect fails, issue the key type Telara’s form labels.