Repository navigation
docs(source-brevo): rewrite setup guide and document rate limits - #76849
Conversation
- Add prerequisites (Brevo account, API keys permission). - Rewrite API key generation steps based on Brevo's help docs. - Document start_date UTC format requirement. - Add rate limit guidance linking to Brevo's rate limit tiers. - Use Markdown links instead of backtick URLs. - Correct changelog date for 0.2.30 to 2026-04-01 (PR #75946 merge date). Co-Authored-By: bot_apk <apk@cognition.ai>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Deploy preview for airbyte-docs ready!
Deployed with vercel-action |
|
↪️ Triggering Reason: Docs/chore PR; no runtime behavior change requires prove-fix. Triggering review for PR hygiene and content validation. |
Reviewing PR for connector safety and quality.
|
AI PR Review ReportReview Action: APPROVED
📋 PR DetailsConnector & PR InfoConnector(s): Risk LevelLevel: 0 — No production impact Review Action DetailsAPPROVED — All enforced gates pass. octavia-bot will submit an APPROVE review on behalf of this report. APPROVE means "no blocking objection"; it does not authorize auto-merge. The merge decision remains with human reviewers or a separate auto-merge policy that consumes 🔍 Gate Evaluation DetailsGate-by-Gate Analysis
📚 Evidence ConsultedEvidence
|
Documentation Confidence Assessment
Overall Confidence: 4/5
externalDocumentationUrls.ql=100,sl=100,releaseStage: alpha.What I Verified vs. What I Inferred
airbyte-integrations/connectors/source-brevo/manifest.yaml):url_base: https://api.brevo.com/v3/andApiKeyAuthenticatorinjectingapi-keyinto the request header.api_keyandstart_dateare the only configuration fields;start_dateuses the regex^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}Z$.check.stream_names: [contacts]— the connection check calls thecontactsendpoint.incremental_syncblocks.modifiedSincerequest parameter.ExponentialBackoffStrategy./v3/contacts/…allows 10 RPS; "all other endpoints" fall back to 100 RPH.3f81be2landed 2026-04-01 UTC, so the previous changelog date of 2026-03-31 for 0.2.30 was one day off.Areas of Concern
What
Rewrites the Brevo source connector documentation so a data engineer new to Brevo can set up the connector end-to-end from the page, and documents behavior the previous page omitted.
Triggered by review of commit 5bcef3e (#76844), which bumped the SDM base image. The bump itself introduced no user-facing behavior change, but review of the page surfaced gaps worth addressing.
How
Corrections
0.2.30changelog date from2026-03-31to2026-04-01to match the merge date of PR chore(source-brevo): bump SDM base image for memory monitor (CDK PR #962) #75946 (commit3f81be2).api key→API keyand replaced a sentence-final comma with a period in the auth section.Additions
YYYY-MM-DDTHH:MM:SSZUTC format required bystart_date(from the manifest regex) and notes that the connection check hits thecontactsendpoint./v3/contacts/…has a higher limit (10 RPS) than the 100 RPH catch-all that applies to the other endpoints this connector uses.Restructuring
Configurationtable toConfiguration referenceand dropped the unused "Default Value" column (neither field has a default).Review guide
docs/integrations/sources/brevo.md— the whole file, especially:0.2.30date).User Impact
New Brevo users get a self-contained setup guide; existing users see accurate rate-limit guidance and a corrected changelog date. No functional connector change.
Can this PR be safely reverted and rolled back?
Link to Devin session: https://app.devin.ai/sessions/e6c9f311b5394a67b96081edd0b5ab43