Webflow + Brevo-integrasjon

Webflow + Brevo

Koble Webflows nettstedsdata til Brevos engasjementsplattform gjennom MCP. Fang skjemaleder, spor besøksadferd, pleie prospekter og utløs flerkanals kampanjer, alt orkestrert av AI-agenter i Claude.

MCP-servere som brukes

ServerPakke/URLAutentiseringFormål
Webflow MCPwebflow/mcp-serverOAuthNettsteder, skjemaer, skjemainnsendinger, CMS-samlinger, sideanalyse
Brevo MCPmcp.brevo.com/v1/brevo/mcpTokenKontakter, e-postkampanjer, SMS, WhatsApp, hendelsessporing

Tip

Webflows MCP-server eksponerer skjemainnsendinger, CMS-data og nettstedsmetadata. Par det med Brevo MCP for å gjøre hvert skjemautfylling til en segmentert kontakt med en automatisert pleiesekvens.

Oppsett

Trinn 1: Koble til begge MCP-servere

Legg til i Claude Desktop- eller Claude Code-konfigurasjonen:

{
"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"
}
}
}
}

Trinn 2: Bekreft tilkobling

Spør Claude:

> Hvilke skjemaer finnes på Webflow-nettstedet mitt?
> Hvor mange kontakter har jeg i Brevo?

Claude bør bruke Webflow MCP for det første spørsmålet og Brevo MCP for det andre.

Brukstilfelle 1: Skjemaledefangst-agent

Synkroniser Webflow-skjemainnsendinger til Brevo-kontakter med kildesporting:

---
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

Brukstilfelle 2: Besøkspleiesekvensagent

Utløs personaliserte pleiesekvenser basert på hvilket skjema og hvilken side lederen kom fra:

---
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

Brukstilfelle 3: CMS-innholdssynkroniseringsagent

Synkroniser Webflow CMS-samlinger til Brevo for dynamisk e-postinnhold:

---
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

Eksempel: Orkestrering på naturlig språk

Med begge MCP-servere tilkoblet kan du orkestrere i sanntid:

Du: "Sjekk Webflow for demo-forespørselsskjemainnsendinger fra
denne uken som ikke er i Brevo ennå, legg dem til som høyprioriterte
ledere og send hver en personalisert demo-bestillings-e-post."
Claude: Sjekker Webflow for demo-forespørselsinnsendinger...
[Bruker webflow MCP for å liste opp skjemaer og filtrere etter "Demo Request"]
[Finner 12 innsendinger fra denne uken]
Sjekker mot Brevo-kontakter...
[Bruker brevo_contacts for å søke etter hver e-post]
7 innsendinger er ikke i Brevo ennå. Behandler...
[Oppretter 7 nye kontakter med LEAD_PRIORITY=high]
[Legger alle 7 til "Demo Requests"-listen]
[Utløser demo-bestillings-e-postmal for hver]
Ferdig:
- 7 nye høyprioriterte kontakter opprettet i Brevo
- Alle lagt til "Demo Requests"-listen
- Demo-bestillings-e-poster sendt med personaliserte kalenderlenker
- 5 eksisterende kontakter hadde duplikatinnsendinger (hoppet over)

Neste steg

AI-assistent

Hei! Spør meg om dokumentasjonen.

Start gratis med Brevo