Joins a contact list
Everyone added to the list from now on starts, whether they came from an import, a sign-up form, the API or a teammate.
CONTACT_ADDEDAutomations
Emails that send themselves, at the right moment for each person.
Welcome a new sign-up today, send a tip in three days and a check-in in a week. Set it up once and Notix walks every person through it on their own clock.
Joins the Signups listStart
Welcome to AcmeEmail
Wait 3 daysWait
Three tips to get startedEmail
Wait 4 daysWait
How is it going?Email
The builder
Steps and paths, on one canvas
Add a step, fill it in, and branch where it matters. Every change saves on its own.
Build one here
An automation is a set of steps joined by paths. Each email step uses a template or one you write in place, filled with the event's data. Delay pauses; Wait for event holds until your app says something happened; If / else splits on a rule; Update contact and Add to segment keep your list up to date.
- Delays and waits from one minute to 30 days
- Each email can come from a different verified address
- Send SMS is coming soon and is marked that way in the builder
Starts when someone joins the Signups list
- Email Welcome to Acmeat once
- Wait 3 dayswait
- Email Three tips to get startedday 3
2 emails, the last one day 3. Each person moves through on their own clock.
steps for notix.automations.create3 steps
steps: [
{ type: "EMAIL", from: "Acme <hello@acme.com>", subject: "Welcome to Acme" },
{ type: "WAIT", seconds: 259200 },
{ type: "EMAIL", from: "Acme <hello@acme.com>", subject: "Three tips to get started" },
]Who gets it
Start when someone joins, or when your app says so
Three ways in, and an optional segment to narrow it down.
Your app enrols them
One call per person, at the moment that matters to your product, such as a trial with three days left.
APIYour app sends an event
Send payment.failed or order.shipped from your app. Every automation on that event starts, and its data goes into the emails.
EVENTOnly a segment
Limit it to people who match a segment, and let them leave early when they stop matching.
exitWhenLeavesSegmentnotix.automations is the same as notix.journeys
import { Notix } from "notix-js";
const notix = new Notix(process.env.NOTIX_API_KEY);
// Your app decides when someone starts, for example 3 days before a trial ends.
await notix.automations.enroll("jrn_trial_ending", {
email: "wanjiru@example.com",
});
pip install notix-sdk
from notix import Notix
notix = Notix() # reads NOTIX_API_KEY
notix.journeys.enroll("jrn_trial_ending", {"email": "wanjiru@example.com"})
composer require usenotix/notix-php
<?php
use Notix\Notix;
$notix = new Notix(getenv('NOTIX_API_KEY'));
$notix->journeys->enroll('jrn_trial_ending', ['email' => 'wanjiru@example.com']);
/v1/automations and /v1/journeys are the same endpoints
curl -X POST https://app.usenotix.dev/api/v1/automations/jrn_trial_ending/enroll \
-H "Authorization: Bearer $NOTIX_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "wanjiru@example.com" }'
Recipes
Start from a goal, not a blank page
Each recipe arrives with its steps in place. Change what you like.
Six ready-made starting points
Pick a goal, choose who gets it and name it. The same recipes are in the API, so your code or your AI agent can set one up too.
create-welcome.ts
const { data: welcome } = await notix.automations.createFromRecipe({
recipeId: "welcome",
name: "Welcome series",
triggerType: "CONTACT_ADDED",
contactBookId: "cb_signups",
fromEmail: "Acme <hello@acme.com>",
});
// Check every email, then turn it on.
await notix.automations.preflight(welcome!.id);
await notix.automations.activate(welcome!.id);
New automation
What's it for?Goal
Welcome new people
Help people finish setup
Rescue a failed payment
Remind before a trial ends
Win back quiet customers
Start from scratch
Results
See where people are and why they left
Review before it goes live, then follow every person through it.
A report for every automation
Review and activate checks every email first: a verified domain that is not paused, an unsubscribe link and nothing the deliverability check blocks. Once it runs, the report shows how many started, are in it now, opened and finished.
- A funnel of how many people reached each step
- Why people left early, grouped by reason
- Pause, resume or archive; people pick up where they left off
- The
journey.enrolled,journey.completedandjourney.exitedwebhook events
Welcome series
Joins the Signups listStarted1,284
In it now312
Opened61%
Finished903
StepReached
Email: Welcome to Acme1,284
Wait 3 days1,201
Email: Three tips to get started1,118
Wait 4 days1,010
Email: How is it going?903
FAQ
Questions, answered
What can an automation do today?
Six kinds of step: Send email; Delay, from one minute to 30 days; Wait for event, which holds until your app sends an event or the time runs out; If / else, which splits into a yes path and a no path on a rule about the event or the contact; Update contact; and Add to segment. Send SMS shows in the builder as Coming soon and does not run yet.
How does someone start an automation?
They join a contact list (by import, sign-up form, API or by hand), your app sends an event such as payment.failed (POST /v1/events), or your app enrols them with one API call. People already in the list when you turn it on do not get it.
Can I limit an automation to a segment?
Yes. Pick a segment of the list and only matching people start. Turn on Stop for people who leave the segment and anyone who stops matching leaves early.
What happens when someone unsubscribes partway through?
They leave the automation and get nothing more from it. Every email carries the same unsubscribe handling as a broadcast, and the report groups everyone who left early by the reason.
Can I test an automation without waiting for days?
Yes. Send me a test puts every email in your own inbox at once, with the waits skipped and [Test] in the subject. Tests do not count toward your plan.
Can someone go through the same automation twice?
For an automation that starts on a list or by enrolment, a person holds at most one run, so enrolling them again is refused with a 409. One that starts on an event starts again on a later event, but never while they are still in it and at most once an hour. An Idempotency-Key header makes a retry safe for 24 hours.
More features
Works with the rest of Notix
Broadcasts
Write a broadcast in the editor or start from a template, send it to a list or segment now or on a schedule, and read the results.
Explore BroadcastsTemplates
A block editor for email, 54 starter templates across 14 industries, and variables you fill in from the API or a broadcast.
Explore TemplatesAudience
Contact books, custom properties, segments and topics people can opt in and out of, all behind the same API key.
Explore AudienceTurn on your welcome series today.
Start from a recipe, add your emails and test it in your own inbox before anyone else gets it.