Start free

Automations

Automations that know when to stop.

A sequence should not keep emailing someone who already replied, unsubscribed or bounced. SendRaven automations end themselves when the conversation says they should. Start one with an API call, when a contact joins an audience, or from an event your application emits.

Start sending freeRead the automations docs
The SendRaven raven holding an envelope

Exits

Every sequence ends when the conversation does.

Onboarding sequence

exit_on_reply

cancel_reason: replied

  1. Day 0Welcome emailsent
  2. Day 2Reply receivedthe sequence stops
  3. Day 7Follow-upcancelled

  • They replied. The sequence stops.

  • They unsubscribed. Future steps are cancelled, including sends already scheduled.

  • They bounced. The address is suppressed and nothing more is tried.

Automations end an enrolment on a reply by default (exit_on_reply), and also on an unsubscribe, a hard bounce or complaint, a topic opt-out, or a tag rule. Out-of-office and other automatic replies do not count as a reply.

A day-seven follow-up after a day-two reply is not automation. It's a bug with good scheduling.

Every automation trigger and exit

Topics

Let people opt down instead of disappearing.

Someone may want product updates but not the newsletter. Topics let each address choose the email it wants, without turning one unsubscribe into a total blackout. Transactional email stays transactional.

Email preferencesThe preference page
  • Newsletternewsletter: off
  • Product updatesproduct-updates: on
  • Receipts and security mailtransactional · always delivered
requestThe same choice, by API
POST /v1/topics/preferences
{
  "email": "maya@acme.com",
  "topics": {
    "newsletter": false,
    "product-updates": true
  }
}
How topics and email preferences work

Before and after

Before and after

BeforeStitched together from a send endpoint

  • Replies land in a shared inbox
  • An unsubscribe that still sends day three
  • A marketing opt-out that blocks receipts
  • All or nothing, so people press spam instead
  • A day-old domain blasting eighteen thousand

AfterWith SendRaven

  • Replies joined to the message they answer
  • Unsubscribe suppresses and cancels what is scheduled
  • Only bounces and complaints block every kind of mail
  • Topics: drop the newsletter, keep the invoices
  • Every new sending identity warmed up automatically

Why transactional and campaigns share one plan but never one reputation

FAQ

Questions about automations

Does SendRaven charge per contact?

No. SendRaven charges for emails sent, and contacts are $0. There is one meter on every plan, so growing an audience does not change the bill until you mail it.

Can SendRaven handle transactional and marketing email?

Yes, on one API and one plan. Adding a domain creates two sending identities, mail. for transactional and news. for marketing, each with its own reputation, so a complaint spike on a newsletter cannot stop a password reset.

What happens when someone replies to an automation?

The sequence stops for that person. Automations end an enrolment on a reply by default (exit_on_reply), and also on an unsubscribe, a hard bounce or complaint, a topic opt-out, or a tag rule. Out-of-office and other automatic replies do not count as a reply.

You send a raven. It comes back.

Give your agent a return address.

Start with 3,000 emails a month. Inbound included. Unlimited contacts. Human approval when you want it.

Start sending freeConnect MCP