Webflow + Brevo Integration

Webflow + Brevo

Connect Webflow’s site data to Brevo’s engagement platform through MCP. Capture form leads, track visitor behavior, nurture prospects, and trigger multi-channel campaigns, all orchestrated by AI agents in Claude.

MCP Servers Used

ServerPackage/URLAuthPurpose
Webflow MCPwebflow/mcp-serverOAuthSites, forms, form submissions, CMS collections, page analytics
Brevo MCPmcp.brevo.com/v1/brevo/mcpTokenContacts, email campaigns, SMS, WhatsApp, event tracking

Tip

Webflow’s MCP server exposes form submissions, CMS data, and site metadata. Pair it with Brevo MCP to turn every form fill into a segmented contact with an automated nurture sequence.

Setup

Step 1: Connect Both MCP Servers

Add to your Claude Desktop or Claude Code configuration:

{
"mcpServers": {
"brevo": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.brevo.com/v1/brevo/mcp",
"--header",
"Authorization: Bearer ${BREVO_MCP_TOKEN}"
],
"env": {
"BREVO_MCP_TOKEN": "your-brevo-mcp-token"
}
},
"webflow": {
"command": "npx",
"args": ["-y", "webflow/mcp-server"],
"env": {
"WEBFLOW_TOKEN": "your-webflow-api-token"
}
}
}
}

Step 2: Verify Connection

Ask Claude:

> What forms exist on my Webflow site?
> How many contacts do I have in Brevo?

Claude should use Webflow MCP for the first question and Brevo MCP for the second.

Use Case 1: Form Lead Capture Agent

Sync Webflow form submissions to Brevo contacts with source tracking:

---
name: webflow-lead-capture
description: Sync Webflow form submissions to Brevo contacts with lead scoring
version: 1.0.0
temperature: 0.1
tools:
- webflow
- brevo_contacts
- brevo_attributes
- brevo_lists
triggers:
- event: form_submission
- schedule: "*/15 * * * *"
---
# Webflow Lead Capture Agent
Capture every Webflow form submission and create enriched Brevo contacts.
## Strategy
1. Poll Webflow for new form submissions since last sync
2. For each submission, create or update Brevo contact with:
- Email, name, phone (from form fields)
- Form name and page URL (as Brevo attributes)
- Submission timestamp
- UTM parameters if available
3. Add contacts to Brevo lists based on form type:
- Contact form → "Inbound Leads" list
- Newsletter signup → "Newsletter Subscribers" list
- Demo request → "Demo Requests" list (high priority)
- Download gate → "Content Leads" list
## Field Mapping
| Webflow Form Field | Brevo Attribute |
|-------------------|-----------------|
| Email | EMAIL |
| Name / First Name | FIRSTNAME |
| Last Name | LASTNAME |
| Phone | SMS |
| Company | COMPANY |
| Message | LEAD_MESSAGE |
| _form_name | WEBFLOW_FORM |
| _page_url | LEAD_SOURCE_URL |
| utm_source | UTM_SOURCE |
| utm_campaign | UTM_CAMPAIGN |
## Rules
- ONLY create contacts from submissions that include a valid email
- NEVER create duplicate contacts, update existing if email matches
- ALWAYS store the form name and page URL for lead attribution
- Track events: webflow_form_submitted, webflow_lead_created

Use Case 2: Visitor Nurture Sequence Agent

Trigger personalized nurture sequences based on which form and page the lead came from:

---
name: webflow-nurture-sequence
description: Orchestrate email nurture sequences based on Webflow form context
version: 1.0.0
temperature: 0.3
tools:
- webflow
- brevo_contacts
- brevo_email_campaign_management
- brevo_templates
- brevo_sms_campaigns
triggers:
- event: webflow_lead_created
---
# Webflow Nurture Sequence Agent
When a new lead is captured from Webflow, trigger the appropriate nurture sequence in Brevo based on form type and page context.
## Sequence Logic
### Contact Form Leads
1. Immediate: Thank-you email confirming message received
2. Day 1: Introduction email with relevant case studies
3. Day 3: Follow-up with product overview
4. Day 7: "Still interested?" with calendar link
### Newsletter Subscribers
1. Immediate: Welcome email with top 3 articles
2. Day 3: Content digest based on signup page topic
3. Day 7: Product mention with value prop
4. Weekly: Newsletter inclusion
### Demo Requests (High Priority)
1. Immediate: Confirmation email + calendar booking link
2. +30 min: SMS confirmation with time slot options
3. Day 1: If no booking → follow-up email with demo video
4. Day 2: If no booking → WhatsApp with direct message
5. Day 3: Escalate to sales team via Brevo deal creation
### Content Downloads
1. Immediate: Delivery email with download link
2. Day 2: Related content recommendation
3. Day 5: Product connection to content topic
4. Day 10: Soft CTA with case study
## Rules
- ALWAYS check contact opt-in status before sending
- NEVER send SMS or WhatsApp without explicit phone + consent
- Personalize with: first name, form type, page they visited
- Use Brevo template variables for dynamic content
- Track engagement: nurture_email_sent, nurture_sms_sent

Use Case 3: CMS Content Sync Agent

Sync Webflow CMS collections to Brevo for dynamic email content:

---
name: webflow-cms-sync
description: Sync Webflow CMS items to Brevo for dynamic email personalization
version: 1.0.0
temperature: 0.1
tools:
- webflow
- brevo_contacts
- brevo_email_campaign_management
- brevo_templates
triggers:
- schedule: "0 8 * * 1"
---
# CMS Content Sync Agent
Pull published content from Webflow CMS collections and use it to power dynamic Brevo campaigns.
## Strategy
1. Query Webflow CMS for blog posts, case studies, or product updates published in the last 7 days
2. Format content summaries for email inclusion
3. Match content to Brevo segments based on topic tags
4. Trigger weekly digest campaigns with personalized content blocks
## Content Mapping
| Webflow CMS Field | Brevo Usage |
|-------------------|-------------|
| name / title | Email subject line, content block heading |
| slug | Link URL construction |
| post-summary | Email preview text |
| main-image | Email hero image |
| category | Segment matching |
| published-on | Recency sorting |
## Rules
- ONLY include published items (not drafts)
- ALWAYS include a direct link back to the Webflow page
- Match content categories to Brevo list interests
- Maximum 5 content items per digest email

Example: Natural Language Orchestration

With both MCP servers connected, you can orchestrate in real-time:

You: "Check Webflow for any demo request form submissions from
this week that aren't in Brevo yet, add them as high-priority
leads, and send each one a personalized demo booking email."
Claude: Checking Webflow for demo request submissions...
[Uses webflow MCP to list forms and filter by "Demo Request"]
[Finds 12 submissions from this week]
Checking against Brevo contacts...
[Uses brevo_contacts to search for each email]
7 submissions are not yet in Brevo. Processing...
[Creates 7 new contacts with LEAD_PRIORITY=high]
[Adds all 7 to "Demo Requests" list]
[Triggers demo booking email template for each]
Done:
- 7 new high-priority contacts created in Brevo
- All added to "Demo Requests" list
- Demo booking emails sent with personalized calendar links
- 5 existing contacts had duplicate submissions (skipped)

Next Steps

AI Assistant

Hi! Ask me anything about the docs.

Start Free with Brevo