Workflow Trigger: Order Submitted in Stack
Managing post-purchase actions efficiently is crucial for any business. The Order Submitted Trigger in Stack automates workflows based on completed orders, whether from 1-Step or 2-Step order forms. This guide will help you understand what this trigger does, how it differs from other order-related triggers, and how to configure it for optimized workflow automation.
Table of Contents
- What is the Order Submitted Workflow Trigger?
- Key Benefits of the Order Submitted Workflow Trigger
- Order Submitted vs. Order Form Submitted
- Configuring the Order Submitted Workflow Trigger
- Frequently Asked Questions
What is the Order Submitted Workflow Trigger?
The Order Submitted Trigger activates a workflow when an order is placed through an order form. Unlike basic order form triggers, this trigger captures both primary purchases and upsell transactions, making it ideal for:
- Sending order confirmation emails
- Automating upsell follow-ups
- Updating customer records with order details
- Segmenting customers based on purchase behavior
This trigger supports custom values, allowing businesses to dynamically reference product names, quantities, prices, and payment methods inside workflows.
Key Benefits of the Order Submitted Workflow Trigger
- Automated Engagement: Sends order confirmations and upsell offers instantly.
- Increased Revenue: Enables upsell workflows to boost sales.
- Time-Saving Automation: Reduces manual order management tasks.
- Detailed Order Insights: Captures product and payment data for better automation.
Order Submitted vs. Order Form Submitted
Understanding the difference between these triggers is essential for choosing the right one for your automation.
| Feature | Order Submitted | Order Form Submitted |
|---|---|---|
| Trigger Activation | Fires for each product purchase (Primary, Bump, Upsell) | Fires once per order submission, regardless of products purchased |
| Filter Capabilities | Can filter by product, price, source, submission type | No filtering by product/price |
| Custom Values | Provides order details like product names, prices, quantities | Limited order details available |
Configuring the Order Submitted Workflow Trigger
Add Order Submitted Trigger
- Navigate to the Automation tab and select Workflows.
- To create a new workflow, click + Create Workflow. To add the trigger to an existing workflow, find and open the desired workflow for editing.
- Click on Add New Trigger and search for "Order Submitted". Select it from the list.
Applying Filters
Filters allow you to fine-tune your workflow trigger by specifying conditions based on order details. This ensures the automation runs only when certain criteria are met.
Global Product
This filter triggers the workflow based on a specific product or price.
- Is: Triggers the workflow only when the specified product is purchased.
- Is Not: Excludes the selected product, ensuring the workflow runs for all other products except the one specified.
Order Source
Determine where the order was placed to ensure the workflow triggers only for purchases from a specific source.
- Options: External, Form, Membership, Order Form, Payment Link, Store, Survey
- Operators:
- Is: Triggers only for the selected order source.
- Is Not: Excludes the selected order source.
Sub-Source
Refine the Order Source further by targeting specific funnels, pages, or subcategories.
- Operators:
- Is: Triggers only when the order matches the selected sub-source.
- Is Not: Excludes orders from the selected sub-source.
In Funnel/Website
Ensure workflows trigger only when an order form is submitted through a specific funnel or website.
- Operators:
- Is: Triggers only if the order is submitted through the selected funnel or website.
- Is Not: Excludes orders from the selected funnel or website.
Page Is
Trigger workflows only when an order form is submitted on a specific page within a funnel or website.
- Operators:
- Is: Triggers only when the order is submitted on the selected page.
- Is Not: Excludes orders from the selected page.
Submission Type
Trigger workflows based on the type of purchase made.
- Primary: Initial product purchase.
- Bump: Optional add-ons during checkout.
- Upsell: Offers presented post-checkout.
Product Price
Trigger workflows based on the specific price of a product.
- Operators:
- Is: Triggers when the product is purchased at a specific price.
- Is Not: Triggers when the product is purchased at any other price.
Enable “Allow Multiple”
To ensure seamless automation for both primary purchases and upsells, enable the Allow Multiple setting. This allows the workflow to trigger separately for each purchase event.
- When Allow Multiple is ON: The workflow can trigger multiple times for the same contact.
- When Allow Multiple is OFF: Any upsell purchases made by the customer won’t trigger a new instance if the workflow is still active from the primary purchase.
Frequently Asked Questions
Q: Does this trigger work with upsell purchases?
Yes, the Order Submitted Trigger fires for both primary purchases and upsells, provided Allow Multiple is enabled in workflow settings.
Q: Can I use this trigger to send order confirmations?
Yes, you can automate order confirmation emails and use the Shopping Cart element to include product details dynamically.
Q: How do I ensure the workflow only triggers for a specific product?
Use the Global Product filter and select “Is” or “Is Not” to include/exclude specific products.
Q: Will this trigger affect my existing order form workflows?
No, the Order Submitted Trigger works independently from the Order Form Submitted Trigger, allowing more granular control over workflow execution.
Q: Can I trigger workflows based on the payment method used?
Yes, you can apply filters based on the payment gateway (Stripe, PayPal, etc.) to trigger different workflows for different payment methods.