AI setup, human approval

Email automation that sets itself up. You approve every word.

Paste your website URL. SendHeron proposes the tag schema your product should emit, then drafts a full lifecycle suite in your brand voice: welcome, trial, win-back, cancel-save. You activate what you want, one sequence at a time.

Or read the API reference, 35 documented endpoints

Beta members get early access to the AI setup. We onboard in small batches and review every account.

app.sendheron.com/sequences

The SendHeron sequence builder showing a live churn-save flow: a tag trigger, a four hour delay, and conditions branching on cancellation reason into two different emails.
  • 4

    lifecycle journeys running in production

  • 35

    documented REST API endpoints

  • €29

    at 5,000 contacts

  • EU

    EU company, EU data residency

Journey and endpoint counts come from the published API reference and the sequences this product runs for PostFast. Pricing is indicative while the private beta is being set up.

How the setup runs

From a website URL to a lifecycle suite you can read

It runs once per project. Everything it produces is a draft: no sequence activates, and nothing sends, until you switch it on yourself.

  1. 01

    Paste your URL

    Your website, plus two questions about your product. That is the whole input.

  2. 02

    Approve the schema

    We read your site and propose the tags and events your product should emit. You edit that list and approve it.

  3. 03

    Read the drafts

    The full suite, drafted: sequences with real triggers, delays and branching, and finished emails in your brand voice.

  4. 04

    Activate what you want

    Review each sequence and switch on only the ones you want. Snippets show your developer how to wire every signal.

If your site cannot be read, a short description of your product works instead. Everything after that first step is identical.

AI setup wizard

Screenshot pending. The schema review step, with the proposed tags and events and the edit controls visible, and the drafted sequence list beside it.

POST /contacts/{id}/events
curl -X POST \
  https://api.sendheron.com/api/v1/contacts/$CONTACT_ID/events \
  -H "Authorization: Bearer $SENDHERON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "trial_started"}'

# 201. The signal is recorded, and any sequence the
# setup drafted against trial_started has just enrolled this contact.

Proof

It already runs a real product's lifecycle email

SendHeron sends every lifecycle email for PostFast: trial activation, win-back, churn save, and dunning.

Live churn-save sequence, production

  1. 01

    Trigger

    Our backend adds the tag cancel-pending the moment a cancellation starts.

  2. 02

    Delay

    Four hours. Long enough that the email does not arrive mid-decision.

  3. 03

    Condition

    Branch on why they cancelled: too expensive, not using it, or neither.

  4. 04

    Send

    A different email down each branch, answering the reason they gave.

That is the flow in the screenshot above, running against real cancellations. One sequence covers three outcomes, which is the whole argument for branching instead of four separate campaigns.

What you get

Everything the lifecycle needs, nothing it doesn't

Workspaces

Several products, one account, one subscription

A workspace is a whole separate project. Its contacts, tags, sequences, templates, sending domains and API keys belong to it and to nothing else, so a side project can sit next to the main product without either one seeing the other's data.

Each workspace owns

  • Contacts
  • Tags
  • Sequences
  • Templates
  • Sending domains
  • API keys
Unsubscribes are per project
Somebody who leaves one product's list is still subscribed to the other. Those are two separate consent relationships and we keep them that way.
Bounces are account-wide
A hard-bounced address is suppressed across every workspace you own, so one project's bad list can never burn a sibling project's sending reputation.

The AI setup runs per workspace, once for each project. This is built for founders and teams running several products of their own. It is not an agency tool yet: per-workspace member permissions do not exist, so there is no such thing as a client login.

Pricing at 5,000 contacts

What lifecycle email costs at 5,000 contacts, and what it does

Scroll to compare

Monthly cost and plan characteristics at 5,000 contacts
AttributeCustomer.ioLoopsMailchimpSendHeron
Monthly at 5,000 contacts$100$49$100€29
Billed onPeak profiles, objects includedSubscribed contactsTotal audience, unsubscribes includedContacts
Builds your suite from your websiteAI agent builds campaigns from a prompt, in productAgent tooling drafts single campaignsnot checkedYes, at setup, as drafts you approve
Separate projects, one subscriptionTwo workspaces on Essentials, billed togetherMultiple teams, billed separately per teamnot checkedYes, one subscription
Sequences includednot checkednot checkednot checkedUnlimited, every tier
EU data residencynot checkednot checkednot checkedEU company, EU data

Competitor prices checked on 2026-07-23, capabilities on 2026-07-29. Each name links to the vendor's own pricing page so you can verify it. Cells marked "not checked" are things we have not yet read off the vendor's page, and we would rather say so than guess.

See full pricing

Questions

The things people ask first

Short answers. If yours is not here, the address in the footer reaches a person.

Private beta

Built by the team behind PostFast. SendHeron has sent its lifecycle email since day one.

The sequences on this page are the ones that run our own trial activation, win-back, churn save and dunning. We onboard in small batches and review every account.