Triggers reference
Complete list of triggers available in PayFacile workflows: order, payment, and subscription events. Each trigger explained with its execution context.
How triggers work
Every workflow starts with a trigger. It is the event that starts the sequence execution. You choose one trigger per workflow when creating it.
When the event occurs, PayFacile automatically runs all workflow actions in the defined order.
New order
Fires when: a customer completes an order (one-time payment or first payment of a subscription).
Use cases: send a welcome email, notify your team via webhook, start an onboarding sequence.
Payment received
Fires when: a payment is successfully collected (first payment or subscription renewal).
Use cases: confirm payment receipt, update an external tool via webhook, send a thank you message.
Payment failed
Fires when: a payment attempt fails (declined card, insufficient funds, rejected direct debit).
Use cases: send a reminder to update payment method, alert your team, start a dunning sequence.
Subscription started
Fires when: a new subscription begins (after the first successful payment).
Use cases: send access instructions, notify a membership management tool.
Subscription suspended
Fires when: a subscription is suspended (unpaid or manual action).
Use cases: inform the customer about the suspension, offer payment assistance, alert your team.
Subscription terminated
Fires when: a subscription is permanently terminated (cancellation by the customer or by you).
Use cases: send a cancellation confirmation email, offer a retention deal, notify your CRM.
Subscription renewed
Fires when: a subscription renews successfully (recurring payment collected).
Use cases: thank the loyal customer, send exclusive content, update your external tools.
