Feature

Marketing Automation Tools for Email

Send the right email when your customer acts, not when a calendar says so. Autoresponders, self-updating segments, recurring campaigns and API-driven workflows — on India-hosted infrastructure, billed in INR with GST.

What is email automation?

Email automation means sending email based on what a subscriber does rather than on a date you pick. Someone signs up and a welcome message reaches them in seconds. Seven days later a follow-up goes out on its own. A subscriber who goes quiet for a month gets a nudge. You set the rule once, and it runs without you.

Event-triggered

Autoresponders fire on what a subscriber does, not on a date in your calendar.

Self-updating

Segments add and remove people automatically as they start and stop matching your rule.

Hands off

Recurring campaigns and A/B tests run and resolve themselves until you stop them.

What neuMails automates, and what it does not

“Marketing automation” can mean two different things, so we state the scope plainly.

neuMails automates email. That covers event-triggered sends, segmentation, recurring campaigns, A/B tests and API-driven workflows. We focus on the sending layer, and we do it in depth.

neuMails does not replace a CRM. If you need lead scoring, multi-channel journeys or sales handoff, use a CRM with an automation layer. Connect it to neuMails through our API, and neuMails will handle the email.

What you can automate

Set each of these up once. After that, they run without you.

Event-triggered sends

An autoresponder fires on an event, not a date. Someone subscribes, and the welcome email reaches them in seconds. Seven days later, a follow-up goes out on its own. A subscriber goes quiet for a month? A re-engagement nudge finds them. You can even send a birthday message, pulled from a custom field you already store.

Each person moves through the sequence at their own pace. Nobody gets an email meant for someone else’s timeline.

Recurring campaigns

Some content has a rhythm. A weekly digest. A monthly statement. A quarterly update. Schedule it once and it keeps going, hands off, until you tell it to stop. For high-volume sends, see bulk email.

Segments that update themselves

Most segments go stale the day you build them. Ours don’t. Set a rule once — plan tier, city, last opened, purchase date. New subscribers who match the rule join the segment automatically. Those who stop matching leave it. Your list stays current without anyone exporting a spreadsheet on a Friday evening. Full list and campaign tooling sits on the email marketing page.

A/B tests that pick their own winner

Test subject lines, sender names or the full email body across different versions. The platform watches opens and clicks, picks the winner, and sends it to the rest of your list. You check the result. You don’t have to babysit the test. Results appear in email analytics as they come in.

API-driven workflows

API keys let your own application talk to neuMails directly. Your product can add subscribers, create campaigns and read reports without anyone logging in.

On signup

Add a subscriber the moment someone signs up in your product.

On any event

Trigger a campaign from an event in your own system.

Into your dashboard

Pull reporting into an internal dashboard your team already uses.

Full endpoint reference is on the email API page, and you can send the same mail over SMTP relay if that suits your stack better.

Webhooks into your systems

Information also flows the other way. Delivery, open, click, bounce, unsubscribe and complaint events push into your systems in real time. If your endpoint is down for a moment, we retry automatically. You don’t lose the event. Every one of those events is also queryable in email logs.

Automation that protects your sender reputation

Automated sending fails differently from manual sending. When a person clicks “send,” a person is watching. When a loop sends, nobody might be. A broken loop can mail the same subscriber forty times before anyone notices. By then, the damage is not only with that customer. It is with Gmail, Outlook and every other mailbox provider that now trusts your domain a little less.

So the safeguards are automated too:

  • Unsubscribes are processed automatically and blocked from every future send.
  • Hard bounces are suppressed in real time by our bounce servers, before the next automated send fires.
  • Feedback loop complaints suppress the person who complained as soon as the complaint arrives.
  • Email box monitors watch a mailbox and act on auto-replies, out-of-office loops and role-account bounces.
  • Per-campaign suppression lists keep a group of people out of one automated sequence, without blocking them from everything else.

Authentication is part of the same picture. SPF, DKIM and DMARC are set up with a guided DNS wizard, and seed list testing shows where your automated mail actually lands before you scale it.

Where the automation runs

Your email runs on AWS Mumbai (ap-south-1), in India.

Paid plans get dedicated IPs with automatic warmup. A new IP address has no history, so mailbox providers treat it with caution. Warmup raises your volume slowly, so the IP earns trust before it carries your full load.

Billing is in INR, with GST invoices. No currency conversion, no surprise forex charges on your card. See plans and pricing.

One more detail matters more than it seems. The same account carries your transactional and OTP traffic. So an automated campaign and a password reset share one suppression list and one sender reputation. An address that hard-bounced on Tuesday’s campaign is already known on Wednesday, whatever you send next.

Frequently asked questions

What is the difference between an autoresponder and a recurring campaign?

An autoresponder reacts to something a subscriber does, such as signing up. Each person receives it at their own time. A recurring campaign sends the same content to a list on a fixed schedule, such as every Monday.

Can automation trigger from events in my own application?

Yes. With an API key, your application can add subscribers and trigger campaigns when something happens in your product. Webhooks then send delivery and engagement events back to your systems in real time.

Does this replace a CRM?

No. neuMails handles email automation: triggered sends, segments, recurring campaigns and delivery. It does not do lead scoring or sales handoff. If you use a CRM, connect it to neuMails through the API.

What happens if an automated sequence hits a bounced address?

Hard bounces are suppressed in real time. The address is removed from future sends before the next automated email fires, so your sequence does not keep mailing a dead address.

Can I A/B test inside an automated sequence?

You can test subject lines, sender names and full email bodies. The platform picks the winner based on opens and clicks and sends it to the rest of the list.

Automation you set up once

Set the rules once, on infrastructure that stays in India. Start with 5,000 emails free every month — no card needed.

Get Started