Repository navigation
instagram: add 1 doc-sourced sample (instagram/messages) - #81
Merged
Merged
Conversation
Copied as-is from hookdeck/webhook-registry samples-doc/providers/instagram/
at main @ ba2f81af (#140). The sample is the admin-text messages notice from
the Instagram Messaging webhooks page. safeStem("instagram/messages") gives
instagram.messages, matching the registry's file stem. messenger has no
samples in the registry, so nothing is added for it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mp6z12EgZRFuEhuPqFwxMT
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Gareth · project thread
Before: hookdeck/webhook-registry#140 (merged) added the
instagramandmessengerrows for the two Meta source types in hookdeck/core#6195. This repo had no samples for either.After:
providers/instagram/holds 1 doc-sourced sample,latest/instagram.messages.json. It is the "Admin text"messagesnotice from Meta's Instagram Messaging webhooks page: amessaging[]element withmessage.admin_textandhandoff_reason: purchase_intent. Its IDs are Meta's own placeholders (IGID,IGSID), so it holds no PII and nothing was substituted.index.jsonhastopic_identifier: nulland provenancedocs, likeproviders/facebook/.This PR covers instagram only. The registry has no samples for messenger:
samples-doc/providers/messenger/doesn't exist at registry main @ba2f81af, and the contents API returns 404 for it. #140 explains why. Every Messenger example is amessaging[]fragment or uses<PSID>-style placeholders. Thegroup_feedexample is wrapped in a top-level array.How: I copied
samples-doc/providers/instagram/from a fresh clone of registry main @ba2f81afas-is.diff -ragainst the source reports no differences.Topic and file stem: the sample's
topicisinstagram/messages, which contains a slash.safeStemintopic.ts(used byrequestReceiver.ts) givesinstagram.messages. The registry'sharvest_instagram.pygives the same stem (topic.replace("/", ".")), and so does its sharedsafe_stemrule. So the file name matches the receiver's stem and there is no mismatch.With
topic_identifier: null, a live capture would be saved asuntitled-<md5>, the same as facebook today. A capture-ready identifier would need key-presence logic, which is out of scope for this PR.Checks:
yarn install --frozen-lockfileworked.yarn compilesucceeded, andpublic/providers.jsonlists instagramlatestasdocs(sourced 2026-11-05).yarn testgave 26 passed, 0 failed.Generated by Claude Code