docs: enrich Airbyte and GitHub integration pages - #2825
Open
marcel-rbro wants to merge 4 commits into
Open
Conversation
Salvage still-useful content from two help-center articles being retired: - Airbyte: add a section on triggering an Airbyte sync automatically from an Apify webhook when an Actor run succeeds. - GitHub: clarify that a linked Actor is rebuilt manually by default, and the push webhook is what makes rebuilds automatic. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
marcel-rbro
added
documentation
Contributor
|
✅ Preview for this PR (commit |
Fix markdownlint bullet style, list punctuation, and passive voice flagged by the review-docs standards checks. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Move requirements into a page-level Prerequisites section near the top, reorder into a source -> connection -> auto-sync flow, and fold the auto-sync requirements into a lead-in so prerequisites no longer sit below the whole setup. Tighten prose and fix terminology. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename the two setup headings so they describe distinct steps: setting up the Apify Dataset source, then connecting that source to a destination. Add a short explainer of what an Airbyte connection is. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
marcel-rbro
marked this pull request as ready for review
July 28, 2026 09:57
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
2 participants
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.
What
Enriches two Integrations pages with still-useful content salvaged from help-center articles that are being retired as part of the help-center audit.
Airbyte
Adds a Trigger a sync automatically after an Actor run section: use an Apify
ACTOR.RUN.SUCCEEDEDwebhook to call the Airbyte API and start a sync for your connection, so a successful run refreshes the dataset and immediately moves the new data to your destination. The exact Airbyte endpoint/auth is deferred to the Airbyte API reference since it differs between Airbyte Cloud and self-managed instances.GitHub
Clarifies the manual-vs-automatic build distinction in the Build automatically on every push section: a linked Actor is rebuilt manually by default, and the push webhook is what makes rebuilds automatic. No new UI is documented.
Why
Part of the help-center → docs migration audit. Both pieces were the only non-duplicative, evergreen content in their source articles.