CorebillFollow-ups that run
whether you're online or not.
A trigger, a condition, and the actions that follow — email, invoice, notification, webhook or Slack. Build it once and it keeps working.
Starts on the events that actually happen in Corebill.
Not a generic webhook you have to wire up yourself — pick a real event from your quotes, invoices, customers, payments or catalog.
Customers
- Customer created
- Customer updated
Quotes
- Quote created
- Quote sent
- Quote approved
- Quote rejected
- Quote expired
Invoices
- Invoice created
- Invoice sent
- Invoice paid
- Invoice overdue
- Invoice cancelled
Payments
- Payment received
Services
- Item created
- Item updated
Branch on real fields. Act with real side effects.
Conditions
Match all or any of a group of rules on a field coming from the event, the customer, the quote or invoice, the payment, the item, or a custom field.
It waits, it retries, and it remembers what happened.
Delays that resume on their own
Wait minutes, hours or days between steps — an invoice reminder two days after it's sent, a follow-up a week after a quote goes out. The flow picks up exactly where it left off, with no server to keep running in the meantime.
A full history, with retries
Every run is logged step by step — status, duration and what changed. A timeout or a 5xx/429 from a webhook retries automatically with backoff; a 4xx or a blocked destination fails fast instead of hammering it.
Start from a flow that already works.
Duplicate one and adjust the condition or the wording — you rarely need to build from a blank canvas.
Invoice from approved quote
quote.approved → create invoice → send emailPayment reminder
invoice.overdue → wait 2 days → send emailSlack alert on payment
payment.received → send Slack messageNotify the team on a new quote
quote.created → create notificationAutomations that outsiders can't hijack.
Privileged actions need a privileged role
Webhooks, Slack messages and email to a custom address can only be created or edited by an owner or admin.
Secrets stay masked
Webhook headers and Slack URLs show as •••••••• to anyone without admin rights, in the editor and in the execution log.
Unsafe destinations are blocked
Every outbound request is checked before it's sent — internal or private network addresses are refused outright.
Viewers can look, not touch
A viewer sees your workflows and their run history, but can't create, edit or turn one on.
Questions about Automations
No. You drag a trigger, a condition and one or more actions onto a canvas and fill in a form for each — the same nodes described on this page.
A transient failure — a timeout, a 5xx or a 429 — is retried automatically with backoff, up to three attempts. A 4xx or a blocked destination fails immediately instead of retrying.
No — those, along with email to a custom address, are privileged actions restricted to owners and admins. A member can still build flows with the other actions.
Yes. Delays can wait minutes, hours or days and resume exactly where they left off — there's no server that needs to stay running in between.
Every execution keeps a log per node — status, duration, what went in and what came out — so you can see exactly where it stopped and why.
Set up your first automation in a few minutes.
Start from the “Invoice from approved quote” template and adjust it to how your team actually works.