Integrazione HubSpot + Brevo
HubSpot + Brevo
Collega i dati del CRM di HubSpot alla piattaforma di engagement di Brevo. Usa HubSpot come fonte di verità per i dati di contatti e trattative, e Brevo per l’esecuzione delle campagne multicanale, email, SMS, WhatsApp.
Server MCP utilizzati
| Server | URL | Autenticazione | Scopo |
|---|---|---|---|
| HubSpot MCP | mcp.hubspot.com | OAuth/PKCE | Dati CRM: contatti, aziende, trattative, ticket, prodotti, ordini (sola lettura) |
| Brevo MCP | mcp.brevo.com/v1/brevo/mcp | Token | Contatti, email, SMS, WhatsApp, campagne, tracciamento eventi |
Caution
Il server MCP di HubSpot al momento è in sola lettura (BETA). Puoi leggere i dati del CRM da HubSpot e usarli per guidare le azioni in Brevo, ma non puoi scrivere di nuovo su HubSpot tramite MCP. Per una sincronizzazione bidirezionale, usa l’API REST di HubSpot insieme alla connessione MCP.
Configurazione
Passaggio 1: crea un’app di autenticazione MCP in HubSpot
- In HubSpot, vai su Development > MCP Auth Apps
- Fai clic su Create MCP auth app
- Imposta il tuo URL di reindirizzamento (per i test con Claude Desktop:
http://localhost:6274/oauth/callback/debug) - Annota il tuo Client ID e il tuo Client Secret
Passaggio 2: collega entrambi i server MCP
Per gli strumenti che supportano OAuth (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
Il server MCP di HubSpot richiede OAuth con PKCE. Strumenti come Cursor lo gestiscono in modo nativo. Con Claude Desktop o Claude Code potrebbe servirti ottenere un token separatamente e passarlo come token Bearer.
Passaggio 3: verifica
> Show me my HubSpot deals in the Negotiation stage> How many contacts do I have in Brevo?Caso d’uso 1: agente di sincronizzazione dei contatti CRM
Sincronizza i contatti di HubSpot con Brevo arricchendoli con la fase della trattativa:
---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 reportingCaso d’uso 2: agente per le campagne legate alla fase della trattativa
Attiva campagne Brevo in base ai cambi di fase delle trattative in HubSpot:
---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 attributionEsempio: interrogazione in linguaggio naturale
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.Passaggi successivi
- Shopify + Brevo, l’integrazione e-commerce
- Stripe + Brevo, l’integrazione con gli eventi di pagamento
- Specifica degli agenti, personalizza il comportamento degli agenti