Skip to main content

Integrations

Integrations connects providers your organisation owns — starting with AI keys you bring yourself (BYOK). Use this page when you want Content or Asset Generate without sharing keys across tenants. Integrations are organisation-scoped. Enable providers on the org that should use them. For the full platform list (product area, vendor pricing, build priority, status, vault vs platform-owned), see Integration platforms.

Supported integrations

What you can connect today and which Brandblox capabilities each platform unlocks: Legend: Yes = shipped capability for connected orgs · Partial = connectable but limited (see notes) · — = not this provider’s job Partial notes (code-backed):
  • Asset Generation (OpenAI / Claude / OpenRouter) — Generate UI unlocks with an enabled AI integration; image output today is a placeholder stub, not a full vaulted image model call.
  • Asset Storage (S3) — BYO bucket settings connect in Integrations; credentials are not vaulted yet, so uploads stay on Brandblox R2 until that slice ships.
Catalog label Claude is Anthropic. Platform defaults (R2 media, SendGrid send-test, Workers AI for Add from URL) are Brandblox-owned — see Integration platforms.

Coming soon / On hold

Not connectable yet — see Integration platforms for Priority vs Status and each vendor’s public-API capability notes (template, campaign, assets, blocks, lists, send, preview):
  • Medium priority: Constant Contact, Campaign Monitor (trial-only / no lasting free)
  • On hold (enterprise / sales-led): Dotdigital, Iterable, Adestra (Upland Adestra), Acoustic, Salesforce Marketing Cloud (SFMC), Pardot / Account Engagement (Salesforce Account Engagement), Oracle Responsys, Adobe Marketo Engage (Marketo), and Adobe Campaign

AI (BYOK)

Add Integration walks through:
  1. Provider — pick from the catalog (filter by capability tags — Email Export, Content Generation, Asset Generation, Automations, Asset Storage — or search). OpenAI / Claude / OpenRouter carry Content Generation and Asset Generation; Zapier is Automations; Klaviyo, Braze, Mailchimp, Brevo, Omnisend, HubSpot, Kit, MailerLite, SendGrid, Mailjet, Vero, and Bird are Email Export; S3 is Asset Storage.
  2. Connect — name + API key (encrypted in Brandblox’s secure vault; the app keeps only a vault reference and last-four hint). For Klaviyo, use a private API key with templates:write, campaigns:write, lists:read, and accounts:read. For Braze, choose the REST cluster URL and a REST API key with templates.email.create, templates.email.list, segments.list, and messages.schedule.create (plus App Identifier + from email for campaigns). For Mailchimp, paste a Marketing API key (…-us21) from Account → Extras → API keys; the suffix is the server prefix. For Brevo, paste a v3 API key from Settings → SMTP & API → API Keys. For Omnisend, paste an API key from Store settings → Integrations → API keys with email-templates.write, campaigns.write, and segments.read. For HubSpot, paste a private app access token with content, marketing.email.read, marketing.email.write, and crm.lists.read. For Kit, paste a v4 API key from Settings → Developer → API keys. For MailerLite, paste an API token from Integrations → MailerLite API (optional verified from email recommended). For SendGrid, paste a Marketing Campaigns API key from Settings → API Keys with Marketing (Designs, Single Sends, Lists) Full Access and Sender Verification Read Access — this is your org’s BYOK key, separate from Brandblox platform send-test. For Mailjet (Sinch), paste the Public API Key and Secret Key from Account Settings → API Keys. For Vero, paste a Campaign API key from Settings → Project → API Keys → Campaign API (Campaigns API access is granted on request via support@getvero.com). For Bird (MessageBird), paste an API key (bk_us1_… or bk_eu1_…) from Developers → API keys (optional from email/name recommended).
  3. Configure (AI only) — pick the model this named connection should use (Recommended / Best / Fast / Cheap when available). Klaviyo, Braze, Mailchimp, Brevo, Omnisend, HubSpot, Kit, MailerLite, SendGrid, Mailjet, Vero, and Bird skip Configure.
You can connect the same API key multiple times under different names and models — for example OpenAI - Fast and OpenAI Cheap — so Generate stays simple while power users keep cost/quality tiers. Click a row (or ⋯ → Edit) to change the name and, for AI connections, pick the model on that same screen. The API key is shown locked (hashed, last four visible). Unlocking warns that the old vaulted key will be removed — you must paste a new key; leaving it empty does not keep the previous secret. Cancel unlock to leave the vaulted key in place. Use ⋯ → Disable / Enable to toggle availability, or Delete to revoke the vault secret and remove the connection.

Content Generate

On Content Generate, pick the integration by name only. The model comes from that integration’s saved configuration — there is no separate model dropdown. At least one enabled AI integration unlocks:
  • Content Generate (runs against your vaulted key + saved model)
  • Asset Generate (where shown)
Without an enabled AI integration, Generate UI stays disabled; manual workflows still work. Add from URL uses Brandblox AI (platform Workers AI) for a one-shot refine after HTML extract — it does not require a BYOK integration.

Emails export (Klaviyo / Braze / Mailchimp / Brevo / Omnisend / HubSpot / Kit / MailerLite / SendGrid / Mailjet / Vero / Bird)

Connect Klaviyo, Braze, Mailchimp, Brevo, Omnisend, HubSpot, Kit, MailerLite, SendGrid, Mailjet, Vero, or Bird to export juiced email HTML from the email builder Export → Export tab:
  • Create template — new HTML email template in the connected CRM (MailerLite creates a draft campaign — it has no separate templates API; SendGrid creates a Design Library design; Mailjet/Bird create a marketing template; Kit/Vero create a draft broadcast)
  • Create campaign — new campaign (Klaviyo/Mailchimp/Brevo/HubSpot/MailerLite/SendGrid/Mailjet/Bird audience list or group, Braze/Omnisend segment, Kit segment/tag, or Vero preference topic) with that HTML already added (SendGrid creates a draft Single Send; Mailjet creates a campaign draft; Bird creates a broadcast draft; Vero creates a draft broadcast — set audience in Vero)
Deep links: /integrations?add=Klaviyo, /integrations?add=Braze, /integrations?add=Mailchimp, /integrations?add=Brevo, /integrations?add=Omnisend, /integrations?add=HubSpot, /integrations?add=Kit, /integrations?add=MailerLite, /integrations?add=SendGrid, /integrations?add=Mailjet, /integrations?add=Vero, /integrations?add=Bird. Operator setup notes live in the Project store (docs/klaviyo-email-export-setup.md, docs/braze-email-export-setup.md, docs/mailchimp-email-export-setup.md, docs/brevo-email-export-setup.md, docs/omnisend-email-export-setup.md, docs/hubspot-email-export-setup.md, docs/kit-email-export-setup.md, docs/mailerlite-email-export-setup.md, docs/sendgrid-email-export-setup.md, docs/mailjet-email-export-setup.md).

Other connectors

Zapier and similar connectors skip Configure when they have no settings. Follow the Integrations wizard in-app when a connector is available for your org.

S3 / DAM (BYO asset storage)

Connect a customer S3-compatible bucket to override Brandblox’s default R2 media storage for that organisation’s new uploads. You provide:
  • Bucket name
  • Region
  • Public https:// base URL (CDN or website endpoint used in email img src)
  • Optional API endpoint (for non-AWS S3-compatible hosts)
Access keys are not stored in the app database. Until credentials are vaulted and the connection is enabled + healthy, uploads continue on Brandblox R2. Object keys stay immutable (/{workspace}/{asset}/{hash}.ext) and email-safe (no signed URLs).