{"id":1267,"date":"2026-03-17T10:55:38","date_gmt":"2026-03-17T10:55:38","guid":{"rendered":"https:\/\/onesystemcrm.com\/help\/?post_type=docs&p=1267"},"modified":"2026-03-17T10:56:23","modified_gmt":"2026-03-17T10:56:23","password":"","slug":"workflow-trigger-payment-received-2","status":"publish","type":"docs","link":"https:\/\/onesystemcrm.com\/help\/Supports\/workflow-trigger-payment-received-2\/","title":{"rendered":"Workflow Trigger – Payment Received"},"content":{"rendered":"

This article will show you how to use Payment Received workflow trigger to automate follow-up actions after any successful payment. Whether it\u2019s a one-time charge, subscription renewal, or invoice payment, you can streamline confirmations, updates, and team notifications, saving time and improving customer experience.<\/p>\n

\n

What is Payment Received Trigger?<\/strong><\/h1>\n

The Payment Received trigger allows you to initiate automated workflows when a payment is successfully made through your OneSystemCRM account. This includes payments from funnels, invoices, calendars, memberships, forms, and even manual entries. Whether it\u2019s a one-time transaction or a recurring subscription payment, this trigger lets you respond immediately\u2014without lifting a finger.<\/p>\n

This is an essential automation tool for reducing manual follow-up, confirming payments, and ensuring consistent communication with customers and internal teams.<\/p>\n

\n

Key Benefits of Payment Received Trigger<\/strong><\/h2>\n

Leverage automation to eliminate manual payment follow-ups, improve response times, and keep your CRM and team instantly updated. This trigger creates a seamless post-payment experience for both your business and your customers.<\/p>\n

    \n
  • Send Instant Confirmations:<\/strong>\u00a0Automatically deliver confirmation emails or SMS messages the moment a payment is processed, keeping your customers informed and reassured.<\/span><\/li>\n<\/ul>\n
      \n
    • Update Contact Records:\u00a0<\/strong>Apply tags, update custom fields, or trigger internal notes to reflect the customer\u2019s payment status in their profile without manual input.<\/span><\/li>\n<\/ul>\n
        \n
      • Notify Your Team Immediately:\u00a0<\/strong>Alert your sales, support, or fulfillment teams in real-time so they can take timely action after a successful transaction.<\/span><\/li>\n<\/ul>\n
          \n
        • Trigger Upsell or Membership Access:\u00a0<\/strong>Kick off sequences like upsell offers, bonus content delivery, or grant membership access based on the type of purchase.<\/span><\/li>\n<\/ul>\n
            \n
          • Automate Failed Payment Follow-Up:\u00a0<\/strong>Set up workflows to respond to failed transactions with retries, alerts, or personalized communication to recover lost revenue.<\/span><\/li>\n<\/ul>\n
              \n
            • Simplify Subscription & Invoice Tracking:\u00a0<\/strong>Track recurring payments or invoice completions and tie them to specific follow-up actions or CRM updates effortlessly.<\/li>\n<\/ul>\n
              \n

              How to Configure Payment Received Trigger<\/strong><\/h2>\n

              Setting up this trigger ensures your system responds to payments instantly. Here\u2019s a clear step-by-step guide to configure it efficiently and accurately.<\/span><\/p>\n

              Start a New Workflow<\/strong><\/h3>\n

              Navigate to Automation > Workflows in the left menu, then click\u00a0+ Create Workflow\u00a0<\/strong>in the top right.\u00a0From the dropdown, select Start from Scratch to begin building a custom workflow from the ground up.<\/span><\/p>\n

              <\/p>\n

              Select Trigger Type<\/strong><\/h3>\n

              Click + Add New Trigger to open the trigger options.\u00a0Scroll to the Payments section and choose Payment Received to begin building your payment automation.<\/span><\/p>\n

              <\/p>\n

              Name Your Trigger<\/strong><\/h3>\n

              Enter a clear and descriptive name for your trigger (e.g., \u201cPayment for Course Access\u201d).\u00a0Naming helps keep workflows organized and easily identifiable, especially when using multiple payment triggers.<\/span><\/p>\n

              <\/p>\n

              Add Filters<\/strong><\/h3>\n

              Click + Add filters to narrow down which payment events trigger this workflow. Filters allow you to target specific transaction types, sources, products, or statuses.<\/p>\n

                \n
              • Source Filter:<\/strong>\u00a0Specify where the payment originated. This helps tailor automation based on the payment channel used.<\/li>\n
              • Calendar:\u00a0<\/strong>Payment received from a calendar appointment booking.<\/li>\n
              • External:\u00a0<\/strong>Payment made through third-party sources like Stripe, PayPal, or external API integrations.<\/li>\n
              • Form:\u00a0<\/strong>Payment submitted through a form that includes a payment element.<\/li>\n
              • Funnel:\u00a0<\/strong>Payment made through a funnel page, such as a one-step or two-step order form.<\/li>\n
              • Invoice:<\/strong> Payment completed via an invoice sent through OneSystemCRM invoicing feature.<\/li>\n
              • Manual Payment:<\/strong>\u00a0A payment recorded manually inside the CRM.<\/li>\n
              • Memberships:\u00a0<\/strong>Payment triggered by access to a membership product or course.<\/li>\n
              • Website:\u00a0<\/strong>Payment made through the e-commerce Storefront (Products or Subscriptions).<\/li>\n<\/ul>\n

                <\/p>\n

                Choose Filter Criteria<\/strong><\/h3>\n

                Select from available standard fields like Global Product, Payment Status, or Source. These filters help you target specific types of transactions for precise workflow control.<\/p>\n

                <\/p>\n

                Filter by Product<\/strong><\/h3>\n

                Choose Global Product as your filter type and select the specific product name. This ensures the workflow only triggers when a payment is received for that exact product.<\/p>\n

                <\/p>\n

                Filter by Payment Status<\/strong><\/h3>\n

                Add a Payment Status filter and set it to Success. This ensures the workflow only runs when a payment is successfully completed.<\/p>\n

                <\/p>\n

                Filter by Source<\/strong><\/span><\/h3>\n

                Add the Source filter and set it to Calendar. This restricts the trigger to only activate for payments made through calendar-based bookings.<\/p>\n

                <\/p>\n

                Specify Calendar<\/strong><\/span><\/h3>\n

                Use the Calendar filter to select the exact calendar (e.g., \u201cPat\u2019s Calendar\u201d). This adds another layer of precision by tying the workflow to a specific booking calendar.<\/p>\n

                <\/p>\n

                Save the Trigger<\/strong><\/span><\/h3>\n

                Once all filters are applied, click Save Trigger to finalize your configuration. This locks in your criteria so the workflow only activates under the defined conditions.<\/p>\n

                <\/p>\n

                \n

                Frequently Asked Questions<\/strong><\/h2>\n

                Q: Can I filter by product or membership plan?<\/strong><\/p>\n

                Yes, use the Source and Sub-Source filters to pinpoint payments from specific funnels, calendars, or memberships.<\/p>\n

                Q: Can this trigger failed payments too?<\/strong><\/p>\n

                Absolutely! Use the \u201cPayment Status = Failed\u201d filter to create follow-up workflows for retries or dunning emails.<\/p>\n

                Q: Can I use Custom Values (like payment amount)?<\/strong><\/p>\n

                Yes, you can use dynamic fields like\u00a0{{Payment Amount}}<\/span>,\u00a0{{Transaction ID}}<\/span>, and others in emails or internal notifications.<\/p>\n

                Q: How do I test the trigger?<\/strong><\/p>\n

                Use sandbox payment environments or process a real payment with test products. Make sure your workflow is activated before testing.<\/p>\n

                Q: Can I combine this with other triggers?<\/strong><\/p>\n

                Yes! You can include multiple triggers in a single workflow or use If\/Else branches to split logic based on payment source or result.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

                This article will show you how to use Payment Received workflow trigger to automate follow-up actions after any successful payment. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_category":[55],"doc_tag":[],"class_list":["post-1267","docs","type-docs","status-publish","hentry","doc_category-payments-workflow-triggers"],"year_month":"2026-07","word_count":865,"total_views":"13","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"usamasaeed219","author_nicename":"usamasaeed219","author_url":"https:\/\/onesystemcrm.com\/help\/author\/usamasaeed219\/"},"doc_category_info":[{"term_name":"Payments Workflow Triggers","term_url":"https:\/\/onesystemcrm.com\/help\/Supports-category\/payments-workflow-triggers\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1267","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/comments?post=1267"}],"version-history":[{"count":2,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1267\/revisions"}],"predecessor-version":[{"id":1269,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1267\/revisions\/1269"}],"wp:attachment":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/media?parent=1267"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_category?post=1267"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_tag?post=1267"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}