Send on the right trigger, every time
Journeys that fire on signup, purchase, or inactivity. Branching, delays, same templates.
How it works
From conversion to retention, automatically
A trigger, then a sequence. Branch on the contact. Same pipeline.
Event-driven triggers
Signup, purchase, inactivity. From events, webhooks, or activity.
Branch on the contact
Split on fields and segments. Not one blast for everyone.
Delays & wait steps
Wait an hour, a day, or until a condition is met.
Reuses your templates
Same templates, domains, and deliverability.
See it as it runs
Opens, clicks, conversions per step.
Questions
Common questions
Are automations available in Unitpost today?
No. Automations are on our roadmap and not yet available — there is nothing to turn on in your account. This page describes what we're building so you can tell us whether it fits before we ship it. Everything else on the platform works today: transactional sending, scheduled campaigns to a segment, contacts, topics, templates, inbound email, and webhooks.
What can I use for a welcome or drip sequence in the meantime?
Drive the sequence from your own code. Call POST /api/v1/email when your app decides someone should hear from you, with an optional scheduled_at up to 90 days ahead so you can queue a later message in the same request. Subscribe a webhook to delivery and engagement events, and let your existing job runner decide what to send next. Your logic stays in your app.
Can I schedule an email or a campaign without automations?
Yes, scheduling ships today and is separate from automations. Pass scheduled_at on POST /api/v1/email for a single message, or on a campaign to have it go out later; PATCH the email to cancel or reschedule it, and campaigns have their own cancel and reschedule endpoints. The horizon is 90 days ahead on paid plans and 7 days on free.
Will automations reuse my existing templates and domains?
That's the plan: an automation step is intended to send through the same published templates, verified domains, suppression list, and deliverability path you already use, rather than a parallel sending system. It isn't built yet, so treat this as design intent and not a shipped guarantee. When it lands, the same consent and suppression rules that gate campaigns today will gate automated steps.
How will I know when automations launch?
Join the waitlist from this page and we'll tell you when it's ready. There's no date to share yet, and we'd rather leave the page honest than put a quarter on it. If you have a specific journey you need — an onboarding series, a win-back, an inactivity nudge — telling us shapes what ships first.