Subscription and Refund Triggers for Payments in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

Two new payment triggers — Subscription and Refund — let you automate work when a subscription is created, moves trial-to-active, or is cancelled, and when a refund succeeds, fails, or runs partial.

Sparkforge already supported Payment Received, Order Submitted, and Invoice triggers. Two more give you tighter control over revenue automations.

Subscription trigger

Fires on subscription lifecycle changes:

Subscription created.
Subscription moves from trial to active.
Subscription cancelled.

Use status filters and IF conditions to branch on which status changed, or which product the subscription belongs to. Subscription custom values are exposed inside the Payments custom value group, so you can pull them into emails, SMS, and tasks.

Refund trigger

Fires whenever a refund is attempted. Branch on:

Success or failure.
Full or partial refund.
Refund amount.
Refund source.

Refund custom values are also available inside Payments custom values, so notifications can carry the right context (amount, transaction, who processed it).

Gateway support

Gateway	Subscription trigger	Refund trigger
Stripe	Full lifecycle	Yes
Authorize.net	Full lifecycle	Yes
NMI	Full lifecycle	Yes
PayPal	Created only	Coming

Connect gateways under Payments > Integrations.

Frequently Asked Questions

Can I use these triggers with PayPal?

Partially. Today the Subscription trigger only fires on subscription creation for PayPal. Cancellation, trial-to-active, and refund coverage for PayPal are on the roadmap.

Where do I find subscription and refund custom values?

Inside the Payments custom value group when building a workflow. They include amount, status, gateway, and product references.

Can I notify a customer differently for partial vs full refunds?

Yes. Use IF/ELSE branches on the refund amount or full/partial flag to send different emails or SMS.