Workflow Trigger - Payment received

The Payment Received trigger is designed to act as a centralized mechanism for capturing all incoming payments across the CRM, including one-time purchases, subscription charges, invoices, and more. It can be customized with filters, such as source type and transaction status, to target specific use cases. This trigger helps businesses automate tasks, streamline processes, and efficiently respond to real-time customer transactions.

Covered in this Article

What is the Payment Received Workflow Trigger, and what does it do?

What are some excellent usage cases for this, along with their benefits?

How to use the Payment Received Trigger?

Workflow Trigger Filtersfor Payment Received Workflow Trigger

If/Else Conditions for Payment Received Workflow Trigger

Custom Values for Payment Received Workflow Trigger

FAQs

Will this trigger include subsequent subscription payments as well?

How can I achieve the trigger for successful subsequent subscription transactions?

What does the Customer present/first transaction mean and the Customer not present/subscription transaction?

Will failed payments also be captured in this trigger?

I have configured the trigger and selected a specific product in the filters. Does this mean that the trigger will fire off when that product is sold anywhere?

What is the sub-source filter?

What is the Payment Received Workflow Trigger, and what does it do?

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.

What are some excellent usage cases for this, along with their benefits?

The Payment Received trigger offers numerous usage cases and benefits, helping businesses automate processes, improve customer experience, and gain insights from payment data. Some common usage cases and their benefits include:

Automated payment confirmation:Usage Case: Send customers automated confirmation emails or messages when Payment is processed.

Benefits: Enhances customer experience by providing instant payment confirmation, reduces manual tasks, and helps maintain clear communication with customers.

Subscription management:Usage Case: Automatically update subscription status in the system when a subscription payment is successful or failed.

Benefits: Ensures accurate and up-to-date subscription information, streamlines subscription management, and reduces manual intervention.

Dunning management:Usage Case: Automatically trigger dunning email sequences for customers with failed subscription payments.

Benefits: Improves revenue recovery by addressing payment failures promptly, reduces churn, and enhances customer retention.

Customer segmentation:Usage Case: