Integration
Connect Gridfox and Sendinblue
When Record Created fires in Gridfox, your agent runs Add contact in Sendinblue, or New contact in Sendinblue to Add record in Gridfox. 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 Gridfox 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 Gridfox and Sendinblue can do together
From Gridfox to Sendinblue
When Record Created in Gridfox
then Add contact in Sendinblue
When Record Created or Updated in Gridfox
then Add contact attribute in Sendinblue
From Sendinblue to Gridfox
When New contact in Sendinblue
then Add record in Gridfox
When Updated contact in Sendinblue
then Update record in Gridfox
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 Gridfox and Sendinblue
Triggers and actions 4 triggers · 31 actions
Trigger
Record CreatedTriggers when a new record is created.
Trigger
Record Created or UpdatedFires when a record in the chosen Gridfox table is created or updated.
Action
Add recordCreate a record in a table.
Action
Add userAdd a user to the project.
Action
Delete recordDelete a record.
Action
Find recordsSearch records in a table by search parameters.
Action
Get recordGet a record by reference field value.
Action
Get record auditGet audit history for a record.
Action
List tablesList tables in the project.
Action
List User Groupslists the project's user groups with their member users (id, email).
Action
Update recordUpdate a record by reference field value.
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 Gridfox
Gridfox to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Gridfox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gridfox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gridfox to MailchimpMailchimp marketing automation and email platform.
Gridfox to StripeStripe is a payment processing platform for online businesses.
Gridfox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
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
Gridfox and Sendinblue, answered
What can start an automation from Gridfox?
Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Sendinblue when something happens in Gridfox?
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 Gridfox?
Yes. When something happens in Sendinblue, your agent can act in Gridfox too. This page covers both directions: Sendinblue's triggers and Gridfox's actions are listed here as well.
Do I have to build a connector for Gridfox 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.