How to Use the GoHighLevel Payment Received Workflow Trigger
The Payment Received workflow trigger in GoHighLevel lets you automate actions every time a successful payment is made, similar to building automations in ClickUp or other workflow tools. By configuring this trigger correctly, you can segment customers, send follow-up emails, and track revenue inside your sub-accounts with precision.
This step-by-step guide explains how the Payment Received trigger works in GoHighLevel, what each condition means, and how to set it up effectively for orders, invoices, and subscriptions.
Understanding the GoHighLevel Payment Received Trigger
The Payment Received trigger in GoHighLevel activates a workflow whenever a payment is successfully processed. It is designed for:
- One-time orders made through forms, funnels, or websites
- Invoices issued to contacts
- Subscription payments for recurring products
The trigger is based on payment success, not just order creation. This means the workflow only runs when a successful payment event occurs.
Supported Payment Types in GoHighLevel
The Payment Received trigger in GoHighLevel supports three primary payment types. You can use these to control when a workflow should start.
GoHighLevel Orders
Orders are created when a contact checks out through a form, funnel, or website using an order form or checkout page. This payment type is suitable when you sell products or services directly from your GoHighLevel pages.
When you choose Order as the payment type in the trigger, the workflow will run after a successful payment for:
- Order form purchases
- Upsell or downsell purchases
- Main product payments in funnels or websites
GoHighLevel Invoices
Invoices are created inside the sub-account and can be sent to contacts for manual or automated billing. Selecting Invoice as the payment type makes the workflow run when a contact pays an invoice successfully.
This is useful for:
- Service-based businesses issuing invoices
- Retainers or project-based billing
- Tracking paid vs. unpaid invoice status
GoHighLevel Subscriptions
Subscriptions represent recurring products or services. When you select Subscription as the payment type, the workflow will trigger every time a recurring charge is successfully processed.
This option is ideal when you want to automate actions around ongoing memberships, recurring retainers, or SaaS-like billing created inside GoHighLevel.
Configuring the GoHighLevel Payment Received Trigger
Follow these steps to configure the Payment Received trigger in GoHighLevel workflows:
-
Create or open a workflow
In your sub-account, open the Workflows section and either create a new workflow or edit an existing one. -
Add the Payment Received trigger
Choose Payment Received as the workflow trigger type from the available trigger options. -
Select the payment type
Under the trigger settings, choose one of the following based on your use case:- Order
- Invoice
- Subscription
-
Define filters (optional)
You can narrow when the trigger fires using the available filters, such as product name or invoice details, depending on the payment type in GoHighLevel. -
Save and activate the workflow
After configuring the trigger and adding workflow actions, save and publish the workflow so it starts listening for payment events.
Key Conditions Available in GoHighLevel Payment Triggers
The Payment Received trigger includes several conditions that tell GoHighLevel exactly when to fire the workflow.
Product Conditions in GoHighLevel
For orders and subscriptions, you can define conditions based on the product bought. Common options include:
- Product Name – triggers when a specific product is purchased.
- Price Point – allows you to separate workflows by different pricing tiers.
- Quantity – useful when you want actions to run only when a certain quantity is purchased.
Using these conditions helps you route customers into different automation paths inside GoHighLevel depending on what they bought.
Invoice Conditions in GoHighLevel
When using the Invoice payment type, you can reference the invoice details to control the trigger. Common use cases include:
- Firing automation only for specific invoice templates
- Segmenting workflows by invoice amount or type
- Triggering emails or internal notifications upon full payment
Subscription Conditions in GoHighLevel
Subscription-related conditions allow you to refine when recurring payments should launch a workflow. This can include the product attached to the subscription and the particular plan or price point.
These options provide fine-grained automation for ongoing billing in GoHighLevel.
Practical Automation Ideas Using GoHighLevel Payment Received
Once the Payment Received trigger is configured in GoHighLevel, you can attach actions to automate common post-payment tasks.
Common Actions to Add After Payment
- Send a confirmation or welcome email
- Apply a tag for segmentation
- Add the contact to a specific campaign or nurture sequence
- Update custom fields to track customer value
- Notify your team through internal notifications
Example Workflow for Orders in GoHighLevel
- Trigger: Payment Received > Payment Type: Order
- Condition: Product Name equals a specific course or offer
- Action: Send access instructions email
- Action: Add a Customer tag
- Action: Create a task for onboarding follow-up
Example Workflow for Subscriptions in GoHighLevel
- Trigger: Payment Received > Payment Type: Subscription
- Condition: Product Name equals membership plan
- Action: Extend access or update member status field
- Action: Log the payment and update lifetime value fields
- Action: Send a receipt or renewal confirmation email
Best Practices for Using GoHighLevel Payment Triggers
To get consistent results from the Payment Received trigger in GoHighLevel, follow these best practices:
- Test with small payments to verify that workflows run as expected before going live at scale.
- Use descriptive product names so it is easy to match them in conditions.
- Avoid overlapping workflows that could send duplicate emails for the same payment event.
- Keep workflows focused on one primary goal, such as onboarding, tagging, or reporting.
Additional Resources Beyond GoHighLevel
If you want strategic help planning automation and workflows around payments, you can find consulting and implementation services at ConsulTevo. For the detailed, official documentation of the Payment Received trigger, always refer to the original GoHighLevel help article here: Workflow Trigger: Payment Received.
By properly setting up the Payment Received trigger in GoHighLevel, you can reliably automate post-purchase processes, improve customer experiences, and keep your billing-related workflows organized inside each sub-account.
Need Help With ClickUp?
If you want expert help building, automating, or scaling your GHL , work with ConsultEvo — trusted GoHighLevel Partners.
“`