Flow Triggers
Flow triggers are events from Globo Preorder that can start a Shopify Flow workflow.
To add a flow action, please follow 2 steps below:
1) Customer placed preorder
Purpose
Use this trigger to start customer and operations workflows immediately after a preorder is created.
How it works
When a checkout creates a preorder order, our Globo Preorder app emits this event to Shopify Flow. Your workflow can then read order information and run follow-up actions (tags, notifications, CRM updates, internal alerts).
Data available
Order reference
The Shopify order object
Order name
Human-readable order label (for example #1001)
Order number
Numeric order number
Typical customer-facing use cases
Send preorder confirmation sequence
Route order to a preorder-specific support queue
Add tags for proactive customer service
2) Customer signed up for back-in-stock alerts
Purpose
Capture customer intent when a customer requests a notification for an out-of-stock variant.
How it works
When a customer submits the back-in-stock form, our Globo Preorder app emits this event with customer + variant context. Shopify Flow can use this to segment customers, notify teams, and start nurture journeys before restock.
Data available
Customer email
Email submitted by customer
Customer phone
Phone submitted by customer (if present)
Customer locale
Customer language/locale
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Variant name
Variant title
SKU
Variant SKU
Signup at
Subscription timestamp
Typical customer-facing use cases
Add customer to the waitlist audience in the CRM
Notify the support team about demand spikes
Trigger localized communication by
Customer locale
3) Customer notified of back-in-stock alert
Purpose
Track outbound restock notifications and trigger post-notification follow-up.
How it works
After a waitlist notification is sent to a customer, our Globo Preorder app emits this event. This is useful for measuring notification effectiveness and for creating "second reminder" workflows when no order is placed.
Data available
Customer email
Notification recipient email
Customer phone
Notification recipient phone
Customer locale
Customer language/locale
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Variant name
Variant title
SKU
Variant SKU
Checkout link
Direct checkout path
Product page link
Product page URL
Unsubscribe link
Waitlist opt-out URL
Typical customer-facing use cases
Send a reminder after 24 hours if not purchased
Record outbound notification in CRM timeline
Split campaign performance by locale or SKU
4) Preorder profile enabled
Purpose
Start automation when a preorder configuration/offer is activated.
How it works
When a merchant enables a preorder offer in the app, this event is emitted. Use it to coordinate launch readiness: internal alerts, campaign switches, and monitoring setup.
Data available
Profile ID
Internal profile identifier
Profile name
Profile display name
Profile tags
Profile categorization tags
Typical customer-facing use cases
Notify support that the preorder has gone live
Activate customer messaging playbooks
Log profile activation for audit/reporting
5) Preorder profile disabled
Purpose
Stop or adjust automations when a preorder profile is turned off.
How it works
When a merchant disables a preorder offer, this event is emitted. Workflows can then pause customer messaging, inform teams, and prevent outdated automation from running.
Data available
Profile ID
Internal profile identifier
Profile name
Profile display name
Profile tags
Profile categorization tags
Typical customer-facing use cases
Stop preorder-specific campaigns
Alert the support team to update response scripts
Mark profile lifecycle transitions in external systems
6) Product added to profile
Purpose
React when a product/variant becomes a part of a preorder offer.
How it works
When a product variant is linked to a preorder profile, this event is emitted. It enables automatic onboarding workflows for that variant across operations, support, and CRM.
Data available
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Profile name
Related profile name
Profile tags
Related profile tags
Typical customer-facing use cases
Start preorder FAQ/chat macro updates
Notify the team that a variant is now preorder-enabled
Sync profile membership to external tools
7) Product removed from profile
Purpose
React when a product/variant is removed from the preorder scope.
How it works
When a variant is removed from a preorder profile, this event is emitted. This helps stop pre-order messaging and prevent customer confusion.
Data available
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Profile name
Related profile name
Profile tags
Related profile tags
Typical customer-facing use cases
Stop preorder reminder communications
Remove preorder-specific tags/segments
Notify support to avoid outdated responses
8) Product variant restocked
Purpose
Start post-restock workflows for waitlisted customers.
How it works
When inventory returns for a variant, this event is emitted. Workflows can use it to trigger customer notifications, internal alerts, and conversion campaigns.
Data available
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Typical customer-facing use cases
Trigger waitlist notification flow
Alert the support team before inbound questions
Start restock conversion campaign
9) Product preorder started
Purpose
Launch customer and operations automation when a variant enters preorder status.
How it works
When a variant transitions into the preorder state, this event is emitted. It marks the beginning of the preorder lifecycle and is useful for campaign start logic.
Data available
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Profile ID
Internal profile identifier
Profile name
Profile display name
Profile tags
Profile categorization tags
Typical customer-facing use cases
Start preorder announcement communication
Enable preorder support playbook
Trigger internal launch notifications
10) Product preorder ended
Purpose
End preorder automation cleanly when a variant exits preorder status.
How it works
When a variant leaves the preorder state, this event is emitted. Workflows can then stop preorder messaging, switch to standard purchase messaging, and trigger reporting wrap-up.
Data available
Product reference
Shopify product object
Product ID
Product identifier
Variant ID
Variant identifier
Profile ID
Internal profile identifier
Profile name
Profile display name
Profile tags
Profile categorization tags
Ended by
Reason/context source for the end event
Typical customer-facing use cases
Stop preorder campaign sequences
Notify support to update the availability message
Trigger post-campaign analytics workflow
Last updated
Was this helpful?