Integrations / GitHub Actions

GitHub Actions

GitHub Actions workflow automation for workflows, workflow runs, jobs, artifacts, logs, and deployment execution evidence.

OAuth 2.0

Indexes

Actions

Events

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events Yes

Before you connect

Prerequisites

A GitHub organization whose Actions Telara should see.

Owner, or a token/app that can read Actions. This is not the GitHub source connector.

Vendor setup

Get the credential

Prefer the GitHub App

Use the same Telara GitHub App install when it already covers Actions, or install with Actions access.

Token fallback

Create a personal access token that can read Actions and paste it under Settings → Integrations → GitHub Actions.

Permissions Telara requests

repo
OAuth 2.0
workflow
OAuth 2.0
read:org
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

GitHub OAuth App authorization-code connection for repository Actions reads. The OAuth app must be registered with repo, workflow, and read:org scopes; GitHub App and personal-access-token connections remain available.

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.

GitHub App

GitHub App installation token with Actions repository permissions.

Install Telara’s GitHub App using the installation link from your administrator, then finish Connect under Settings → Integrations.

Fields Telara asks for

App ID
Installation ID
Private key

Personal access token

GitHub token with repository Actions access.

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

Fields Telara asks for

Access token

Knowledge

What gets indexed

Resource	Coverage
Pipeline run	Partial — not every record the vendor holds is synced
Job	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Pipeline run	Up to 1 hour	Removed records disappear when Telara next reconciles that resource
Job	Up to 1 hour	Removed records disappear when Telara next reconciles that resource

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: Pipeline run, Job.

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

A token that can clone code is not enough if Actions access was never granted.

Fine-grained tokens must include Actions on every repository Telara should see.