Connect loyalty events to email with Shopify Flow

Published October 1, 2026

Customers may want to know when points are confirmed, a tier changes or a reward is available. Gibbond can publish loyalty events and actions to Shopify Flow on plans that include Flow. Flow can connect an event to a workflow, add conditions and route it to a supported action such as Shopify Email. Gibbond itself does not send email.

Decide what message is useful

Start from the customer’s need rather than the list of available triggers. A points-confirmed message can explain the new balance. A tier-upgrade message can describe the configured benefit and how to use it. An expiring-points reminder can state the actual expiry date or period and link to redemption instructions. Avoid sending a promotional email simply because an event occurred; check the customer’s marketing permissions and the requirements of your chosen sending channel.

Build the workflow in small steps

1. Confirm your Gibbond plan includes Flow access and that Shopify Flow is available in the store.
2. In Flow, create a workflow and choose a Gibbond trigger, such as points earned, points confirmed, tier upgraded or points expiring soon.
3. Add conditions for the cases worth messaging, such as a points threshold or a relevant customer segment.
4. Add a Shopify Email action or another supported action, with concise copy and a clear destination.
5. Test with a development or sample customer, inspect the event fields and verify that the workflow does not issue the reward a second time.
6. Enable the workflow and monitor sends, failures, unsubscribes and support questions.

Use the event as a signal, not a second award

For a birthday reward, configure the reward in Gibbond and use the appropriate event after it has been issued to trigger a message. Do not add another points adjustment or discount creation in Flow unless the intended design requires it; otherwise, a retry or duplicate event could create a second gift. Check the sending provider’s consent requirements and make the message describe the existing reward.

For a points-expiry reminder, the workflow should explain what points are approaching expiry and where the customer can use them. Do not promise a precise balance or date unless those fields are available and confirmed in the actual workflow. Send a test to verify dynamic data and links render correctly.

Protect against duplicate or noisy messages

Automations can be retried, conditions can match more than once and multiple triggers may follow one order. Choose a sensible trigger, add conditions and consider how you will prevent duplicate communication. Where an identifier is available, a stable grant or event ID can help downstream systems deduplicate deliveries. Keep internal logs sufficient to investigate customer questions without exposing unnecessary customer data.

Do not create a message for every points adjustment by default. Staff adjustments, refunds and reversals may all be meaningful internally but confusing as separate customer emails. Decide which events need an immediate notification and which should appear only in the account balance or a periodic summary.

Write email around the actual product behaviour

Say “Your points are confirmed” only when the trigger indicates confirmation. When telling someone they have a new tier, describe the configured multiplier or automatic checkout discount. Treat written perks such as early access as descriptions unless your team has a separate process that grants access. Link to a page explaining redemption and exclusions. Use plain language and keep the subject line specific.

Check it after launch

Review Flow run history after activation. Confirm successful actions and investigate failures, unexpected repeats and messages that did not send. Check unsubscribe handling and keep your workflow documentation current when you change earn, tier, expiry or reward settings. A simple event-to-message map helps support teams answer customers consistently.

Flow gives merchants a way to connect loyalty activity to store automations. The quality of that experience depends on plan access, careful workflow conditions, accurate copy and permission-aware sending.