Webflow + Brevo Integration

Webflow + Brevo

Tajo has a pilot Webflow connector and proposed form-to-contact rule. Offline tests cover the mapping, but a fresh Webflow installation and production sync have not been verified by this review. The UI, template and MCP steps below describe implemented design requiring live verification, not features assumed available in every workspace. A submitted form is not consent on its own. The proposed filter sends only submissions with an accepted opt-in field; verify that field and a controlled live run before relying on the path.

Connecting Webflow

If Webflow connection is available in your workspace, open Connections, choose Webflow under Connect a source and authorize Tajo in Webflow. Confirm the resulting source binding before building a rule.

Building the Sync

When the authorized Webflow binding and consent field are available, the rule builder can follow this path. Verify the preview and a controlled live run before treating it as operational.

1. In Tajo, open Agents and ask the Brevo Integration Architect, for example: “Send newsletter sign-ups from my Webflow site to Brevo.”
2. The agent inspects the Webflow connector. It sees field names and types, never submission values.
3. It proposes a rule with a field map and the consent filter, validates the field map and dry-runs the draft, then saves it.
4. Request publish approval runs a preview. It reads at most 10 submissions, writes nothing to Brevo and records counts only.
5. A person approves the exact rule on the Approvals page. Then the rule can be published.

A Webflow form_submissions -> Brevo contacts template is defined in code. If exposed in your authorized workspace, find it under Connections > Syncs and mappings > New sync from template. It proposes this map:

The implementation recognizes candidate fields named marketingConsent, marketing_consent, optIn, opt_in, newsletter, subscribe or Subscribe, and parses values such as true, yes, on, 1, checked or subscribed. These names and values are not consent evidence on their own. Review the form label, purpose and captured choice for the actual source; unknown or ambiguous evidence must stop marketing sync. Use double opt-in when the workflow requires it.

The configured runtime checks for new submissions every 15 minutes by default. Editing the rule returns it to draft for preview and approval. Verify the schedule, consent filter and destination writes in a controlled live run.

Webflow over MCP

Tajo defines a Webflow MCP route at https://alto.tajo.io/mcp/connectors/webflow for early-access accounts. Its code includes reads for sites, forms, submissions, CMS collections and items, products and orders. Verify authenticated host access and the current tool set in your workspace; MCP exposure does not prove a durable Webflow-to-Brevo sync.

claude mcp add --transport http tajo-webflow https://alto.tajo.io/mcp/connectors/webflow

Doing It Yourself

Webflow runs an official MCP server at https://mcp.webflow.com/mcp, with OAuth. Add it to Claude Code with:

claude mcp add --transport http webflow https://mcp.webflow.com/mcp

See Webflow’s MCP documentation. Pair it with Brevo’s MCP server, described in Brevo MCP Server. Check the opt-in field yourself before you add anyone to Brevo.

Next Steps

• Understanding data sync, how sync rules behave
• HubSpot + Brevo
• Shopify + Brevo