Automations V2

Flows that work for you
while you focus on something else.

Name: arrobaMail — Automations V2
Brand: arrobaMail

Ask the AI to build the flow, or build it yourself visually with nodes and edges: the subscriber enters through a trigger, moves through the actions you define, and arrobaMail decides what happens next based on how they respond. Everyday flows need no code; advanced ones can connect via API and webhooks.

Try automations for free See how it works

Flow activeVisual builder

New subscriber

Trigger

Send welcome email

Action

Opened the email?

Condition

Yes

Send offer

Reminder

From an idea to a flow

Describe it in one sentence. The AI builds it.

Tell Amanda IA what you want to achieve and she proposes a complete, ready-to-launch flow — the same thing you'd build by hand dragging blocks, but in seconds.

Automation · Visual builder AI-assisted

Amanda IA

AI agent expert in email marketing

New subscriber

Trigger

Send welcome email

Action

Wait 2 days

Action

Opened the email?

Condition

Yes

Special offer

Reminder

Clicked?

Condition

Tag "high interest"

Action

Sales follow-up

Result

Flow activeContacts segmentedSales opportunities detected

Triggers

The event that brings the contact in: they subscribe, open, click, change a field, or have a birthday.

Actions

What the flow runs: send an email or campaign, wait, add/remove tags, notify, call a webhook.

Conditions and branches

Decisions based on behavior (did they open it? click it? do they have a tag?) that split the flow into different paths.

Use cases

Six flows almost every team uses.

Each case is a starting point. In the visual editor you adapt them to your product and audience. The platform handles the logic, you handle the content.

Welcome series

New subscribers get an educational sequence spread over several days, branching based on how they engage.

Trigger: subscription3-5 emails with waitsbranches by open

Cart recovery

If a customer abandons checkout, you send a reminder a few hours later and, if they still haven't bought, an offer the next day.

Trigger: abandoned cart webhookwaitpurchase conditionemail

Win-back for inactive contacts

Detect contacts who haven't opened in X days and enroll them in a re-engagement flow with incentives.

Trigger: "no opens in 60d" segmentincentive emailwaitmoves to low engagement

Staged onboarding

For products with a learning curve, send contextual tips based on the user's level.

Trigger: sign-upstage 1wait + usage conditionstage 2etc.

Post-purchase

After a purchase you trigger confirmation, usage instructions, a satisfaction survey and eventual cross-sell.

Trigger: completed purchase3-4 emails with waitssurvey

Transactional via API

Your system triggers operational emails (receipts, confirmations, password resets) by calling the arrobaMail API.

REST API v3 + two-way webhookstracked delivery just like campaigns

Connected to everything else

It's not a separate piece —
it uses everything you already have.

Automations draw on your lists, segments, templates, verified senders and the AI. You set it up once and it gets reused wherever you need it.

Lists and segmentation

Any list or V2 segment can be an entry point. Segment conditions are applied in real time when evaluating who enters the flow.

Trigger on joining a list
Trigger on entering a dynamic segment
Conditions based on custom fields

Campaigns and templates

Every email node reuses the same visual editor and templates you already built. No duplicate work between one-shot campaigns and flows.

Pre-designed and your own templates
Same verified sender
Built-in open and click tracking

API and webhooks

Flows fire outbound webhooks and receive inbound webhooks from your system. Transactional email via REST API v3 with JWT.

Two-way webhooks
REST API v3 with 11 modules
JWT authentication with rate limiting

AI applied

Amanda IA helps you generate the content for each step of the flow, suggest subject lines and review tone before you activate the automation.

Body and subject line generation
Tone improvement suggestions
Recommendations for each stage of the flow

Frequently asked questions

What people ask most about automation

No. The editor is visual: you drag nodes, connect them with lines and fill in each one's parameters using forms. If you want to integrate with your backend you can use the API and webhooks, but for email automations no code is needed.

You can have multiple automations active in parallel to cover different stages of your operation. Usage is deducted from your sending quota according to your plan.

Yes. You pause the flow and contacts stay at the last node they were on. When you reactivate it, they pick up right there. You can also manually remove specific contacts if needed.

Transactional emails go out via REST API v3: your system calls the endpoint with the contact's data and the template. The send is tracked just like a campaign, with metrics and logs available.

By default, the flow avoids re-enrolling a contact who already completed the sequence. You can change this behavior in the settings if your use case requires it (e.g. recurring reminders).

Yes. Automations can trigger on entry into a V2 segment, which supports condition groups and logical operators (AND, OR). The engine evaluates membership in real time.