Integration
Connect GitHub and Sendinblue
When New Branch fires in GitHub, your agent runs Add contact in Sendinblue, or New contact in Sendinblue to Add Labels to Issue in GitHub. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want GitHub and Sendinblue to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What GitHub and Sendinblue can do together
From GitHub to Sendinblue
When New Branch in GitHub
then Add contact in Sendinblue
When New Collaborator in GitHub
then Add contact attribute in Sendinblue
From Sendinblue to GitHub
When New contact in Sendinblue
then Add Labels to Issue in GitHub
When Updated contact in Sendinblue
then Create Issue in GitHub
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with GitHub and Sendinblue
Triggers and actions 17 triggers · 41 actions
Trigger
Issue ClosedTriggers when an issue in a repository is closed.
Trigger
New BranchTriggers when a new branch is created in a GitHub repository.
Trigger
New CollaboratorTriggers when a new collaborator is added to a GitHub repository.
Trigger
New CommitTriggers when a new commit is pushed to a GitHub repository's default branch.
Trigger
New Commit CommentTriggers when someone comments on a commit in a repository.
Trigger
New GistTriggers when you create a new gist on GitHub.
Trigger
New Global EventTriggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
Trigger
New IssueTriggers when a new issue is created in a repository.
Trigger
New LabelTriggers when a new label is added to a GitHub repository.
Trigger
New MilestoneTriggers when a new milestone is created in a repository.
Trigger
New Pull RequestTriggers when a new pull request is opened in a repository.
Trigger
New ReleaseTriggers when a new release is published in a GitHub repository.
Trigger
New Repo EventTriggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
Trigger
New RepositoryTriggers when a new public repository appears under a GitHub user or organization.
Trigger
New WatcherTriggers when someone starts watching a repository.
Action
Add Labels to IssueAdds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
Action
Check Organization MembershipChecks whether a GitHub user is a member of an organization and returns true or false.
Action
Create BranchCreates a new branch in a repository, starting from the commit you choose.
Action
Create CommentAdds a comment to an issue or pull request in a GitHub repository.
Action
Create GistCreates a new gist with one file on the connected GitHub account.
Action
Create IssueCreates a new issue in a GitHub repository.
Action
Create or Update FileCreates a new file in a repository, or replaces an existing file's contents, as a commit.
Action
Create Pull RequestOpens a pull request asking to merge one branch into another.
Action
Delete BranchDeletes a branch from a repository. Any open pull request from that branch is closed.
Action
Find BranchFinds a branch in a GitHub repository by name and returns its latest commit and protection status.
Action
Find IssueFinds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
Action
Find OrganizationFinds a GitHub organization by its login and returns its profile details.
Action
Find Pull RequestFinds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
Action
Find RepositoryReturns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
Action
Find UserFinds a GitHub user by username and returns their public profile.
Action
Get File ContentsReturns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
Action
Submit ReviewSubmits a review on a pull request: approve it, request changes, or leave a review comment.
Action
Update IssueUpdates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
Action
Update Pull RequestChanges a pull request's title, description, target branch, or open/closed state.
Trigger
New contactFires when a new contact is created in Brevo, delivered via a Brevo account webhook subscribed to the "contact created" (contactUpdated/contact) event on Accounts and Settings > Webhooks. Concrete delivery mechanism to be classified during implementation.
Trigger
Updated contactFires when an existing contact is updated, delivered via a Brevo account webhook subscribed to the contact-updated event. Concrete delivery mechanism to be classified during implementation.
Action
Add contactAdds a new contact
Action
Add contact attributeCreates a new contact attribute in Brevo (Sendinblue) under the chosen category and name.
Action
Add contact to listAdds existing Brevo contacts to a contact list, identified by email address, external ID or contact ID.
Action
Add email campaignCreate an email marketing campaign.
Action
Add eventRecords a custom event against a Brevo contact, optionally updating contact attributes and attaching event properties.
Action
Add listCreates a new, empty contact list inside a Brevo folder.
Action
Add senderCreates a new email sender in Brevo. Brevo sends a verification email to the sender address; the sender must be verified before it can be used in campaigns.
Action
Delete contactDelete a contact.
Action
Delete email campaignDeletes an email campaign that has not been scheduled.
Action
Delete listDelete a contact list.
Action
Get contactFetches a contact by email, ID, SMS number or external ID. An error occurs if the contact is not found.
Action
Get email campaignGet an email campaign's report/details by id.
Action
Get listRetrieve the details of a Brevo contact list by its ID, including name, folder, subscriber counts and campaign statistics.
Action
List contact attributesLists all contact attributes defined in the Brevo account, grouped by category.
Action
List contactsReturns all contacts in the Brevo account, optionally filtered by dates, contact IDs, list or segment, or an attribute value.
Action
List listsLists all contact lists in the Brevo account.
Action
List sendersLists the email senders in your Brevo account, optionally filtered by domain or dedicated IP.
Action
List transactional emailsLists transactional emails sent from your Brevo account, filtered by recipient email, template, or message ID. Covers the past 30 days unless a start and end date are given.
Action
Send transactional emailSends a transactional email to one or more recipients, using inline HTML/text content or a saved Brevo template.
Action
Update contactUpdate an existing contact's attributes/lists.
Action
Update email campaignUpdate an email campaign.
Action
Update listUpdates an existing Brevo contact list's name and/or moves it to a different folder.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from GitHub
GitHub to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
GitHub to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
GitHub to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
GitHub to Google SheetsGoogle Sheets
GitHub to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
GitHub to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Sendinblue
Hellotracks to SendinblueHellotracks is a field service platform for dispatching jobs, tracking mobile teams, and managing job status.
HubSpot to SendinblueHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SendinblueSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SendinblueGoogle Sheets
Gmail to SendinblueGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SendinblueGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
GitHub and Sendinblue, answered
What can start an automation from GitHub?
Any of GitHub's 15 triggers in the catalog, including New Branch, New Collaborator, New Commit and New Commit Comment. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sendinblue when something happens in GitHub?
Any of Sendinblue's 22 actions, including Send transactional email, Update contact, Update email campaign and Update list. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Sendinblue to GitHub?
Yes. When something happens in Sendinblue, your agent can act in GitHub too. This page covers both directions: Sendinblue's triggers and GitHub's actions are listed here as well.
Do I have to build a connector for GitHub or Sendinblue?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.