Skip to main content

Workflow Trigger - Payment Received

Overview​

The Payment Received trigger in Stack automates actions based on payments received through the CRM. This includes one-time purchases, subscription charges, and invoice payments. By using this trigger, businesses can streamline their processes, such as sending confirmation emails, updating records, or managing failed payments in real time. Customize it with filters like payment type, source, and transaction status to suit specific business needs.

Trigger Name​

Payment Received

Trigger Description​

The Payment Received trigger captures and acts on payment-related events within Stack workflows. Whether it's a successful transaction, a failed payment, or a subscription renewal, this trigger initiates automated actions such as sending notifications, updating subscription statuses, or managing dunning processes. Customize this trigger by filtering based on payment source, product, transaction type, and payment status.

Key Features​

  • Captures all types of payments: one-time, subscription, and invoices.
  • Supports real-time automation for both successful and failed payments.
  • Customizable with filters: source, product, and transaction status.
  • Automates responses like sending receipts, notifications, or triggering follow-ups.

How to Configure​

Step-by-Step Guide​

  1. Add the Payment Received Trigger:

    • In your workflow builder, select the Payment Received trigger from the list of available triggers.

  2. Name Your Trigger:

    • Provide a descriptive name for the trigger, such as "New Subscription Payment" or "Invoice Payment Received."

  3. Apply Filters (Optional):

    • Make your trigger more specific by applying filters. Available filters include:
      • Payment Source: Funnel, website, invoice, Text2Pay links.
      • Sub-Sources: Choose from options like a one-step order form, two-step order form, or upsell.
      • Transaction Type: Select between "Customer Present" (first transaction) or "Customer Not Present" (subscription/recurring).
      • Payment Status: Filter by successful or failed payments.

  4. Use If/Else Conditions (Optional):

    • Customize the workflow further by adding If/Else conditions based on payment details. For example, send different emails depending on whether the payment was successful or failed.

  5. Customize Actions Based on Payment Data:

    • Use Custom Values from the payment data (e.g., amount, product name, payment method) to personalize follow-up actions, such as sending confirmation emails, updating customer records, or notifying team members.

  6. Save and Activate:

    • Once configured, save and activate the workflow to start automating your payment-based processes.

Example​

Scenario​

A business wants to automatically send a confirmation email when a customer successfully makes a payment for an online course.

Workflow Setup​

  • Trigger: Payment Received
  • Name: "Online Course Payment"
  • Payment Source: Funnel
  • Payment Status: Success

Actions​

  • Send a confirmation email to the customer with course access details.
  • Update the customer record in the CRM with the payment status.
  • Notify the sales team about the successful payment.

Outcome​

When a customer successfully makes a payment via the two-step order form in the funnel, the workflow automatically sends them a confirmation email, updates their CRM record, and notifies the sales team.