HubSpot + Brevo Integration
HubSpot + Brevo
HubSpots CRM-Daten mit Brevos Engagement-Plattform verbinden. HubSpot als Quelle der Wahrheit für Kontakt- und Deal-Daten nutzen und Brevo für die Ausführung von Mehrkanal-Kampagnen – E-Mail, SMS, WhatsApp.
Verwendete MCP-Server
| Server | URL | Auth | Zweck |
|---|---|---|---|
| HubSpot MCP | mcp.hubspot.com | OAuth/PKCE | CRM-Daten: Kontakte, Unternehmen, Deals, Tickets, Produkte, Bestellungen (nur Lesen) |
| Brevo MCP | mcp.brevo.com/v1/brevo/mcp | Token | Kontakte, E-Mail, SMS, WhatsApp, Kampagnen, Event-Tracking |
Caution
HubSpots MCP-Server ist derzeit nur lesend (BETA). Sie können CRM-Daten aus HubSpot lesen und für Aktionen in Brevo nutzen, aber nicht über MCP zurück in HubSpot schreiben. Für bidirektionale Synchronisierung verwenden Sie HubSpots REST-API neben der MCP-Verbindung.
Einrichtung
Schritt 1: HubSpot MCP-Auth-App erstellen
- In HubSpot zu Development > MCP Auth Apps gehen
- Create MCP auth app klicken
- Redirect-URL setzen (für Claude Desktop-Tests:
http://localhost:6274/oauth/callback/debug) - Ihre Client ID und Ihr Client Secret notieren
Schritt 2: Beide MCP-Server verbinden
Für Tools, die OAuth unterstützen (Cursor, VS Code):
{ "mcpServers": { "hubspot": { "url": "https://mcp.hubspot.com/", "headers": { "Authorization": "Bearer your-hubspot-oauth-token" } }, "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" } } }}Tip
HubSpot MCP erfordert OAuth mit PKCE. Tools wie Cursor unterstützen dies nativ. Für Claude Desktop/Code müssen Sie möglicherweise ein Token separat beziehen und als Bearer-Token übergeben.
Schritt 3: Verbindung prüfen
> Zeige mir meine HubSpot-Deals in der Verhandlungsphase> Wie viele Kontakte habe ich in Brevo?Anwendungsfall 1: CRM-Kontaktsynchronisierungs-Agent
HubSpot-Kontakte mit Deal-Stage-Anreicherung zu Brevo synchronisieren:
---name: hubspot-contact-syncdescription: Sync HubSpot CRM contacts to Brevo with deal data enrichmentversion: 1.0.0temperature: 0.1tools: - hubspot - brevo_contacts - brevo_attributes - brevo_lists - brevo_segmentstriggers: - schedule: "0 */4 * * *"---
# HubSpot Contact Sync
Read contacts and associated deal data from HubSpot,sync to Brevo with enriched attributes for segmentation.
## Strategy
1. Query HubSpot for contacts modified since last sync2. For each contact, fetch associated deals and company3. Create/update Brevo contact with enriched data: - CRM lifecycle stage → Brevo attribute - Deal amount → Brevo attribute - Deal stage → Brevo segment4. Auto-segment in Brevo: - "SQL" contacts → Sales Qualified list - "Opportunity" contacts → Active Pipeline list - "Customer" contacts → Customer list
## Field Mapping
| HubSpot Property | Brevo Attribute ||-----------------|-----------------|| email | EMAIL || firstname | FIRSTNAME || lastname | LASTNAME || phone | SMS || lifecyclestage | LIFECYCLE_STAGE || hs_lead_status | LEAD_STATUS || company (associated) | COMPANY || deal amount (sum) | DEAL_VALUE || deal stage (latest) | DEAL_STAGE |
## Rules- NEVER sync contacts without email addresses- ALWAYS preserve existing Brevo data if HubSpot field is empty- Track sync with events: hubspot_sync_success, hubspot_sync_error- Log contact count per lifecycle stage for reportingAnwendungsfall 2: Deal-Stage-Kampagnen-Agent
Brevo-Kampagnen basierend auf HubSpot-Deal-Stage-Änderungen auslösen:
---name: hubspot-deal-campaignsdescription: Trigger targeted Brevo campaigns when HubSpot deals change stagesversion: 1.0.0temperature: 0.3tools: - hubspot - brevo_contacts - brevo_email_campaign_management - brevo_templates - brevo_segmentstriggers: - schedule: "0 9 * * *"---
# Deal-Stage Campaign Agent
Monitor HubSpot deal stages and trigger appropriateengagement campaigns in Brevo.
## Stage-to-Campaign Mapping
| HubSpot Deal Stage | Brevo Action ||-------------------|--------------|| Appointment Scheduled | Send meeting prep email with company info || Qualified to Buy | Add to "Nurture" drip sequence || Presentation Scheduled | Send case study relevant to their industry || Decision Maker Bought-In | Send ROI calculator + pricing guide || Contract Sent | Send "What to expect" onboarding preview || Closed Won | Trigger welcome sequence + onboarding || Closed Lost | Add to "Win-back" sequence (30-day delay) |
## Rules- ONLY send to contacts associated with the deal- Check if contact has opted in to marketing before sending- One campaign trigger per deal stage change (no duplicates)- Log all campaign triggers for deal attributionBeispiel: Natürlichsprachige Abfrage
You: "Find all HubSpot deals that closed this month and make sure those contacts are getting our onboarding email sequence in Brevo."
Claude: Querying HubSpot for deals closed this month...[Uses hubspot MCP to search deals with closeddate in current month]
Found 12 deals closed this month, involving 18 contacts.Checking Brevo for these contacts...[Uses brevo_contacts to look up each email]
Results:- 14 contacts already in Brevo and receiving onboarding sequence- 4 contacts not yet in Brevo
Creating 4 new Brevo contacts and adding to onboarding list...[Uses brevo_contacts to create contacts][Uses brevo_lists to add to "Onboarding" list]
Done. All 18 contacts from this month's closed deals are nowin Brevo's onboarding sequence.Nächste Schritte
- Shopify + Brevo, E-Commerce-Integration
- Stripe + Brevo, Zahlungs-Event-Integration
- Agent-Spezifikation, Agent-Verhalten anpassen