Email Automations API for Onboarding Sequences

On Pro and Custom, NoticeAPI sends template sequences when a contact enters an audience. Use them for short welcome, onboarding, and lifecycle flows with unsubscribe state built in.

Create account Read automation docs

Create an onboarding sequence

curl -X POST https://www.noticeapi.com/api/v1/automations \
  -H "Authorization: Bearer ntc_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Welcome flow",
    "audienceId": "aud_xxxxxxxx",
    "fromAddress": "[email protected]",
    "steps": [
      { "delayMinutes": 0, "templateId": "tpl_welcome" },
      { "delayMinutes": 4320, "templateId": "tpl_tips" }
    ]
  }'

Audience trigger

A contact entering the selected audience starts the sequence.

Template steps

Each automation can send 1 to 5 template steps with relative delays.

Consent stops

Unsubscribed or suppressed contacts stop receiving automation steps.

Cron-driven delivery

Production sequences require the internal automation cron to run every minute.

Sequence anatomy

A small lifecycle engine, not a campaign maze.

A useful automation is a few understandable parts: audience trigger, template steps, relative delays, cron delivery, and recipient-state stops.

Read automation fields

Trigger

Contact enters an audience

Audience membership starts the run for subscribed contacts.

Step

Template sends now or later

Each step points at a stored template and waits the configured delay.

Cron

Due steps are processed every minute

The production cron turns pending sequence steps into actual sends.

Stop

Unsubscribe cancels future steps

Suppressed or unsubscribed contacts stop receiving lifecycle email.

From test send to production traffic.

Create templates

Build the messages that each step will send, including the variables you need.

Choose the audience

Contacts added to that audience enter the automation when it is enabled.

Set relative delays

Each step waits relative to the previous step; send immediately with delayMinutes 0.

Let the cron tick

The automations cron processes due steps and cancels runs for unsubscribed or suppressed contacts.

Lifecycle email with unsubscribe handling

Automations use the same consent guardrails as broadcasts. Templates get an unsubscribe URL for marketing and lifecycle messages, and suppressed contacts are canceled before sending.

Read the implementation.

Automation docsCreate sequences, manage steps, and understand the cron requirement.AudiencesContacts enter automations through audience membership.Email templatesBuild reusable messages for each sequence step.Acceptable useConsent rules for lifecycle and marketing sends.

Questions before you ship.

Can automations schedule one-off broadcasts?

Use broadcast scheduling for one-off audience sends. Automations are contact-triggered template sequences for onboarding and lifecycle messages.

What starts an automation?

Adding a contact to the automation's audience starts a run when the automation is enabled.

What stops an automation?

Pausing or deleting the automation stops future steps. Unsubscribed or suppressed contacts are canceled on the next tick.

Test it. Then send from a verified domain.

Free includes simulator testing and 3,000 emails per month. Production sending on Free needs activation and a verified domain.

Create your account Compare plans