Repository navigation
Add Brevo handler - #15
Open
brejesh4318 wants to merge 1 commit into
Open
brejesh4318 wants to merge 1 commit into
brejesh4318 wants to merge 1 commit into
Conversation
Read-only handler for Brevo (formerly Sendinblue) exposing contacts, lists, campaigns (with delivery statistics) and contact_events tables via the Brevo v3 REST API. Includes rate-limit backoff, filter pushdown and tests. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
This branch has not been 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.
Description
Adds a read-only handler for Brevo (formerly Sendinblue) using the v3 REST API. No new dependencies.
Tables:
contacts,lists,campaigns(delivery stats summed across lists) andcontact_events(opens, clicks, and so on).count.email,list_id,campaign_idandevent_typeequality filters to Brevo instead of filtering locally.Retry-After.check_connectionpasses Brevo's own error text through, because a 401 is often the IP allowlist rather than a bad key.contact_eventsmakes one API call per contact unless filtered byemail, since Brevo has no bulk events endpoint. This is documented in the README.Not included: write support (
INSERTintocontacts).Type of change
Verification Process
To ensure the changes are working as expected:
mindsdb/integrations/handlers/brevo_handler/tests/test_brevo_handler.py- Run
- With a Brevo API key, run:
I ran all four tables, with filters andpython -m unittest mindsdb.integrations.handlers.brevo_handler.tests.test_brevo_handler -v(14 tests).LIMIT, directly against a real Brevo account. I have not yet run them through the MindsDB SQL layer.Additional Media:
Checklist: