Webflow + Brevo Integration
Webflow + Brevo
Webflows Site-Daten mit Brevos Engagement-Plattform über MCP verbinden. Formular-Leads erfassen, Besucherverhalten verfolgen, Interessenten pflegen und Mehrkanal-Kampagnen auslösen – alles orchestriert durch KI-Agenten in Claude.
Verwendete MCP-Server
| Server | Paket/URL | Auth | Zweck |
|---|---|---|---|
| Webflow MCP | webflow/mcp-server | OAuth | Sites, Formulare, Formulareinreichungen, CMS-Kollektionen, Seitenanalysen |
| Brevo MCP | mcp.brevo.com/v1/brevo/mcp | Token | Kontakte, E-Mail-Kampagnen, SMS, WhatsApp, Event-Tracking |
Tip
Webflows MCP-Server stellt Formulareinreichungen, CMS-Daten und Site-Metadaten bereit. In Kombination mit Brevo MCP wird jedes ausgefüllte Formular zu einem segmentierten Kontakt mit einer automatisierten Nurture-Sequenz.
Einrichtung
Schritt 1: Beide MCP-Server verbinden
In Ihrer Claude Desktop- oder Claude Code-Konfiguration hinzufügen:
{ "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" } } }}Schritt 2: Verbindung prüfen
Claude fragen:
> Welche Formulare gibt es auf meiner Webflow-Site?> Wie viele Kontakte habe ich in Brevo?Claude sollte Webflow MCP für die erste Frage und Brevo MCP für die zweite verwenden.
Anwendungsfall 1: Formular-Lead-Erfassungs-Agent
Webflow-Formulareinreichungen mit Quell-Tracking zu Brevo-Kontakten synchronisieren:
---name: webflow-lead-capturedescription: Sync Webflow form submissions to Brevo contacts with lead scoringversion: 1.0.0temperature: 0.1tools: - webflow - brevo_contacts - brevo_attributes - brevo_liststriggers: - 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 sync2. 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 available3. 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_createdAnwendungsfall 2: Besucher-Nurture-Sequenz-Agent
Personalisierte Nurture-Sequenzen basierend auf Formular und Seite auslösen:
---name: webflow-nurture-sequencedescription: Orchestrate email nurture sequences based on Webflow form contextversion: 1.0.0temperature: 0.3tools: - webflow - brevo_contacts - brevo_email_campaign_management - brevo_templates - brevo_sms_campaignstriggers: - 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 Leads1. Immediate: Thank-you email confirming message received2. Day 1: Introduction email with relevant case studies3. Day 3: Follow-up with product overview4. Day 7: "Still interested?" with calendar link
### Newsletter Subscribers1. Immediate: Welcome email with top 3 articles2. Day 3: Content digest based on signup page topic3. Day 7: Product mention with value prop4. Weekly: Newsletter inclusion
### Demo Requests (High Priority)1. Immediate: Confirmation email + calendar booking link2. +30 min: SMS confirmation with time slot options3. Day 1: If no booking → follow-up email with demo video4. Day 2: If no booking → WhatsApp with direct message5. Day 3: Escalate to sales team via Brevo deal creation
### Content Downloads1. Immediate: Delivery email with download link2. Day 2: Related content recommendation3. Day 5: Product connection to content topic4. 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_sentAnwendungsfall 3: CMS-Content-Sync-Agent
Webflow-CMS-Kollektionen mit Brevo für dynamische E-Mail-Inhalte synchronisieren:
---name: webflow-cms-syncdescription: Sync Webflow CMS items to Brevo for dynamic email personalizationversion: 1.0.0temperature: 0.1tools: - webflow - brevo_contacts - brevo_email_campaign_management - brevo_templatestriggers: - 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 days2. Format content summaries for email inclusion3. Match content to Brevo segments based on topic tags4. 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 emailBeispiel: Natürlichsprachige Orchestrierung
Mit beiden verbundenen MCP-Servern können Sie in Echtzeit orchestrieren:
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)Nächste Schritte
- Brevo MCP-Server, Vollständige Liste der Brevo MCP-Module
- Agent-Spezifikation, Agent-Verhalten anpassen
- Shopify + Brevo, E-Commerce-Integration
- Custom API + Brevo, Connectors für jede Plattform erstellen