Integrations / Netlify

Netlify

Netlify web deployment and hosting platform

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 Netlify team you can access.

Vendor setup

Get the credential

Prefer Connect

Settings → Integrations → Netlify. Approve access in Netlify.

Token fallback

In Netlify, User settings → Applications → New access token. Paste it in Telara.

Permissions Telara requests

sites:read
OAuth 2.0
deploys:read
OAuth 2.0
deploys:write
OAuth 2.0
sites:write
OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

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.

API key

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

Fields Telara asks for

API key

Knowledge

What gets indexed

Resource	Coverage
Site	Partial — not every record the vendor holds is synced
Deploy	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Site	Up to 1 day	Removed records disappear on the next full sync
Deploy	Up to 1 hour	provider tombstone

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: Site, Deploy.

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 from a personal account will not see a team’s sites.

Deploy access is whatever that token was granted.