slug: brevo provider: Brevo generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Telecommunications min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 21 edges: - tag: program spec_file: brevo-program-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.92 evidence: POST /loyalty/config/programs createNewLP Create loyalty program; schema loyaltyProgram, LoyaltyProgramState reason: Operations define, publish and manage loyalty programs and member subscriptions, which is squarely loyalty programme administration under Customer Relationship Management. - tag: deals spec_file: brevo-deals-api-openapi.yml capability_id: BC-410.30 capability_id_l1: BC-410 capability_name: Opportunity & Pipeline Management confidence: 0.9 evidence: GET /crm/deals getAllDeals "Get all deals"; GET /crm/pipeline/details getPipelineStages "Get pipeline stages"; "Link and Unlink a deal with contacts and companies" reason: Explicit sales CRM deal and pipeline-stage lifecycle operations, which is opportunity and pipeline management. - tag: reward spec_file: brevo-reward-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.9 evidence: POST /loyalty/offer/programs/{pid}/offers createReward Create a reward; POST .../rewards/redeem redeemVoucher Create redeem voucher request reason: Creation, attribution, redemption and revocation of loyalty rewards and vouchers within a loyalty program — loyalty programme mechanics, not payments or product catalogue. - tag: tier spec_file: brevo-tier-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.88 evidence: POST /loyalty/tier/programs/{pid}/tier-groups createTierGroup; schemas TierGroupUpgradeStrategy, TierGroupDowngradeStrategy, TierTierRewardsItems reason: Configuration of loyalty tier groups, tiers, upgrade/downgrade strategies and assignment of contacts to tiers — loyalty programme structure management. - tag: balance spec_file: brevo-balance-api-openapi.yml capability_id: BC-420.40 capability_id_l1: BC-420 capability_name: Loyalty & Retention Management confidence: 0.85 evidence: GET /loyalty/balance/programs/{pid}/balance-definitions getBalanceDefinitionList; GET /loyalty/balance/programs/{pid}/contact-balances getContactBalances reason: All paths are under /loyalty/, defining point/reward balance types, limits and per-contact balances with transaction history — a loyalty programme engine, not treasury or billing balances. - tag: Email Campaigns spec_file: brevo-email-campaigns-api-openapi.yml capability_id: BC-400.60 capability_id_l1: BC-400 capability_name: Digital Marketing Management confidence: 0.8 evidence: POST /emailCampaigns createEmailCampaign Create an email campaign; POST /emailCampaigns/{campaignId}/sendNow Send an email campaign immediately reason: Full lifecycle and dispatch of email marketing campaigns — digital marketing / marketing automation execution. Some ambiguity vs. demand generation, hence 0.8. - tag: contacts spec_file: brevo-contacts-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.8 evidence: POST /contacts/attributes/{attributeCategory}/{attributeName} createAttribute Create contact attribute; GET /contacts/lists/{listId}/contacts Get contacts in a list reason: Contact record CRUD, custom attributes, lists, folders, import/export and segments — the customer/contact master data layer of the platform. - tag: emailCampaigns spec_file: brevo-email-campaigns-api-openapi.yml reanchored_from: brevo-emailcampaigns-api-openapi.yml capability_id: BC-400.60 capability_id_l1: BC-400 capability_name: Digital Marketing Management confidence: 0.8 evidence: POST /emailCampaigns createEmailCampaign "Create an email campaign"; "Send an email campaign immediately"; "Get an A/B test email campaign results" reason: Creation, scheduling, sending and reporting of marketing email campaigns is digital/email marketing execution. Some ambiguity between Digital Marketing Management and Demand Generation, so confidence is 0.8. - tag: whatsAppCampaigns spec_file: brevo-whatsapp-campaigns-api-openapi.yml reanchored_from: brevo-whatsappcampaigns-api-openapi.yml capability_id: BC-400.60 capability_id_l1: BC-400 capability_name: Digital Marketing Management confidence: 0.8 evidence: POST /whatsappCampaigns createWhatsAppCampaign Create and Send a WhatsApp campaign reason: Operations create, send, and report on WhatsApp marketing campaigns and manage message templates through approval — outbound digital messaging campaign execution, i.e. digital marketing rather than a support channel. - tag: user spec_file: brevo-user-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.78 evidence: POST /organization/user/invitation/send inviteuser Send invitation to user; POST /organization/user/update/permissions EditUserPermission Update permission for a user reason: Administration of organisation user invitations, revocation and per-feature permissions/privileges — identity and access administration. Note this is account admin for the vendor's platform, so it is an IT/security capability, not HR. - tag: webhooks spec_file: brevo-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.78 evidence: POST /webhooks createWebhook Create a webhook; POST /webhooks/export exportWebhooksHistory Export webhook history reason: Full CRUD over outbound webhook subscriptions with event lists, auth config, channel/type and delivery-history export — this is precisely the webhook & event subscription lifecycle capability the frame names, rather than generic plumbing to be discarded. recovered_from: sweep-20260829T005356Z-edges.json - tag: Contact Attributes spec_file: brevo-contact-attributes-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.75 evidence: GET /contacts/attributes List all contact attributes; POST /contacts/attributes/{attributeCategory}/{attributeName} Create a contact attribute reason: Defines and maintains the attribute/custom-field model for contact (customer) records — customer data structure management rather than campaigning or messaging. - tag: Contact Lists spec_file: brevo-contact-lists-api-openapi.yml capability_id: BC-420 capability_id_l1: BC-420 capability_name: Customer Relationship Management confidence: 0.75 evidence: POST /contacts/lists Create a contact list; POST /contacts/lists/{listId}/contacts/add Add contacts to a list reason: Organises customer contact records into lists used as campaign audiences. Clearly CRM-side contact data, but ambiguous between customer data management and segmentation, so L1 only. - tag: coupons spec_file: brevo-coupons-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.75 evidence: POST /couponCollections createCouponCollection 'Create а coupon collection'; POST /coupons 'Create coupons for a coupon collection' reason: Creation and management of coupon collections is promotional discount management for the ecommerce/loyalty layer. recovered_from: sweep-20260829T005356Z-edges.json - tag: smsCampaigns spec_file: brevo-sms-campaigns-api-openapi.yml reanchored_from: brevo-smscampaigns-api-openapi.yml capability_id: BC-400.60 capability_id_l1: BC-400 capability_name: Digital Marketing Management confidence: 0.75 evidence: POST /smsCampaigns createSmsCampaign Creates an SMS campaign; POST /smsCampaigns/{campaignId}/sendNow Send your SMS campaign immediately reason: Creation, scheduling, sending and reporting of outbound SMS marketing campaigns to recipient lists — marketing campaign execution via a digital channel. Some ambiguity between Digital Marketing and Demand Generation sub-capabilities. - tag: Messages spec_file: brevo-messages-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.72 evidence: POST /conversations/messages sendMessageAsAgent Send a message as an agent reason: Operations manage messages within live-chat conversations sent by an agent, i.e. inbound/outbound handling of customer contacts in Brevo's chat product. That is customer inquiry handling rather than campaign marketing; the 'Contacts' title is spurious per tag-splitting. recovered_from: sweep-20260829T005356Z-edges.json - tag: Email Templates spec_file: brevo-email-templates-api-openapi.yml capability_id: BC-400.60 capability_id_l1: BC-400 capability_name: Digital Marketing Management confidence: 0.7 evidence: POST /smtp/templates createSmtpTemplate Create an email template reason: Authoring and maintenance of reusable email templates used for marketing and transactional sends — marketing content/asset management within digital marketing; could also map to content marketing, hence 0.7. recovered_from: sweep-20260829T005356Z-edges.json - tag: WhatsApp Campaigns spec_file: brevo-whatsapp-campaigns-api-openapi.yml capability_id: BC-400 capability_id_l1: BC-400 capability_name: Marketing Management confidence: 0.7 evidence: POST /whatsappCampaigns createWhatsAppCampaign Create and send a WhatsApp campaign reason: Full CRUD plus send for marketing campaigns over WhatsApp — clearly marketing campaign execution. L2 is ambiguous between Digital Marketing Management and Demand Generation Management, so only L1 asserted. - tag: companies spec_file: brevo-companies-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.7 evidence: POST /companies createACompany Create a company; GET /crm/attributes/companies getCompanyAttributes; PATCH /companies/link-unlink/{id} linkAndUnlinkCompanyWithContactAndDeal reason: CRM company-record CRUD, custom attributes, bulk import and linking to contacts/deals — maintenance of the customer/account master record. Account Management (BC-410.20) is an alternative reading, hence moderate confidence. - tag: conversations spec_file: brevo-conversations-api-openapi.yml capability_id: BC-430.10 capability_id_l1: BC-430 capability_name: Customer Inquiry Management confidence: 0.7 evidence: POST /conversations/messages sendAMessageAsAnAgent Send a message as an agent; POST /conversations/agentOnlinePing Sets agent's status to online reason: Live-chat agent messaging to site visitors, automated pushed messages and agent presence — inbound customer contact handling. Contact Centre Operations (BC-430.30) is a nearby alternative given the agent-status endpoint. - tag: masterAccount spec_file: brevo-master-account-api-openapi.yml reanchored_from: brevo-masteraccount-api-openapi.yml capability_id: BC-4230.10 capability_id_l1: BC-4230 capability_name: Tenant Provisioning & Lifecycle confidence: 0.7 evidence: POST /corporate/subAccount "Create a new sub-account under a master account."; "Delete a sub-account"; "Update sub-account plan"; "Enable/disable sub-account application(s)" reason: Creation, plan assignment, feature toggling and deletion of sub-accounts beneath a master account is multi-tenant provisioning and lifecycle management. Some overlap with tenant configuration and SSO federation operations in the same tag, hence 0.7.