Integrations / LangSmith Alerts (Webhook)
LangSmith Alerts (Webhook)
LangSmith Alerting Rules webhook — push delivery of the runs that triggered an alert rule, in real time, instead of Telara polling /api/v1/runs/query. Complements the `langsmith` pull connector. One delivery covers ALL runs that tripped the rule in its evaluation window ({rule_id, start_time, end_time, runs: [...]}); the receiver splits `runs` into one SpendEvent per run (see mcp-gateway/internal/spendhook/handler.go's decodeEventRows) so per-run granularity is real, not a lie on top of a batched aggregate. LangSmith has no HMAC signing for alert webhooks; the tenant provisions a shared secret via the ?token= query parameter instead. TENG-2189.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
In Telara
Connect in Telara
Spend
What gets measured
Resolution: Per run.
Attribution: Matched to people by email.
How far back vendor history goes is not published uniformly for this connector.
- input_tokenstokens
- output_tokenstokens
- framework_runscount
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
This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.
Honesty