Integration
Connect Sendinblue to SigningHub
When New contact fires in Sendinblue, your agent runs Add Document in SigningHub. 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 Sendinblue and SigningHub to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Sendinblue can start in SigningHub
When New contact in Sendinblue
then Add Document in SigningHub
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 Sendinblue and SigningHub
Triggers and actions 2 triggers · 33 actions
- New contact
Fires 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.
- Updated contact
Fires 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.
- Add contact
Adds a new contact
- Add contact attribute
Creates a new contact attribute in Brevo (Sendinblue) under the chosen category and name.
- Add contact to list
Adds existing Brevo contacts to a contact list, identified by email address, external ID or contact ID.
- Add email campaign
Create an email marketing campaign.
- Add event
Records a custom event against a Brevo contact, optionally updating contact attributes and attaching event properties.
- Add list
Creates a new, empty contact list inside a Brevo folder.
- Add sender
Creates 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.
- Delete contact
Delete a contact.
- Delete email campaign
Deletes an email campaign that has not been scheduled.
- Delete list
Delete a contact list.
- Get contact
Fetches a contact by email, ID, SMS number or external ID. An error occurs if the contact is not found.
- Get email campaign
Get an email campaign's report/details by id.
- Get list
Retrieve the details of a Brevo contact list by its ID, including name, folder, subscriber counts and campaign statistics.
- List contact attributes
Lists all contact attributes defined in the Brevo account, grouped by category.
- List contacts
Returns all contacts in the Brevo account, optionally filtered by dates, contact IDs, list or segment, or an attribute value.
- List lists
Lists all contact lists in the Brevo account.
- List senders
Lists the email senders in your Brevo account, optionally filtered by domain or dedicated IP.
- List transactional emails
Lists 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.
- Send transactional email
Sends a transactional email to one or more recipients, using inline HTML/text content or a saved Brevo template.
- Update contact
Update an existing contact's attributes/lists.
- Update email campaign
Update an email campaign.
- Update list
Updates an existing Brevo contact list's name and/or moves it to a different folder.
- Add Digital Signature
Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
- Add Document
Uploads a document file into an existing SigningHub document package.
- Add Electronic Signature
Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
- Add Recipient to Workflow
Adds a signer or other recipient to a document package's workflow.
- Add User
Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
- Create Integration URL
Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
- Create Package
Creates a new document package in SigningHub to hold documents and recipients for a signing workflow.
- Download Package
Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
- Get Document Fields
Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
- Get Package
Returns the details of a SigningHub document package: its name, owner, status and the documents it contains.
- Share Document for Signing
Shares a prepared document package with its signers and starts the signing workflow.
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 Sendinblue
Sendinblue to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Sendinblue to WhopWhop is a platform that let's you build businesses.
Sendinblue to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Sendinblue to StripeStripe is a payment processing platform for online businesses.
Sendinblue to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Sendinblue to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SigningHubSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SigningHubGoogle Sheets
Gmail to SigningHubGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SigningHubGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Sendinblue and SigningHub, answered
What can start an automation from Sendinblue?
Any of Sendinblue's 2 triggers in the catalog, including New contact and Updated contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Sendinblue?
Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigningHub to Sendinblue?
SigningHub has no triggers in the catalog today, so automations start in Sendinblue. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.
Do I have to build a connector for Sendinblue or SigningHub?
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.
Can my AI client use Sendinblue and SigningHub without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.