The Payment Received trigger automates processes and actions based on incoming payments when used in a workflow. It can be configured to respond to specific payment events, such as successful or failed transactions or particular products and payment sources. Here are some detailed functionalities and use cases:

Workflow automation: The trigger initiates the Workflow whenever a payment is received, allowing for automated actions like sending confirmation emails, generating invoices, or updating customer records in a CRM.

Customization with filters: Users can apply various filters to the trigger, such as transaction type, payment source, or product. This enables the creation of targeted workflows for specific scenarios, like subscription renewals, or failed payments.

Real-time response: The trigger operates in real-time, enabling businesses to respond quickly to customer transactions. This can help improve customer satisfaction by providing immediate feedback or resolving issues promptly.

Conditional actions: By using if/else conditions in the Workflow, different actions can be executed depending on the payment characteristics, such as the amount, source, or transaction status.

Reporting and analytics: The trigger can capture payment data for analysis and reporting purposes. By monitoring incoming payments and their attributes, businesses can gain insights into sales performance, customer behavior, and potential areas for improvement.

Inside a workflow, add a workflow trigger called Payment Received.

Please Note:

Choosing a filter allows you to choose its respective Sub-filters the next time you add a filter to the same workflow trigger.

Workflow Trigger Filters 

for Payment Received Workflow Trigger

You can then make your Workflow trigger more specific using filters. Here is a table of all the available filters and sub-filters.

TriggerFilterOptions at Filter LevelSub-Filter Level 1Options at Sub-Filter Level 1OperatorsPayment ReceivedPayment SourceInvoiceSub-SourceText2Pay linkis, is notOne-time invoiceRecurring templateFunnel/ Website

Sub-SourceOne-step order formTwo-step order formUpsellTransaction typeCustomer present/first transaction
Customer not present/subscription transactionCalendarCalendarCalendar namesGlobal ProductGlobal product NamesPricePrices Names as per selected Global ProductPayment statusSuccess---Failed

If/Else Conditions for Payment Received Workflow Trigger

Once you have added your desired set of Filters and Sub-Filters to your workflow trigger, you can add an If/Else Condition for Payment if you need to branch out the Workflow based on certain conditions.