Skip to content

Workflows · 2 min read

Payment Received Trigger

The Payment Received trigger starts a workflow whenever a payment comes in. That includes one-time purchases, subscription charges, invoices, and calendar bookings. Use it to send receipts, thank-you messages, or internal alerts, update contact records, or start onboarding.

Add the trigger

  1. Go to Automation > Workflows and open a workflow.
  2. Click Add New Trigger and choose Payment Received.
  3. Add filters to narrow it down, then save.
Once you pick a filter, its sub-filters become available the next time you add a filter.

Filters

| Filter | Options | Sub-filters | | --- | --- | --- | | Payment Source | Invoice | Sub-source: text-to-pay link, one-time invoice, or recurring template | | | Funnel/Website | Sub-source: one-step order form, two-step order form, or upsell | | | Calendar | Pick calendars by name | | Transaction Type | Customer present / first transaction, or customer not present / subscription transaction | | | Product | Pick a product | Pick its prices | | Payment Status | Success or Failed | |
Use is or is not with each filter.

Branch with If/Else

After the trigger, you can add an If/Else step to branch on the payment's product, funnel or website, calendar, source, status, or amount. For amounts, use comparisons such as greater than, less than, or equal to.

Custom values

These custom values are available in emails, SMS, and internal notifications:
  • Payment: {{payment.source}}, {{payment.currency_symbol}}, {{payment.currency_code}}, {{payment.sub_total_amount}}, {{payment.discount_amount}}, {{payment.coupon_code}}, {{payment.tax_amount}}, {{payment.total_amount}}, {{payment.created_on}}, {{payment.transaction_id}}, {{payment.payment_status}}, {{payment.gateway}}, {{payment.method}}, {{payment.card.last4}}, {{payment.card.brand}}
  • Customer: {{payment.customer.id}}, {{payment.customer.first_name}}, {{payment.customer.last_name}}, {{payment.customer.name}}, {{payment.customer.email}}, {{payment.customer.phone}}, {{payment.customer.address}}, {{payment.customer.city}}, {{payment.customer.state}}, {{payment.customer.country}}, {{payment.customer.postal_code}}
  • Invoice: {{payment.invoice.name}}, {{payment.invoice.number}}, {{payment.invoice.issue_date}}, {{payment.invoice.due_date}}, {{payment.invoice.url}}, {{payment.invoice.recorded_by}}

Common questions

Does it fire for subscription renewals? Yes. It fires for payments made on an order form and for subscription charges that happen in the background.
How do I catch only successful renewals? Set Payment Source to Funnel/Website, Transaction Type to Customer not present / subscription transaction, and Payment Status to Success.
What do the transaction types mean? "Customer present / first transaction" is the first payment, made by the customer at checkout. "Customer not present / subscription transaction" is a later subscription charge made automatically.
Are failed payments included? Yes, if you don't filter by status. Use the Payment Status filter to pick success or failed.
If I filter by a product, does it fire wherever that product sells? Yes. It fires for that product from any source unless you also filter by source.

Did this answer your question?

No, I need help

More in Workflows