Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Nov 27, 2025

What

Improves the Facebook Pages connector documentation by fixing grammar issues and correcting a misleading reference that could confuse users.

This PR was created by an AI (Devin) as part of an automated documentation review following commit e21c11e.

Link to Devin run: https://app.devin.ai/sessions/b160b1ba089d4a33a4cd3af256509762

How

  1. Fixed grammar issues in the setup guide (added missing articles, improved phrasing)
  2. Added missing punctuation (colon after introductory sentence, space before backtick)
  3. Corrected "Setup Guide below" to "Setup Guide above" in Performance considerations section - the Setup Guide is actually above this section, not below
  4. Made the rate limiting guidance more specific by mentioning "Long-Lived Page Token"

Review guide

  1. docs/integrations/sources/facebook-pages.md - All changes are in this single file

Key changes to verify:

  • Line 17-19: Grammar improvements in setup steps
  • Line 26: Added colon after introductory sentence
  • Lines 41, 49: Added missing space before backtick in code formatting
  • Line 76: Fixed "below" → "above" reference (most important fix)

User Impact

Users will have clearer, more grammatically correct documentation. The fix to the "Setup Guide below" reference removes potential confusion when users are looking for rate limiting guidance.

Can this PR be safely reverted and rolled back?

  • YES 💚

…ence in documentation

Co-Authored-By: unknown <>
@devin-ai-integration
Copy link
Contributor Author

Original prompt from API User
Please use playbook macro: !connectordocs\n\nThe commit to review is e21c11ebc1d60f758b00b79ff55324a91bde3e22. This commit was pushed to master and may contain connector changes that need documentation updates.

PLAYBOOK_md:
## Overview

The goal of this task is to update Airbyte's end user documentation for a connector. A change has been merged to master in GitHub for that connector. Updated documentation might be necessary, since documentation quality can vary from connector to connector.

## Your role

You are Technical Writer Devin. You write clear, concise, and accurate technical documentation for end users of Airbyte. Your audience consists of data engineers who are using Airbyte to move data from one location to another. Some readers are less technical and some are more technical. Assume you are writing for someone who is less technical so all audiences can still follow your instructions, but don't patronize or look down upon your readers.

## Your task

1. Review the source code for the Airbyte connector described in this change.
         
2. To improve your context, search the web and read the official third-party API documentation for the product this connector works with. Not all third parties have public documentation, but most do. If you can't find the right documentation, ignore this step.
            
3. Find the user documentation for this connector. It's in the airbyte repository, in the /docs/integrations folder. Review this documentation. Based on the research you did in steps 1 and 2, create a new branch and propose any necessary improvements to this documentation. Perform this action in the following steps: Fix information that is technically incorrect. Then add information that isn't documented, but is necessary or helpful when trying to operate the connector. Then remove information that is irrelevant, outdated, or repeated. Then correct spelling and grammar mistakes.
            
4. Build the Docusaurus site locally using `pnpm clear` and `pn... (3281 chars truncated...)

@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
    • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
    • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
  • /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
  • /run-live-tests - Runs live tests for the modified connector(s).
  • /run-regression-tests - Runs regression tests for the modified connector(s).
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-dev.{git-sha}) for all modified connectors in the PR.
  • JVM connectors:
    • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
      Example: /update-connector-cdk-version connector=destination-bigquery
    • /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
  • Python connectors:
    • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
    • /poe source example lock - Alias for /poe connector source-example lock.
    • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
    • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.

📝 Edit this welcome message.

@devin-ai-integration devin-ai-integration bot added area/documentation Improvements or additions to documentation team/documentation labels Nov 27, 2025
@devin-ai-integration
Copy link
Contributor Author

Hi @ian-at-airbyte,

I am an AI (Devin) and have proposed documentation updates based on a review of commit e21c11e, which updated the Facebook Pages connector to v24 of the Facebook Graph API.

After reviewing the connector source code and the official Facebook Graph API documentation, I identified several improvements to the user documentation:

  1. Grammar fixes: Added missing articles ("a Facebook Developer Account", "a Facebook App") and improved phrasing ("Add the following permissions" instead of "Add next permission")
  2. Clarification: Added context that the Graph API Explorer is a Facebook tool
  3. Formatting: Added missing space before backtick in code formatting, added colon after introductory sentence
  4. Corrected misleading reference: The Performance considerations section said "follow the instructions in the Setup Guide below" but the Setup Guide is actually above that section. Changed to "Setup Guide above" and made the guidance more specific by mentioning "Long-Lived Page Token"

You can merge this PR, modify it, or close it if you disagree with the changes. This PR was requested by unknown ().

5. Fill in Page ID (if you have a page URL such as `https://www.facebook.com/Test-1111111111`, the ID would be`Test-1111111111`)
5. Fill in Page ID (if you have a page URL such as `https://www.facebook.com/Test-1111111111`, the ID would be `Test-1111111111`)

### For Airbyte OSS:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[markdownlint-fix] reported by reviewdog 🐶

Suggested change
### For Airbyte OSS:
### For Airbyte OSS

@github-actions
Copy link
Contributor

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-p3nt6pkkf-airbyte-growth.vercel.app

Built with commit 677d0b9.
This pull request is being automatically deployed with vercel-action

devin-ai-integration bot added a commit that referenced this pull request Dec 5, 2025
This PR consolidates changes from three separate PRs (#70243, #70275, #70276) into a single cohesive update:

Grammar and formatting improvements:
- Added missing articles (a Facebook Developer Account, a Facebook App)
- Improved phrasing (these instructions, the following permissions)
- Added missing colon after introductory sentence
- Fixed missing space before backtick in code formatting
- Removed trailing colon from heading per markdownlint

Reference and content fixes:
- Fixed misleading 'Setup Guide below' to 'Setup Guide above'
- Made rate limiting guidance more specific (Long-Lived Page Token)

OAuth permissions alignment:
- Aligned OAuth App permissions with Step 3 setup guide
- Added read_insights (required for Page Insights and Post Insights streams)
- Removed unnecessary permissions (pages_manage_ads, pages_manage_metadata, catalog_management)
- Fixed typo 'The Facebook Pages' to 'the Facebook Pages'

Co-Authored-By: [email protected] <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants