For the complete documentation index, see llms.txt. This page is also available as Markdown.

Flow Actions

Flow actions are operations your workflow can execute through the Globo Preorder app.

To add a flow action, please follow 2 steps below:

1

Click the Plus sign.

2

Choose an action you want.


1) Add product variant to preorder offer

Purpose

Automatically move a variant into preorder coverage.

How it works

This action links a variant to a target preorder offer. After linking, that variant follows the profile's preorder configuration and lifecycle behavior.

Inputs

Input
Required
Meaning

variant_id

Yes

Shopify variant ID or GID

profile_id

Yes

Profile identifier / selling plan related identifier

Typical customer-facing use cases

  • Auto-enable preorder when a product enters a campaign

  • Sync profile assignment from external product rules

Safe usage notes

  • Use consistent ID format (numeric ID or GID) across your workflows

  • Validate that profile_id belongs to the expected profile before running in bulk


2) Remove product variant from preorder offer

Purpose

Remove a variant from preorder coverage when it should no longer be sold as preorder.

How it works

This action unlinks a variant from a preorder offer. Optionally, it can also disable "continue selling when out of stock" for that variant.

Inputs

Input
Required
Meaning

variant_id

Yes

Shopify variant ID or GID

profile_id

Yes

Profile identifier

disabled_continue_selling

No

If true, disables continue selling when out of stock

Typical customer-facing use cases

  • End preorder eligibility for selected variants

  • Prevent further out-of-stock selling after profile removal

Safe usage notes

  • Use the optional disabled_continue_selling carefully in high-volume catalogs

  • Test this action on a staging store before running large batch automations


3) Collect pending payment

Purpose

Collect payment for preorder orders that were authorized with deferred capture/payment terms.

How it works

The action attempts to capture pending payment for the target order. If enabled, customer notification is sent when capture fails.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

notify_customer_on_failure

No

Sends customer email if capture fails

Typical customer-facing use cases

  • Capture at release date before fulfillment is opened

  • Automate payment retry + notification policy

Safe usage notes

  • Add a condition to ensure the order is in a collectible state

  • Pair with support alerts so failed captures are handled quickly


4) Hold all fulfillments

Purpose

Temporarily block shipping for all fulfillment orders related to a preorder.

How it works

The action places all fulfillments for the order on hold. This prevents shipment while your team resolves inventory, compliance, or risk issues.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

reason_notes

No

Internal reason for the hold

Typical customer-facing use cases

  • Pause shipments during quality checks

  • Pause shipment when payment/risk checks require manual review

Safe usage notes

  • Include reason_notes so support can answer customer inquiries accurately

  • Add a paired release workflow to avoid long accidental holds


5) Notify customers in waitlist

Purpose

Send back-in-stock notifications to customers waiting for a specific variant.

How it works

The action sends notifications to customers on the waitlist for the provided variant.

Inputs

Input
Required
Meaning

variant_id

Yes

Shopify variant ID or GID

Typical customer-facing use cases

  • Notify waitlist immediately after restock verification

  • Trigger manual campaigns when merchant wants controlled send timing

Safe usage notes

  • This action does not perform inventory validation before sending

  • Add preconditions in Flow to avoid sending too early or incorrectly


6) Open scheduled fulfillments

Purpose

Move scheduled preorder fulfillments into normal processing state.

How it works

The action changes fulfillment orders from "Scheduled" to "Unfulfilled", making them ready for standard warehouse/fulfillment workflows.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

Typical customer-facing use cases

  • Release orders for fulfillment on launch/restock date

  • Transition from planned shipment to operational shipment

Safe usage notes

  • Ensure payment and inventory checks are complete before opening fulfillments

  • Run this after expected release date/time conditions


7) Release all fulfillments

Purpose

Resume shipment for orders currently placed on hold.

How it works

The action removes fulfillment holds and sets fulfillments back to "Unfulfilled", allowing shipping operations to continue.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

Typical customer-facing use cases

  • Resume shipping after hold reason is resolved

  • Recover operations from temporary fulfillment freezes

Safe usage notes

  • Add checks so release only happens when risk/compliance flags are cleared

  • Notify support when release occurs to align customer communication


8) Send shipping update notification

Purpose

Proactively inform customers about preorder shipping progress.

How it works

This action sends a shipping update email for a preorder order. You can use default template content or provide custom subject/header/body text.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

email_subject

No

Custom subject line

email_header

No

Custom email header

email_description

No

Custom email body text

Typical customer-facing use cases

  • Send milestone updates before dispatch

  • Send localized, campaign-specific shipping communication

Safe usage notes

  • Keep message content aligned with actual fulfillment status

  • If custom fields are empty, default template content is used


9) Split preorder fulfillments

Purpose

Separate preorder items from in-stock items for cleaner fulfillment execution.

How it works

For mixed orders, this action creates separate fulfillment handling so in-stock products can ship now while preorder items remain in their own fulfillment path.

Inputs

Input
Required
Meaning

Order reference

Yes

Shopify order object

Typical customer-facing use cases

  • Ship available items immediately to reduce customer wait time

  • Avoid blocking entire order because one line is preorder

Safe usage notes

  • Add customer communication so split-shipment expectations are clear

  • Pair with shipping update actions for transparency

Last updated

Was this helpful?