Zatražite rani pristup

Unesite ime i imejl adresu ili broj telefona. Poslaćemo vam detalje o pristupu platformi Tajo.

Prilagođeni API + Brevo integracija

Prilagođeni API + Brevo

Nema svaka platforma MCP server. Za WooCommerce, BigCommerce, Magento, sopstvene CRM sisteme ili bilo koji sistem sa REST API-jem, napravite konektorskog agenta koji povezuje vaše podatke sa Brevom.

Dva pristupa

Pristup 1: MCP server iz zajednice

Proverite da li za vašu platformu postoji MCP server iz zajednice:

PlatformaMCP iz zajedniceStatus
WooCommercewoocommerce-mcp-serverOdržava zajednica
BigCommerceProverite direktorijum MCP serveraVarira
MagentoProverite direktorijum MCP serveraVarira
SalesforceDostupno više opcijaAktivna zajednica
ZendeskDostupno preko Composio/ZapierAktivno

Ako server iz zajednice postoji, koristite ga na isti način kao i zvanične, dodajte ga u svoju Claude konfiguraciju uz Brevo MCP.

Pristup 2: Agent sa HTTP alatima

Za platforme bez MCP servera, napravite agenta koji koristi ugrađene HTTP mogućnosti Claude-a da direktno poziva REST API-je, a zatim upisuje podatke u Brevo preko MCP-a.

Izrada prilagođenog konektorskog agenta

Korak 1: Razumite izvorni API

Dokumentujte ključne endpoint-e koji su vašem agentu potrebni:

# Example: WooCommerce REST API
source_api:
base_url: "https://your-store.com/wp-json/wc/v3"
auth: Basic (consumer_key:consumer_secret)
endpoints:
- GET /customers # List customers
- GET /customers/{id} # Get customer details
- GET /orders # List orders
- GET /orders/{id} # Get order details
- GET /products # List products
- GET /coupons # List coupons

Korak 2: Definišite agenta

---
name: woocommerce-brevo-sync
description: Sync WooCommerce customers and orders to Brevo
version: 1.0.0
temperature: 0.1
tools:
- brevo_contacts
- brevo_attributes
- brevo_lists
- brevo_email_campaign_management
triggers:
- schedule: "0 */6 * * *"
- webhook: /agents/woocommerce/sync
method: POST
---
# WooCommerce → Brevo Sync Agent
Connect WooCommerce store data to Brevo for engagement campaigns.
## Source API
- **Base URL**: https://your-store.com/wp-json/wc/v3
- **Authentication**: Basic Auth with consumer key/secret
- **Key endpoints**: /customers, /orders, /products
## Sync Strategy
### Customer Sync
1. GET /customers?modified_after={last_sync_time}
2. For each customer:
- Map WooCommerce fields to Brevo attributes
- Create or update Brevo contact
- Add to appropriate list based on order history
### Order Event Sync
1. GET /orders?after={last_sync_time}&status=completed
2. For each order:
- Track "order_completed" event in Brevo
- Update contact attributes (order_count, total_spent)
- Trigger post-purchase campaign if applicable
## Field Mapping
| WooCommerce | Brevo Attribute |
|-------------|-----------------|
| email | EMAIL |
| first_name | FIRSTNAME |
| last_name | LASTNAME |
| billing.phone | SMS |
| orders_count | ORDER_COUNT |
| total_spent | TOTAL_SPENT |
| date_created | CUSTOMER_SINCE |
| role | CUSTOMER_TYPE |
## API Call Pattern
For each sync operation, the agent should:
1. Call WooCommerce REST API to fetch data
2. Transform the response to Brevo's expected format
3. Call Brevo MCP tools to create/update contacts
4. Log sync results for monitoring
## Rules
- Respect WooCommerce API rate limits (default: 25 req/10 seconds)
- ONLY sync customers with valid email addresses
- Implement incremental sync using modified_after parameter
- Store last sync timestamp for next run

Korak 3: Konfigurišite Brevo MCP

Povežite samo one Brevo module koji su vašem agentu potrebni:

{
"mcpServers": {
"brevo_contacts": {
"url": "https://mcp.brevo.com/v1/brevo_contacts/mcp",
"headers": { "Authorization": "Bearer your-brevo-token" }
},
"brevo_email": {
"url": "https://mcp.brevo.com/v1/brevo_email_campaign_management/mcp",
"headers": { "Authorization": "Bearer your-brevo-token" }
},
"brevo_lists": {
"url": "https://mcp.brevo.com/v1/brevo_lists/mcp",
"headers": { "Authorization": "Bearer your-brevo-token" }
}
}
}

Korak 4: Pokrenite agenta

You: "Sync all WooCommerce customers from the last week to Brevo
and add new customers to the Welcome Series list."
Claude: I'll sync your WooCommerce customers to Brevo.
Fetching customers modified in the last 7 days from WooCommerce...
[Makes HTTP GET to your-store.com/wp-json/wc/v3/customers?modified_after=...]
Found 67 customers. Syncing to Brevo...
[Uses brevo_contacts to create/update contacts]
[Uses brevo_lists to add 23 new customers to "Welcome Series"]
Sync complete:
- 67 customers processed
- 44 existing contacts updated
- 23 new contacts created → added to Welcome Series
- 0 skipped (all had valid emails)

Šablon: generički konektor za REST API

Koristite ovaj šablon za bilo koji REST API:

---
name: {platform}-brevo-connector
description: Sync {platform} data to Brevo for engagement
version: 1.0.0
temperature: 0.1
tools:
- brevo_contacts
- brevo_attributes
- brevo_lists
triggers:
- schedule: "0 */6 * * *"
---
# {Platform} → Brevo Connector
## Source API Configuration
- **Base URL**: {api_base_url}
- **Auth**: {auth_method} ({details})
- **Rate Limit**: {rate_limit}
## Data to Sync
### Contacts
- Source endpoint: {endpoint}
- Brevo mapping: {field_map}
- Sync frequency: Every 6 hours
- Incremental: Use modified_after / updated_since parameter
### Events
- Source endpoint: {endpoint}
- Brevo event name: {event_name}
- Trigger: When {condition}
## Sync Logic
1. Fetch changed records from source since last sync
2. Transform to Brevo format
3. Upsert contacts via brevo_contacts
4. Track events for campaign triggers
5. Log results and update sync cursor
## Error Handling
- Retry failed API calls 3 times with exponential backoff
- Skip individual records that fail validation
- Report errors in sync summary
- NEVER stop entire sync for single record failure

Kada napraviti pun MCP server

Ako primetite da istu platformu povezujete iznova i iznova, razmislite o izradi pravog MCP servera:

Dovoljan je agentNapravite MCP server
Jednokratne ili retke sinhronizacijeDnevna produkciona sinhronizacija
Izrada prototipa integracijeDeljenje unutar tima ili organizacije
Jednostavne operacije čitanjaSložene operacije u više koraka
Potrebno je manje od 5 API endpoint-aPotrebna je puna pokrivenost API-ja

Da biste napravili prilagođen MCP server, pogledajte MCP specifikaciju i Tajo Integration Builder za generisanje servera iz OpenAPI specifikacija.

Sledeći koraci

Zatražite rani pristup

Unesite ime i imejl adresu ili broj telefona. Poslaćemo vam detalje o pristupu platformi Tajo.

automatsko prepoznavanje
AI asistent

Zdravo! Pitajte me o dokumentaciji.