Refund Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Refund trigger runs Sparkforge workflows whenever a refund processes inside the platform. Filter by status (successful or failed), amount, source, and type to power confirmation emails, internal tasks, and failed-refund alerts.

The Refund trigger fires when a refund is issued inside Sparkforge. Use it to send confirmations, assign internal follow-up tasks, and route failed refunds to the right team without manual intervention.

What the Refund trigger does

It activates a workflow when a refund event occurs on a payment processed through Sparkforge. Filters scope it by status, amount, source, and type, so you can run distinct workflows for partial vs. full refunds, successful vs. failed attempts, and high-value vs. routine refunds.

Why it is useful

Customer notifications: automatic refund confirmation emails or SMS, which cuts inbound support volume.
Team task assignment: a follow-up task gets created so nothing slips.
Filtered automation: different workflows for different refund amounts, types, sources, or statuses.
Failed-refund recovery: branch on failures to alert finance or retry.
Consistent operations: every refund follows the same internal handling.

Set up a Refund workflow

Go to Automation in the left navigation.
Click + Create Workflow in the top right.
Name the workflow.
Click + Add New Trigger and select Refund.
Click + Add Filters and set scope (see below).
Add downstream actions — emails, SMS, internal tasks, tag updates.
Save and publish.

Available filters

Status

Successful: fires after a completed refund.
Failed: fires when a refund attempt fails.

Amount

Greater than, less than, or equal to a dollar threshold — useful for separating high-value refunds (which need finance review) from routine ones.

Source

Where the refund originated: Calendar, Communities, Payment Link, Invoices, Manual, and other supported sources.

Type

Full Refund: the entire transaction was refunded.
Partial Refund: only part of the transaction was refunded.

Common actions

Refund-related custom values are available under the Payments section in Custom Values, so you can reference refund amount, transaction ID, and reason inside emails and tasks.

Send a customer confirmation

On a successful refund, send an email or SMS with the amount and reference. On a failed refund, send a different message with next steps.

Assign an internal task

Create a task for the success or finance team to verify the refund posted and follow up if needed.

Frequently Asked Questions

Will the trigger fire if I refund through Stripe directly?

No. The refund must be issued inside Sparkforge for the trigger to fire. Sparkforge supports Stripe, Authorize.net, and NMI integrations — the refund must go through those connections inside the CRM.

Does it handle multiple refunds for the same contact?

Yes. Each refund is treated as a separate event, so the workflow fires again for each refund — even on the same contact.

How do I trigger only on partial refunds?

Add a Type filter set to Partial. Stack Status = Successful or Status = Failed to scope further.

What happens if the refund attempt fails?

The Status = Failed branch fires. Use it to alert internal teams, retry through a different gateway, or message the customer with next steps.

Can I notify only internal teams instead of the customer?

Yes. Use internal email or task actions — customer-facing channels are optional and you can omit them entirely.