Introduction
The Stripe Wait for Subscription Event step pauses the workflow until the Gravity Forms Stripe Add-On receives a webhook for one of the following subscription events.
Note: Webhooks are automatically created when you configure the Stripe Add-On and set up a subscription feed on your form. These webhooks listen for Stripe events and trigger workflow actions accordingly.
Subscription Events
The step can wait for any of the following events:
| Event | Webhook Type | Description | Where to Find Details |
|---|---|---|---|
| Upcoming Payment | invoice.upcoming | Stripe will attempt to charge the customer soon (typically sent a few days before the charge) | Navigate to Payments > Invoices in your Stripe Dashboard |
| Paid | invoice.payment_succeeded | Payment was successfully processed | Navigate to Payments > Invoices in your Stripe Dashboard and click on the invoice |
| Failed | invoice.payment_failed | Payment attempt failed, typically due to customer-side issues such as insufficient funds, expired cards, or declined transactions | Navigate to Payments > Invoices in your Stripe Dashboard and click on the failed invoice. The failure details will appear in the payment timeline |
| Cancelled | customer.subscription.deleted | The subscription was cancelled (can be triggered from the Stripe Dashboard, a Gravity Forms workflow, or any other system connected to your Stripe account) | Navigate to Payments > Subscriptions in your Stripe Dashboard |
For detailed information about each event, see Stripe’s webhook event documentation.
Cross-Form Subscription Management
The Wait for Subscription Event step responds to webhooks for subscriptions in your Stripe account, regardless of where the cancellation or change originated. For example:
- Form A creates a subscription and includes a Wait for Subscription Event step for cancellations
- Form B processes a cancellation request for that same subscription
- The webhook triggers Form A’s workflow to continue
This also means that subscriptions cancelled directly in the Stripe Dashboard will trigger the workflow to continue.
Jump to Step Per Subscription Event
Use the “Next Step if” status options to determine which step in your workflow should be used when each of these events occurs. This allows you to create different workflow paths based on the subscription event received.
Max Number of Wait for Subscription Event Steps
There is no limit to the number of Wait for Subscription Event steps you can use in your workflow, however, you may only need one. Here is an example payment and user registration workflow which loops between Wait for Subscription Event and Notification steps until the subscription is cancelled.
