One event in.
A sequence out.
Send Plunk an event when something happens in your product. The emails, the waiting and the branching happen here.
What a step can do
Events, not schedules
Workflows start from something a contact did. Send the event from your app with one API call and the flow takes over from there.
Delays that respect the clock
Wait an hour, a day, or until a specific point in the future. Contacts sit in the delay without holding a connection open.
Branching on real data
Split a flow on contact fields, on custom data you have attached, or on whether an earlier email in the same flow was opened.
Webhooks out
A workflow step can call your own systems, so an email sequence can also update a CRM or kick off work elsewhere.
Re-entry, decided by you
Choose whether a contact who triggers the same event twice runs the flow twice or is ignored the second time.
Building one
- Step 01
Pick the trigger
Any event you already track starts a workflow: a signup, a purchase, a plan change. Contacts enter the moment the event fires.
- Step 02
Compose the flow
Drag in emails, delays, conditions and webhooks. Branches split on contact data or on how someone responded to an earlier step.
- Step 03
Turn it on
Every run is visible while it happens, so you can see where a contact is in the flow and what the next step will be.
Three that people build first
Onboarding
Walk a new signup through the product over their first week, and stop sending the rest of the sequence once they have done the thing it was nudging them toward.
user.signed-up → Welcome → Wait 2 days → Getting startedCart recovery
Follow up on an abandoned checkout while it is still live, then follow up again with an incentive if the first message goes unanswered.
cart.abandoned → Wait 1 hour → Reminder → Wait 1 day → DiscountRe-engagement
Catch contacts as they go quiet and branch on whether they opened the last thing you sent, so the dormant and the merely busy get different messages.
contact.inactive → If opened last email → Update / Offer
Frequently asked questions
What can trigger a workflow?
Any event you send Plunk from your own code, plus inbound email and contact changes. If your product can make an HTTP request when something happens, it can start a workflow.
Can a workflow branch on what someone did?
Yes. A branch checks a condition, such as whether an email was opened or a contact has a given field, and sends each answer down its own path.
What happens if someone enters a workflow twice?
You choose. A workflow can allow re-entry for things like abandoned carts, or run once per contact for things like onboarding.
Can I stop a sequence part way through?
Yes. A workflow can exit early when the contact does the thing it was nudging them toward, so nobody gets chased for something they already did.
Build your first workflow.
Free plan: 1,000 emails a month. Paid: $0.001 an email.