GetSale
HomeAll our Shopify appsContact Us
GetSale Bulk Discounts & Sales

GetSale Bulk Discounts & Sales

Read reviewsStart 5-day free trial

Integrations

Automate Discount Events with Shopify Flow

Start workflows when GetSale finishes starting or ending a classic price-reduction discount.

Last updated on 27 Jul, 2026

GetSale provides two Shopify Flow triggers that let you automate work around your sale lifecycle. A workflow can start after GetSale has successfully finished applying or removing a classic price-reduction discount.

Before you begin

  • Install and set up the Shopify Flow app on your store.

  • Keep GetSale installed on the same store.

  • Decide what should happen after a discount starts or ends, such as sending a notification or calling another service.

GetSale provides triggers only. The conditions and actions that follow come from Shopify Flow, Shopify, or another installed app.

Create a GetSale workflow

  1. From Shopify admin, go to Apps > Flow.

  2. Click Create workflow.

  3. Click Select a trigger.

  4. In the Installed list, select GetSale.

  5. Choose GetSale discount started or GetSale discount ended.

  6. Add any conditions and actions that should run after the trigger.

  7. Give the workflow a clear name, then click Turn on workflow.

For general help using the workflow editor, see Shopify's guide to creating workflows.

Available GetSale triggers

GetSale discount started

Fires after GetSale finishes applying a classic discount and records it as active. It does not fire merely because the scheduled start time has arrived; GetSale first completes the price changes.

GetSale discount ended

Fires after GetSale finishes removing a classic discount and records the completed end state. For a repeating discount, it fires at the end of each completed cycle before the discount returns to its next scheduled state.

Data available in the workflow

Both triggers provide these text fields:

  • Discount ID — the internal GetSale ID for the discount.

  • Discount name — the campaign name entered in GetSale.

  • Schedule type — one of one-off, one-off-schedule, or repeated-schedule.

  • Event time — the ISO 8601 date and time when GetSale recorded the completed transition.

You can insert these fields into Flow conditions and actions. For example, use the discount name in a notification or branch a workflow according to the schedule type.

Example automations

  • Notify your team by email or Slack when a sale goes live.

  • Send a message when a sale ends so merchandising can review the storefront.

  • Send an HTTP request to an external reporting or campaign system.

  • Use a condition to run different actions for one-off and repeating discounts.

  • Record the discount name and event time in an audit destination supported by Flow.

Important behavior

  • The triggers apply to classic price-reduction discounts. Quantity-break discounts do not emit these events.

  • Events fire after GetSale completes the transition. Large catalogs can therefore trigger later than the scheduled start or end time.

  • A workflow must be turned on before the relevant discount transition completes.

  • Flow delivery is asynchronous and best-effort. A Shopify Flow outage never prevents GetSale from starting or ending the discount.

  • GetSale submits a completed event once after delivery begins. If Shopify Flow is unavailable at that moment, the workflow might not run.

Troubleshooting

The GetSale trigger is missing

Confirm that both GetSale and Shopify Flow are installed on the same store. In the trigger picker, look under Installed and select GetSale. If Flow was already open when GetSale was installed or updated, close and reopen the workflow editor.

The workflow did not run

Check that the workflow was turned on before the transition, that the discount is a classic price-reduction discount, and that GetSale completed the start or end operation successfully. Large discounts can take time to finish. Review the workflow's activity in Shopify Flow for delivery or action errors.

A repeating discount generated an ended event

This is expected. The ended trigger fires after every completed cycle of a repeating discount, even when another cycle is scheduled later.

Was this page helpful?
Previous

Widgets & Banners

Next

Please contact us through the GetSale app for further support