BigCommerce + Brevo Integration

BigCommerce + Brevo

Connect BigCommerce store data to Brevo’s engagement platform through MCP. Sync customers, trigger order-based campaigns, recover abandoned carts, and drive repeat purchases, all orchestrated by AI agents in Agentx.

MCP Servers Used

ServerPackage/URLAuthPurpose
BigCommerce MCPCommunity MCP serverAPI token (V3)Customers, orders, products, carts, channels
Brevo MCPmcp.brevo.com/v1/brevo/mcpTokenContacts, email campaigns, SMS, WhatsApp, event tracking

Tip

BigCommerce exposes a comprehensive V3 REST API. Use a community MCP server or the Custom API + Brevo pattern to connect BigCommerce data to Agentx alongside Brevo MCP.

Setup

Step 1: Create BigCommerce API Credentials

  1. In BigCommerce Admin, go to Settings > API > API Accounts
  2. Create a V3 API account with scopes: Customers (read), Orders (read), Products (read), Carts (read)
  3. Note your Store Hash, Client ID, and Access Token

Step 2: Connect Both MCP Servers

{
"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"
}
},
"bigcommerce": {
"command": "npx",
"args": ["-y", "bigcommerce-mcp-server"],
"env": {
"BIGCOMMERCE_STORE_HASH": "your-store-hash",
"BIGCOMMERCE_ACCESS_TOKEN": "your-access-token"
}
}
}
}

Step 3: Verify Connection

Ask Agentx:

> How many customers does my BigCommerce store have?
> How many contacts are in my Brevo account?

Agentx should use BigCommerce MCP for the first and Brevo MCP for the second.

Use Case 1: Customer Sync Agent

Sync BigCommerce customers to Brevo contacts with purchase history:

---
name: bigcommerce-customer-sync
description: Sync BigCommerce customers to Brevo contacts with order data
version: 1.0.0
temperature: 0.1
tools:
- bigcommerce
- brevo_contacts
- brevo_attributes
- brevo_lists
triggers:
- schedule: "0 */6 * * *"
- event: customer_created
- event: order_completed
---
# BigCommerce Customer Sync Agent
Synchronize customer data from BigCommerce to Brevo contacts.
## Strategy
1. Query BigCommerce for customers modified since last sync
2. For each customer, fetch order history from BigCommerce
3. Create or update Brevo contact with profile + commerce attributes
4. Segment into Brevo lists:
- New registrations → "Welcome Series" list
- Repeat buyers (2+ orders) → "Loyal Customers" list
- High-value (>$500 LTV) → "VIP" list
- Inactive (no order in 90 days) → "Win-Back" list
## Field Mapping
| BigCommerce Field | Brevo Attribute |
|------------------|-----------------|
| email | EMAIL |
| first_name | FIRSTNAME |
| last_name | LASTNAME |
| phone | SMS |
| company | COMPANY |
| date_created | SIGNUP_DATE |
| orders_count (computed) | ORDER_COUNT |
| total_spent (computed) | TOTAL_SPENT |
| last_order_date (computed) | LAST_ORDER |
| customer_group_id | BC_SEGMENT |
| accepts_product_review_abandoned_cart_emails | OPT_IN |
## Rules
- ONLY sync customers who have accepted marketing emails
- NEVER overwrite Brevo data if BigCommerce field is empty
- ALWAYS validate phone numbers to E.164 format before sync
- Track events: bc_sync_success, bc_sync_error

Use Case 2: Post-Purchase Campaign Agent

Trigger personalized post-purchase sequences from BigCommerce order data:

---
name: bigcommerce-post-purchase
description: Orchestrate post-purchase campaigns based on BigCommerce order events
version: 1.0.0
temperature: 0.3
tools:
- bigcommerce
- brevo_contacts
- brevo_email_campaign_management
- brevo_templates
- brevo_sms_campaigns
triggers:
- event: order_completed
- event: order_shipped
---
# BigCommerce Post-Purchase Agent
When a BigCommerce order completes or ships, trigger the appropriate engagement sequence in Brevo.
## Sequence Logic
### First-Time Buyers
1. Immediate: Order confirmation (transactional)
2. Day 3: Welcome email with brand story and product care tips
3. Day 7: How-to guide for purchased product category
4. Day 14: Review request with direct link
5. Day 30: Cross-sell based on purchased category
### Repeat Buyers
1. Immediate: Order confirmation
2. Day 3: Loyalty reward notification
3. Day 14: "Restock" reminder if consumable product
4. Day 21: Early access to new arrivals in preferred category
### High-Value Orders (>$200)
1. Immediate: Premium order confirmation
2. Day 1: Personal thank-you email
3. Day 3: SMS with tracking + styling/usage tips
4. Day 7: VIP program invitation
### Order Shipped
1. Immediate: Shipping confirmation with tracking link
2. +2 days: SMS tracking update
3. +5 days (estimated delivery): "How's your order?" check-in
## Rules
- ALWAYS check order status before sending, skip if cancelled/refunded
- NEVER send marketing to customers who haven't opted in
- Personalize with: product name, order number, customer first name
- Use Brevo template variables for dynamic content

Use Case 3: Abandoned Cart Recovery

Bridge BigCommerce cart data with Brevo messaging:

---
name: bigcommerce-cart-recovery
description: Recover BigCommerce abandoned carts via Brevo email, SMS, and WhatsApp
version: 1.0.0
temperature: 0.2
tools:
- bigcommerce
- brevo_contacts
- brevo_email_campaign_management
- brevo_templates
- brevo_sms_campaigns
triggers:
- event: cart_abandoned
conditions:
- cart_value: "> 30"
- time_since_activity: "> 1h"
---
# BigCommerce Cart Recovery Agent
Monitor BigCommerce abandoned carts and execute recovery sequences through Brevo.
## Recovery Sequence
1. **+1 hour**: Reminder email with cart contents and product images
2. **+24 hours**: If no open → SMS with short link to cart
3. **+48 hours**: If no recovery → Email with 10% discount code
4. **+72 hours**: If cart > $150 and no recovery → WhatsApp with personal message
## Cart Data to Include
- Product images and names (from BigCommerce)
- Cart total with currency formatting
- Direct checkout recovery URL
- Discount code (generated dynamically for step 3)
## Rules
- NEVER send to customers who already completed checkout
- ALWAYS check cart status before each step
- Maximum 4 touchpoints per abandoned cart
- Respect opt-out preferences per channel

Example: Natural Language Orchestration

With both MCP servers connected:

You: "Find BigCommerce customers who bought more than twice in the
last 3 months but aren't in my Brevo 'Loyal Customers' list.
Add them and trigger a loyalty reward email."
Agentx: Querying BigCommerce for repeat customers...
[Uses bigcommerce MCP to fetch customers with 2+ orders in last 90 days]
Found 67 repeat customers.
Checking Brevo list membership...
[Uses brevo_contacts to check "Loyal Customers" list]
29 customers are missing from the list. Processing...
[Creates/updates 29 contacts with ORDER_COUNT and TOTAL_SPENT]
[Adds 29 to "Loyal Customers" list]
[Triggers loyalty reward email template]
Done:
- 29 customers added to "Loyal Customers" list
- Loyalty reward emails sent to all 29
- ORDER_COUNT and TOTAL_SPENT attributes updated
- 38 were already in the list (skipped)

Next Steps

Request early access

Share your first name and an email address or phone number. We will follow up with Tajo access details.

automatic detection
AI Assistant

Hi! Ask me anything about the docs.