Billing automation that runs itself.
A workflow watches for something to happen and does something about it, without a person in the loop: email a customer when their payment fails, tag an account when it upgrades, pause a subscription at the end of a contract. You build it from a trigger, conditions, and steps, in a visual builder.
Starts on anything. Waits for anything.
- Three trigger kinds: an event, a recurring schedule in your timezone, or a date offset like three days before a contract ends
- Conditions branch: one path when they match, another when they do not
- Delays and waits are durable: a workflow can watch an invoice for a week, survive restarts, and resume exactly where it left off
- An approval step pauses until a teammate signs off, which makes sensitive automations safe instead of forbidden
Actions with real reach.
- Email the customer or your own team, from a template or composed inline
- Update fields, add and remove tags, send a payment request, apply a credit or a discount
- Pause or cancel a subscription when the conditions call for it
- Post a signed webhook to your own systems, with your headers and merge fields, every attempt recorded and retryable
- Notify a Slack channel through your connected workspace
Questions, answered.
What can start a workflow?
Three kinds of trigger: an event (a payment fails, a subscription is created), a recurring schedule in your timezone, or a date offset such as three days before a contract ends. Each workflow is scoped to a module, like customers or subscriptions, which decides its triggers and fields.
What can a workflow actually do?
Send a customer or internal email, update a field, add or remove a tag, send a payment request, apply a credit or a discount, pause or cancel a subscription, post a signed webhook to your own systems, or notify a Slack channel.
Can a workflow wait?
Yes, durably. It can delay for a set time, or pause until something happens, like the invoice being paid, with a timeout. Waits survive restarts and resume exactly where they left off, so a workflow can watch an invoice for a week without anyone babysitting it.
Can a human stay in the loop?
An approval step pauses the run until a teammate approves or rejects it. Use it to make sensitive automations safe, like asking someone to sign off before a write off, instead of banning the automation.
What happens when a step fails?
Every run is logged with each step's outcome. A failed webhook step records the response it got, and you can retry the run from its history.
Set it once. It runs itself.
Event and schedule triggers, durable waits, and every run on the record.