Skip to main content

Workflow Trigger: Order Submitted

The Order Submitted trigger enrolls a contact into a workflow whenever an order, bump, or upsell is successfully submitted, allowing advanced post-purchase automation.

Updated over 2 months ago

Who This Is For / When to Use

  • Accounts running one-step or two-step order forms.

  • Teams triggering upsells, cross-sells, or post-purchase follow-ups.

  • Businesses needing order-level data such as products, prices, coupons, or payment gateways inside workflows.

What the Order Submitted Trigger Does

  • Fires when an order is successfully submitted.

  • Supports primary products, bump offers, and upsells.

  • Can fire multiple times for the same contact when re-entry is enabled.

  • Provides access to order-related custom values inside workflow actions.

How to Create a Workflow with Order Submitted

Step 1: Create or Open a Workflow

Navigate to Automations > Workflows and click Create Workflow, or open an existing workflow.

Step 2: Add the Order Submitted Trigger

  1. Click Add Trigger.

  2. Choose Order Submitted from the trigger list.

  3. Name the trigger if needed.

Configuring Trigger Filters

Filters control which orders will trigger the workflow.

Available Trigger Filters

  • Product – Filters by global product name.

  • Price – Filters by price name.

  • Order Source – Filters by order form or payment link.

  • Submission Type – Primary, Bump, or Upsell.

  • Funnel – Filters by funnel name.

  • Page – Filters by page inside a funnel.

Understanding Submission Type Filters

Submission Type filters determine which part of the checkout triggers the workflow.

  • Primary – Fires when the main product is purchased.

  • Bump – Fires only when a bump product is purchased.

  • Upsell – Fires only when an upsell is purchased.

If no bump or upsell is purchased, those filters will not trigger the workflow.

Allowing Multiple Trigger Executions

Enable Allow Re-entry

To allow the same contact to trigger the workflow multiple times:

  1. Open the workflow.

  2. Go to Settings.

  3. Enable Allow re-entry.

Important behavior:
If a contact is still inside the workflow (for example, waiting on a wait step), they cannot re-enter until they exit.

Important Wait Step Consideration

If you plan to handle upsells or bumps, avoid placing long wait steps immediately after the trigger.

Why:

  • A contact held in a wait step cannot re-enter the workflow for a subsequent upsell.

  • This can prevent upsell-based workflows from firing as expected.

Using Conditions with Order Data

Branching Logic with If/Else

You can guide contacts through different paths based on order data.

Common condition use cases:

  • Order Total greater than a specific value.

  • Product purchased equals a specific product.

  • Submission Type equals Upsell.

Order Submitted vs Order Form Submitted

Key Differences

  • Single checkout event: Order Submitted sends one event containing all purchased products.

  • Advanced filtering: Supports product and price-based filters.

  • Custom values: Provides access to order totals, coupons, payment gateways, and customer details.

Order Form Submitted does not support these order-level details.

Using Order Custom Values in Actions

Order-related custom values can be used in:

  • Emails

  • SMS

  • Internal notifications

  • Webhooks

Important:
Order custom values only appear if Order Submitted is included as the workflow trigger.

Available Order Custom Values

Order

Includes:

  • Currency symbol and code

  • Cart total and order total

  • Coupon code and total discount

  • Created date and time

  • Order ID

  • Payment gateway

Order > Customer

Includes:

  • First name and last name

  • Email and phone

  • Full address, city, state, country, and postal code

Using Payment Links with Order Submitted

The Order Submitted trigger also works with payment links.

Example use case:

  • Trigger a workflow when an order source equals Payment Link.

Common Issues and Fixes

Workflow does not trigger for upsells
Ensure Allow re-entry is enabled and the contact is not stuck in a wait step.

Order custom values not visible
Confirm the workflow trigger is Order Submitted, not Order Form Submitted.

Trigger fires only once
Check workflow settings and enable Allow re-entry.

FAQ

What is the Order Submitted trigger used for?

It is used to trigger workflows after an order, bump, or upsell is completed, enabling post-purchase automation.

How can I allow the trigger to fire multiple times for the same contact?

Enable Allow re-entry in the workflow settings.

How do submission type filters work?

Submission Type filters control whether the workflow triggers on primary purchases, bump offers, or upsells.

Will this affect existing Order Form Submitted workflows?

No. Existing workflows remain unchanged, but Order Submitted is recommended for advanced order data.

Why can’t I see order custom values in my emails?

Order custom values only appear when Order Submitted is actively used as the workflow trigger.

Can I customize workflows based on order totals or products?

Yes. Use If/Else conditions to branch based on order totals, products, funnels, or submission types.

Are wait steps recommended when using upsells?

No. Wait steps can prevent contacts from re-entering the workflow for upsells.

Does this trigger support PayPal and Stripe?

Yes. Payment gateway details are available through order custom values.

Did this answer your question?