Start a Workflow When a Payment Is Received

The Payment Received trigger is a single entry point for money coming in, whether it is an invoice, an order form purchase, a subscription charge, or a paid booking. Use it to send receipts, update records, or alert your team to failures.

What it covers

It fires for one-time purchases, recurring charges, and invoice payments, and it can react to both successful and failed attempts. With filters, you decide exactly which of those should start the workflow.

Add filters

Click Add Filter, choose a filter, then add a sub-filter where one is offered.

• Payment Source: Invoice (sub-sources: text-to-pay link, one-time invoice, recurring template), Funnel or Website (one-step order form, two-step order form, upsell), or Calendar.
• Transaction Type: customer present (first transaction) or customer not present (subscription renewal).
• Calendar: a specific calendar by name.
• Global Product and Price.
• Payment Status: Success or Failed.

Example: for two-step order forms only, choose Payment Source > is > Funnel, then add Sub-Source > is > Two-step order form.

Branch inside the workflow

Add an If/Else and test product, funnel or website, calendar, source, payment status, or amount. Amount supports comparisons such as greater than, less than, or is empty.

Payment merge fields

Once the trigger is in place, your emails, texts, and notifications can include payment source, currency, total, subtotal, discount, tax, coupon code, creation date, and transaction ID, plus customer details (name, email, phone, address) and invoice details (name, number, issue and due dates, link).

Common recipes

• Send a thank-you message on a successful payment.
• Notify your team and message the customer when a payment fails.
• Move a subscriber's status field after a renewal.
• Tag high-value buyers when the amount exceeds a threshold.

Good to know: Create separate workflows for Success and Failed so each can use its own wording and follow-up timing.