Home/HighLevel/Features/Workflows/HighLevel payment received trigger step by step configuration

Workflows and Automation

HighLevel payment received trigger step by step configuration

In short

The Payment Received trigger fires a workflow whenever a payment is recorded in HighLevel. It works for one time charges, subscription renewals, invoices, calendar bookings and manual entries, letting you automate confirmations, contact updates and internal alerts without manual effort.

AreaWorkflows · Section
Used forOnline course provider, Local service business, Ecommerce store
Setup steps10 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders of SaaS businesses who need instant confirmation emails after subscription renewals, keeping customers informed.
  • Small agencies that want to tag contacts and notify team members automatically whenever a client pays for a service.
  • Coaches or membership site owners who must grant access and send welcome material right after a payment is captured.

02Payment received triggers, explained

The Payment Received trigger starts a workflow each time HighLevel registers a successful payment. It covers payments from funnels, invoices, calendars, memberships, forms and manual entries. Once the trigger fires, any actions in the workflow, emails, SMS, tag updates, notes or internal alerts, run automatically.

The trigger lives inside the workflow builder under Automation > Workflows. After adding a new workflow, you select + Add New Trigger, scroll to the Payments section and choose Payment Received. From there you can apply filters to narrow the payment events that launch the workflow, such as product, source, status or specific calendar.

Filters are built from standard fields like Global Product, Payment Status and Source. By combining them you can target a single product, only successful payments, or payments that came from a particular calendar booking. Saving the trigger locks the criteria so the workflow runs only under those exact conditions.

03How businesses use the Payment Received trigger

  • Online course provider. Create a workflow that sends a welcome email with login details when a student pays for a course. Add a filter for the specific course product and set Payment Status to Success so the email fires only for completed transactions.
  • Local service business. Set up a workflow that tags a contact as "Paid" and notifies the scheduling team after a client pays through a calendar booking. Use the Source filter set to Calendar and select the appropriate booking calendar.
  • Ecommerce store. Configure a workflow that updates the order record and alerts fulfillment staff when a payment comes from the website storefront. Apply a Source filter of Website and filter by the sold product to keep inventory actions accurate.

04The numbers and rules that matter

  • Standard filter fields include Global Product, Payment Status, Source.
  • Order Submitted trigger requires V2 funnels; V1 users should use Payment Received.

05How to set up and use the Payment Received trigger in HighLevel

Configure payment received trigger

  1. Open Automation > Workflows from the left navigation and click + Create Workflow.
  2. Choose Start from Scratch from the dropdown to begin a new workflow.
  3. Select + Add New Trigger and scroll to the Payments section.
  4. Pick Payment Received as the trigger type.
  5. Enter a descriptive name for the trigger, such as "Payment for Course Access".
  6. Click + Add filters to open the filter selection panel.
  7. Add a Global Product filter and select the product that should start the workflow.
  8. Add a Payment Status filter and set it to Success to run only on completed payments.
  9. Add a Source filter, set it to Calendar, and then choose the specific calendar to target.
  10. Click Save Trigger to store the filter configuration.

06What it looks like in HighLevel

07Settings that matter

  • Source. Determines the origin of the payment, such as Calendar, External, Form, Funnel, Invoice, Manual Payment, Memberships or Website.
  • Calendar. Specifies the exact booking calendar whose payments should activate the workflow.
  • Global Product. Filters the trigger to run only when the payment is for the selected product.
  • Payment Status. Sets the required status of the payment, for example Success or Failed, before the workflow can fire.

08Things to know before you rely on it

  • There is no dedicated Stripe recurring charge trigger; recurring Stripe charges are captured by the Payment Received, Order Submitted or Subscription triggers.
  • Order Submitted trigger requires V2 funnels; V1 funnel users must rely on the Payment Received trigger.
  • All three payment triggers work with Stripe, PayPal and any other connected gateway, but they normalize events across gateways.

09How it connects to the rest of HighLevel

  • Learn how to use the Order Submitted trigger for post purchase automation. Order Submitted trigger
  • Set up Subscription trigger to react to subscription lifecycle changes. Subscription trigger
  • Use the Invoice trigger to start workflows when an invoice payment is recorded. Invoice trigger
  • Read the basics of workflow creation, including triggers, filters and actions. Workflow basics

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Payments are the lifeblood of any small business, but chasing receipts and updating records after every sale can eat up precious time. The first thing I would get right is the filter that locks the trigger to the exact product or service you sell, so you only fire the automation when it matters.

Once that filter is tight, the rest of the workflow runs itself. Sending confirmations, tagging the contact, and pinging your team. It’s a clean way to keep the sales funnel moving without lifting a finger.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about the Payment Received trigger.

Can I filter by product or membership plan?

Yes. Use the Source and Sub Source filters to narrow payments from specific funnels, calendars or memberships.

Can this trigger fire on failed payments?

Yes. Add a Payment Status filter set to Failed to launch a workflow for retries or dunning emails.

Are dynamic payment values available for use in emails?

Yes. You can insert fields such as {{Payment Amount}} and {{Transaction ID}} into messages or internal notes.

How can I test the trigger before going live?

Run a sandbox transaction or process a test payment with a test product, ensuring the workflow is activated.

Can I combine this trigger with other triggers in one workflow?

Yes. Multiple triggers can be added to a workflow, and If/Else branches can split logic based on payment source or result.

Is there a Stripe specific trigger for recurring charges?

No. Stripe recurring charges are captured by the generic Payment Received, Order Submitted or Subscription triggers.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.