docs: end-to-end Apify webhook example#176
Merged
bobakemamian merged 2 commits intomainfrom Apr 21, 2026
Merged
Conversation
Captures the exact flow validated against real Apify infrastructure on
2026-04-21: two buttons (scrape launcher + dataset fetcher) + one
drawer with webhook trigger. Real trip time: ~15s from press to
`[serve] drawer on-apify-done ok`.
Exercises the whole webhook surface in one walk-through:
- batteries for the Apify token (globally scoped, stays out of repos)
- `buttons webhook setup` with the cert.pem flow, apex guard, and
zone-drift detection
- alternative --api-token path for multi-zone / headless
- `${inputs.webhook.body.resource.defaultDatasetId}` CEL resolution
- auto-declared `webhook` input on trigger drawers
- drawer-level retry policy on transient upstream 502s
- listener drain + process-group kill on Ctrl-C
- dry-run via `press --webhook-body` without running the listener
Flags a known gap: `drawer NAME set on_failure.*` is not yet wired;
direct JSON edit of drawer.json is the current path. Worth a follow-up.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Promotes the examples folder out of docs/ to the repo root so it's discoverable alongside README/CLAUDE.md without spelunking into the Mintlify docs tree. Both walk-throughs move: - examples/apify-to-snowflake.md (drawer composition reference) - examples/apify-webhook-scrape.md (just-added webhook reference) Updates the single CLAUDE.md reference to the new paths. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Captures the exact flow we validated against real Apify infrastructure on 2026-04-21 as a reference example under
docs/examples/apify-webhook-scrape.md.Covers:
buttons webhook setupwith cert.pem or--api-tokenpaths (apex guard + zone-drift detection both noted)apify-scrape-ig-post(fire + register callback) andapify-fetch-dataset(pull results)on-apify-donewith webhook trigger at/apify-donepress --webhook-bodywithout running the listenerFlags a gap:
drawer NAME set on_failure.*isn't supported by thesetverb yet — direct JSON edit is the current path. Worth a follow-up to extendservice.SetFieldor add a dedicated retry verb.🤖 Generated with Claude Code