Most email marketing work happens inside the arrobaMail panel, without writing a line of code. But some businesses need the platform to talk to their own systems: a purchase in the store should create a contact, a sign-up in an app should trigger a welcome email, or an AI assistant should check your campaigns on your behalf.
This guide is an orientation: it explains in plain terms what the paths to integration are, when each one makes sense, and where to go for the technical detail. The programming part lives in the specialized sections — built for your technical team or your developer.
Tip: if you don't need to connect arrobaMail to another system, you can skip this section without missing anything. Everything essential for day-to-day use happens from the panel.
Is integration worth it for you?
It makes sense to connect arrobaMail to your systems when:
- An e-commerce store or CRM needs to create or update subscribers in real time.
- You want to trigger automatic emails based on events happening outside the platform (a purchase, a sign-up, a payment).
- Your team builds its own dashboards with your campaign metrics.
- You work with an AI assistant (like Claude or Cursor) and want to operate your account from there.
There are four paths, and you pick based on the case. All of them start from the same place: the integration overview.
1. The API: connecting your systems by code
The API v3 lets other systems operate arrobaMail automatically: create subscribers, create campaigns, check statistics, or trigger flows, without entering the panel. It's the path for custom integrations built by a developer.
It covers managing lists, campaigns, segments, senders, and automations. To understand the overview and use cases, there's API REST v3 for developers; for the detail of every available operation, the complete technical reference.
2. Webhooks: letting an external event trigger a flow
A webhook is a way for your system to notify arrobaMail when something important happens: a customer completed a purchase, someone signed up, a payment was declined. That notification can start an automation, add a tag, or send an email instantly, with no manual intervention.
It's what connects your store or your app to your automations. How to configure it is covered in the integration section.
3. Transactional sends: one-to-one emails
Transactional emails are individual messages triggered by a specific action: a purchase confirmation, a password reset, a receipt. They're not commercial campaigns; they go to a single person in response to something they did.
It's best to send them from an address separate from your campaigns, to protect the reputation of both channels. The implementation detail is covered alongside the API.
4. MCP: operating your account with an AI assistant
If you use an AI assistant like Claude, Cursor, VS Code, or Windsurf, you can connect it to arrobaMail via MCP (an open standard) and ask it things in natural language: "show me the status of my latest campaigns," "add these contacts to the list." The assistant queries your account in real time and responds — without writing code.
It's the most accessible path for frequent lookup and assisted management tasks. Everything is in MCP: arrobaMail for AI assistants.
Which one to choose
| Path | For whom | How it's used | Where to go deeper |
|---|---|---|---|
| API v3 | Developers | Code (custom integrations) | /api · /api/referencia |
| Webhooks | Technical teams | External events that trigger flows | /integracion |
| Transactional | Technical teams | One-to-one emails from your system | /api |
| MCP | Any user with an AI assistant | Natural language from Claude, Cursor… | /mcp |
Important: to create campaigns or send emails from any integration, the sender you use has to be verified and certified on the account. If it isn't, the send won't go through. Revisit sender verification if needed.
Not sure where to start? The integration overview brings together all four paths and helps you choose based on your case.