Integrations / Pipedream

Pipedream

Pipedream Connect usage records. Customer creates an OAuth client in their Pipedream workspace (client_credentials at /v1/oauth/token) — not a Telara-registered public OAuth app. Paste client_id, client_secret, project_id.

OAuth 2.0

Spend

Actions

What Telara does

Capability matrix

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

Before you connect

Prerequisites

A Pipedream workspace you can administer.

Workspace admin. Telara does not register a Pipedream OAuth app — you own the client.

Vendor setup

Get the credential

Open API OAuth clients

In Pipedream, go to Settings → API → OAuth Clients (wording is API → New OAuth Client).

Create a client

Click New OAuth Client. Name it for Telara. Copy client id, client secret, and the project id from the project switcher.

Paste in Telara

Settings → Integrations → Pipedream. Enter project id, client id, and client secret. Telara uses those to read usage records.

In Telara

Connect in Telara

OAuth 2.0

Pipedream Settings → API → New OAuth Client (client_credentials). Telara does not register a vendor OAuth app — the customer owns the client.

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

Project Id

Spend

What gets measured

Resolution: Aggregated buckets.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

credits
count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

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.

This catalog entry does not declare extra semantic-search exclusions.

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 personal API key is the wrong class for this connector. Use the OAuth client Settings → API creates.

Usage only exists for workflows in that project.