The Refund Workflow Trigger allows you to automatically launch workflows when a refund occurs. This automation can be filtered by refund status, amount, type, and\/or source. It enables seamless responses to refund events like sending confirmation messages to customers or assigning internal tasks to team members.<\/p>\n
\n
Key Benefits of the Refund Workflow Trigger<\/strong><\/h2>\nAutomating actions around refunds helps you deliver better service, respond faster, and minimize manual work. These benefits enhance team efficiency while improving customer experience.<\/p>\n
\n- \n
Customer Notifications:<\/strong>\u00a0Automate refund confirmation messages via SMS or email to reduce support requests.<\/p>\n<\/li>\n- \n
Team Task Assignment:<\/strong>\u00a0Create follow-up tasks automatically to ensure your team acts promptly.<\/p>\n<\/li>\n- \n
Filtered Automation:<\/strong>\u00a0Launch workflows only when refunds meet specific criteria (amount, type, status, source).<\/p>\n<\/li>\n- \n
Improved Customer Satisfaction:<\/strong>\u00a0Deliver timely updates during refund processes to improve trust and retention.<\/p>\n<\/li>\n- \n
Proactive Handling of Failed Refunds:<\/strong>\u00a0Trigger alternative workflows when refunds fail, reducing churn risk.<\/p>\n<\/li>\n- \n
Efficient Operations:<\/strong>\u00a0Eliminate manual processes and ensure consistent handling of refund scenarios.<\/p>\n<\/li>\n<\/ul>\n
\nHow To Set Up a Refund Workflow Trigger<\/strong><\/h2>\nSetting up the Refund Workflow Trigger ensures\u00a0that your refund processes\u00a0are automated, timely, and customized to your specific business rules.<\/p>\n
Step 1:\u00a0<\/strong>Create New Workflow<\/u><\/h4>\n\n- Navigate to\u00a0Automation<\/strong> using the left-hand navigation bar in your sub-account<\/li>\n
- Click the\u00a0+ Create Workflow\u00a0<\/strong>button in the top-right corner to create a new workflow<\/li>\n<\/ul>\n
![\"\"](\"https:\/\/onesystemcrm.com\/help\/wp-content\/uploads\/2026\/03\/ZZBizO4XIRVc1NH8Wjf5KX_5aWgk20WDwQ11-scaled.png\")
<\/p>\n
Step 2:<\/strong>\u00a0Add Refund Trigger<\/u><\/h4>\n\n- \n
Name your workflow<\/p>\n<\/li>\n
- \n
Click\u00a0+ Add New Trigger<\/strong><\/p>\n<\/li>\n- \n
Search for and select the\u00a0Refund<\/strong>\u00a0trigger<\/p>\n<\/li>\n<\/ul>\n![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046717860\/original\/_jM5I_qQ61hfhV68VDDVWIITCg7sEk7viw.png?1747340170\")
<\/p>\n
Step 3:<\/strong>\u00a0Add Trigger Filters<\/u><\/h4>\n\n- \n
Click\u00a0+ Add Filters<\/strong>\u00a0at the bottom of the Workflow Trigger page<\/p>\n<\/li>\n- \n
Apply filters as needed (see next section for details on filter options)<\/p>\n<\/li>\n<\/ul>\n
![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046717891\/original\/cIciIyzT1MEerYNKPA916HLhjhZ8AgfKMQ.png?1747340235\")
<\/p>\n
Step 4:<\/strong>\u00a0Build Out Workflow<\/u><\/h4>\n\n- \n
Add actions based on your business needs (notifications, task assignments, etc.)<\/p>\n<\/li>\n
- \n
Click\u00a0Save<\/strong>\u00a0and\u00a0Publish<\/strong>\u00a0the workflow<\/p>\n<\/li>\n<\/ul>\n![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046717915\/original\/-hXp2tiTpSM_QZk532r_LDiDQB7NzU9xvA.png?1747340309\")
<\/p>\n
\nUsing Filters for Refund Trigger<\/strong><\/h2>\nFilters give you control over exactly when the refund workflow will activate, ensuring it’s only triggered by relevant refund scenarios. These filters can be used individually or stacked with each other to give you more control.<\/p>\n
\n- \n
Status:<\/strong> Filter based on refund status<\/p>\n\n- \n
Successful: Trigger only after a completed refund.<\/p>\n<\/li>\n
- \n
Failed: Trigger when a refund attempt fails.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
- \n
Amount:<\/strong> Filter based on refund value<\/p>\n\n- \n
Greater than, Less than, or Equal to a specific dollar amount (e.g., refund > $100)<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
- \n
Source:<\/strong> Filter based on where the refund originated<\/p>\n\n- \n
Options include Calendar, Communities, Payment Link, Invoices, Manual, and more.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n
- \n
Type:<\/strong> Filter based on the type of refund<\/p>\n\n- \n
Full Refund or Partial Refund<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046717990\/original\/mDbwWvTTVUB6cF4Ru3425UdHLU4TInLQXg.png?1747340454\")
<\/p>\n
\nAdding Actions to the Refund Trigger Workflow<\/strong><\/h2>\nAfter your trigger and filters are set, you can add various actions based on the desired outcome. These examples highlight common use cases.<\/p>\n
Tip: Refund custom values are also available inside the Payments section in Custom Values. This allows you to send include specific refund details within your messages.<\/span><\/pre>\n\n
Example 1:<\/u><\/strong>\u00a0Send a Confirmation Notification<\/u><\/h4>\n<\/h4>\n
A practical use case for the Refund Trigger is automating customer notifications. For instance, if a refund is processed successfully, an automated email can be sent to inform the customer of the successful transaction. Conversely, if a refund fails, a different automated message can be triggered to notify the customer of the issue and provide further instructions. This ensures timely communication and enhances customer satisfaction during potentially frustrating situations.<\/p>\n
![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046718045\/original\/0J6GrOtaNGaUA6OkEa1hWpGMBqpnxwuX-g.png?1747340637\")
<\/p>\n
Example 2:\u00a0<\/strong>Assign an Internal Task<\/u><\/h4>\nUse the Refund Trigger to create a task for your support or success team to follow up with a customer who received a refund.<\/p>\n
![](\"https:\/\/s3.amazonaws.com\/cdn.freshdesk.com\/data\/helpdesk\/attachments\/production\/155046718058\/original\/hVs5vFEY3YJ01ITG3iCZuPG4qaABWrFJjA.png?1747340670\")
<\/em><\/p>\n
\nFrequently Asked Questions<\/strong><\/h2>\nQ: Can the Refund Trigger handle multiple refunds for the same contact?<\/strong>
Yes. Each refund instance is treated as a new trigger event. By default, each refund event (even for the same customer) will trigger the workflow again.<\/p>\nQ: Will this trigger if I refund through Stripe directly or another external provider?<\/strong>
No. The refund must be issued inside HighLevel for the trigger to fire. The payment processors supported in HighLevel are Stripe, Authorize.net and NMI. The integration must be set up and the refund must go through HighLevel in order for the trigger to fire.<\/p>\nQ: How do I use this trigger for partial refunds only?<\/strong>
Add a condition to the trigger for Refund Type = Partial. You can use multiple conditions (like Refund Type + Refund Failed) to filter events even more accurately.
\n
\nQ: What happens if the refund fails?<\/strong>
The workflow can still fire based on the selected filters. Use the Refund Failed = True filter to manage cases where the refund fails. This is useful to notify team members of a failed refund.<\/p>\nQ: What if I want to notify internal teams instead of the customer?<\/strong>
You can use internal actions such as tasks or internal emails to notify internal teams of a refund.<\/p>\n","protected":false},"excerpt":{"rendered":"The Refund Workflow Trigger allows you to automate important tasks whenever a refund is issued. Whether you’re notifying customers, assigning […]<\/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-1274","docs","type-docs","status-publish","hentry","doc_category-payments-workflow-triggers"],"year_month":"2026-07","word_count":810,"total_views":"19","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\/1274","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=1274"}],"version-history":[{"count":1,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1274\/revisions"}],"predecessor-version":[{"id":1276,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1274\/revisions\/1276"}],"wp:attachment":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/media?parent=1274"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_category?post=1274"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_tag?post=1274"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Customer Notifications:<\/strong>\u00a0Automate refund confirmation messages via SMS or email to reduce support requests.<\/p>\n<\/li>\n Team Task Assignment:<\/strong>\u00a0Create follow-up tasks automatically to ensure your team acts promptly.<\/p>\n<\/li>\n Filtered Automation:<\/strong>\u00a0Launch workflows only when refunds meet specific criteria (amount, type, status, source).<\/p>\n<\/li>\n Improved Customer Satisfaction:<\/strong>\u00a0Deliver timely updates during refund processes to improve trust and retention.<\/p>\n<\/li>\n Proactive Handling of Failed Refunds:<\/strong>\u00a0Trigger alternative workflows when refunds fail, reducing churn risk.<\/p>\n<\/li>\n Efficient Operations:<\/strong>\u00a0Eliminate manual processes and ensure consistent handling of refund scenarios.<\/p>\n<\/li>\n<\/ul>\n Setting up the Refund Workflow Trigger ensures\u00a0that your refund processes\u00a0are automated, timely, and customized to your specific business rules.<\/p>\n Name your workflow<\/p>\n<\/li>\n Click\u00a0+ Add New Trigger<\/strong><\/p>\n<\/li>\n Search for and select the\u00a0Refund<\/strong>\u00a0trigger<\/p>\n<\/li>\n<\/ul>\n Click\u00a0+ Add Filters<\/strong>\u00a0at the bottom of the Workflow Trigger page<\/p>\n<\/li>\n Apply filters as needed (see next section for details on filter options)<\/p>\n<\/li>\n<\/ul>\n Add actions based on your business needs (notifications, task assignments, etc.)<\/p>\n<\/li>\n Click\u00a0Save<\/strong>\u00a0and\u00a0Publish<\/strong>\u00a0the workflow<\/p>\n<\/li>\n<\/ul>\n Filters give you control over exactly when the refund workflow will activate, ensuring it’s only triggered by relevant refund scenarios. These filters can be used individually or stacked with each other to give you more control.<\/p>\n Status:<\/strong> Filter based on refund status<\/p>\n Successful: Trigger only after a completed refund.<\/p>\n<\/li>\n Failed: Trigger when a refund attempt fails.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Amount:<\/strong> Filter based on refund value<\/p>\n Greater than, Less than, or Equal to a specific dollar amount (e.g., refund > $100)<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Source:<\/strong> Filter based on where the refund originated<\/p>\n Options include Calendar, Communities, Payment Link, Invoices, Manual, and more.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n Type:<\/strong> Filter based on the type of refund<\/p>\n Full Refund or Partial Refund<\/p>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n After your trigger and filters are set, you can add various actions based on the desired outcome. These examples highlight common use cases.<\/p>\n \n A practical use case for the Refund Trigger is automating customer notifications. For instance, if a refund is processed successfully, an automated email can be sent to inform the customer of the successful transaction. Conversely, if a refund fails, a different automated message can be triggered to notify the customer of the issue and provide further instructions. This ensures timely communication and enhances customer satisfaction during potentially frustrating situations.<\/p>\n Use the Refund Trigger to create a task for your support or success team to follow up with a customer who received a refund.<\/p>\n Q: Can the Refund Trigger handle multiple refunds for the same contact?<\/strong> Q: Will this trigger if I refund through Stripe directly or another external provider?<\/strong> Q: How do I use this trigger for partial refunds only?<\/strong> Q: What if I want to notify internal teams instead of the customer?<\/strong> The Refund Workflow Trigger allows you to automate important tasks whenever a refund is issued. Whether you’re notifying customers, assigning […]<\/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-1274","docs","type-docs","status-publish","hentry","doc_category-payments-workflow-triggers"],"year_month":"2026-07","word_count":810,"total_views":"19","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\/1274","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=1274"}],"version-history":[{"count":1,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1274\/revisions"}],"predecessor-version":[{"id":1276,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/docs\/1274\/revisions\/1276"}],"wp:attachment":[{"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/media?parent=1274"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_category?post=1274"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/onesystemcrm.com\/help\/wp-json\/wp\/v2\/doc_tag?post=1274"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nHow To Set Up a Refund Workflow Trigger<\/strong><\/h2>\n
Step 1:\u00a0<\/strong>Create New Workflow<\/u><\/h4>\n
\n
<\/p>\nStep 2:<\/strong>\u00a0Add Refund Trigger<\/u><\/h4>\n
\n
<\/p>\nStep 3:<\/strong>\u00a0Add Trigger Filters<\/u><\/h4>\n
\n
<\/p>\nStep 4:<\/strong>\u00a0Build Out Workflow<\/u><\/h4>\n
\n
<\/p>\n
\nUsing Filters for Refund Trigger<\/strong><\/h2>\n
\n
\n
\n
\n
\n
<\/p>\n
\nAdding Actions to the Refund Trigger Workflow<\/strong><\/h2>\n
Tip: Refund custom values are also available inside the Payments section in Custom Values. This allows you to send include specific refund details within your messages.<\/span><\/pre>\nExample 1:<\/u><\/strong>\u00a0Send a Confirmation Notification<\/u><\/h4>\n
<\/h4>\n
<\/p>\nExample 2:\u00a0<\/strong>Assign an Internal Task<\/u><\/h4>\n
<\/em><\/p>\n
\nFrequently Asked Questions<\/strong><\/h2>\n
Yes. Each refund instance is treated as a new trigger event. By default, each refund event (even for the same customer) will trigger the workflow again.<\/p>\n
No. The refund must be issued inside HighLevel for the trigger to fire. The payment processors supported in HighLevel are Stripe, Authorize.net and NMI. The integration must be set up and the refund must go through HighLevel in order for the trigger to fire.<\/p>\n
Add a condition to the trigger for Refund Type = Partial. You can use multiple conditions (like Refund Type + Refund Failed) to filter events even more accurately.
\n
\nQ: What happens if the refund fails?<\/strong>
The workflow can still fire based on the selected filters. Use the Refund Failed = True filter to manage cases where the refund fails. This is useful to notify team members of a failed refund.<\/p>\n
You can use internal actions such as tasks or internal emails to notify internal teams of a refund.<\/p>\n","protected":false},"excerpt":{"rendered":"