Skip to content

Langfuse: read the topic from type - #97

Open
garethx wants to merge 1 commit into
mainfrom
fix/langfuse-topic-identifier
Open

garethx wants to merge 1 commit into
mainfrom
fix/langfuse-topic-identifier

Conversation

@garethx

@garethx garethx commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

This changes one field. providers/langfuse/index.json now uses "topic_identifier": "type" in place of "action".

Langfuse's current docs show two webhook payloads: prompt-version and monitor-alert. Both name the event in a top-level type field ("prompt-version", "monitor-alert"). The old v1/created.json sample keyed off action, but the docs no longer describe that shape.

Every other change from the 2026-11-12 webhook hub batch comes through webhook-registry, not this PR. All the files involved are doc-sourced (they carry a source key), so the Doc samples guard would fail a direct edit, and the next registry sync would overwrite one anyway. Once the batch's registry changes merge, the registry-sync pull request will:

  • replace doc-example personal data with placeholders in payt, kolide, globalstack, goody, creem, fountain, felloh, justt, isnap and loyaltylion. That covers names, emails, addresses, tokened links, account numbers and SSN-style values. The opaque IDs the vendors printed are kept.
  • refresh stale shapes from the vendors' current examples: formbricks (dataByQuestionCode, outcome), omnara (agent_profile_id, parent_agent_id, root_agent_id) and notifuse contact.created (four consent fields).
  • remove langfuse/v1/created.json and add prompt-version.json and monitor-alert.json.

For existing providers the sync never touches index.json, so the Langfuse discriminator has to change here. The change doesn't depend on merge order, because doc samples carry their own topic. sourced_on stays at 2026-10-26. It is still the oldest retrieval date for this version, so it does not overstate how fresh the samples are.

Checks: yarn test passes (26 of 26) and yarn compile passes. The guard script reports no doc-sourced edits. I also ran the registry's sync_webhook_samples.py plan against this branch for these 14 providers: 9 adds, 167 updates and 1 removal, with nothing blocked and no captures affected. With that plan applied to a scratch copy, yarn compile still passes.

🤖 Generated with Claude Code

Langfuse's current docs send prompt-version and monitor-alert payloads
with the event in a top-level type field; the action field the old
created sample used is no longer the discriminator. The samples themselves
arrive through webhook-registry's sync, which leaves index.json alone for
existing providers, so this one field is changed here.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
webhook-samples Ready Ready Preview Nov 19, 2026 1:43pm UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — 2f694c04 Deployed Nov 19, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant