Email the customer when an Ordergroove subscription changes frequency

When a customer changes how often their Ordergroove subscription delivers, this workflow sends them an email from your Gmail account confirming the change.

Ordergroove

Gmail

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 3.3k sites Free to import

What this workflow does

Customers who change their delivery schedule want to know the change took. Without a note, some will contact support to check, and others won't notice a mistake until a box arrives at the wrong time. This workflow sends a confirmation email whenever the frequency changes.

The Ordergroove trigger, Subscription Change Frequency, fires when a subscription's delivery frequency is modified. The event data comes into FlowMattic, and the Gmail step's Send Email action sends a message from your connected Gmail account. You write the subject and body, and map the recipient and details from the Ordergroove data.

The email needs the customer's address. Change a test subscription's frequency after import and check in Task History that the event carries an email you can map as the recipient. Other subscription changes, such as skips or cancellations, don't fire this trigger.

Confirming a slower delivery schedule

A customer moves from monthly to every two months. They get an email from your shop's Gmail address confirming the new schedule.

Fewer support tickets after changes

Customers who change their frequency get written confirmation, so they have something to check before writing to support.

Personal touch for a small brand

A small subscription business sends the confirmation from the founder's Gmail account, so replies go straight to a real person.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Ordergroove Subscription Change Frequency
Fires when the delivery frequency of an Ordergroove subscription is modified. The subscription and customer data from the event become available for the email.
Step 2Action
Gmail Send Email
Sends an email from your connected Gmail account to the recipient you map. Write the subject and body, and insert details from the Ordergroove event, such as the new frequency if it is present.

What you need

FlowMatticCore
Ordergroove AccountAccount
Gmail AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Send the email to yourself first by putting your own address in the recipient while testing, then switch to the customer's email from the Ordergroove data.
Add a Google Sheets step after Gmail to log each frequency change with the customer and date, which helps spot customers who change often.
Add a Filter before the Gmail step that continues only when the Ordergroove data holds an email address, so runs without a recipient stop there.

Questions about this workflow

Does this email go out when an Ordergroove subscription is skipped or cancelled?

No. The trigger fires only when the delivery frequency is modified. Other Ordergroove events need their own trigger.

Which Gmail address sends the confirmation?

Whichever Gmail account is connected to this workflow's Send Email step. Replies from customers land in that inbox.

What if a customer changes their frequency twice in a day?

Each change is its own Ordergroove event, so each one sends an email.

Will the Ordergroove email show the customer's new delivery schedule?

Only if the frequency change event carries it. Change a test subscription after import and check the event data in Task History before you write the message.