Order Submitted Workflow Trigger in Sparkforge

The Order Submitted trigger fires when an order completes through a Sparkforge order form. Unlike Order Form Submitted, which fires once per submission, Order Submitted fires for each line item — primary product, bump, and upsell — making it the right tool for confirmation emails, upsell follow-ups, and granular reporting.

What the trigger does

It captures every product purchase from a 1-step or 2-step order form, plus upsells and bumps. The trigger exposes custom values for product names, quantities, prices, and payment method, so downstream emails, tasks, and CRM updates can use real order data.

What it is good for

• Sending order confirmation emails with itemized details.
• Driving upsell follow-up sequences.
• Updating customer records with purchase data.
• Segmenting contacts by what they bought.

Order Submitted vs. Order Form Submitted

Configure the trigger

1. Open Automation > Workflows. Pick an existing workflow or click + Create Workflow.
2. Click Add New Trigger, search for Order Submitted, and select it.
3. Name the trigger something descriptive, like Course primary purchase.
4. Apply filters (see below) to scope when the workflow runs.
5. Save and publish.

Filters and operators

Global Product

Trigger on a specific product or price. Use Is to include or Is Not to exclude.

Order Source

Where the order originated:

• External: third-party integration.
• Form: a standard form (not an order form).
• Membership: a membership product purchase.
• Order Form: a Sparkforge order form transaction.
• Payment Link: a direct payment link.
• Store: the online storefront.
• Survey: a survey with an order step.

Sub-Source

Refines the order source. If Order Source is Order Form, Sub-Source narrows to a specific funnel or website. For Store, it can target a category.

In Funnel / Website

Restrict the trigger to a specific funnel or website. Useful for separating product launches across distinct sales channels.

Page Is

Restrict the trigger to a specific page within a funnel or site — like a checkout page, registration form, or upsell page.

Submission Type

• Primary: initial product purchase at checkout.
• Bump: optional add-on accepted during checkout.
• Upsell: a post-checkout offer that the customer accepted.

Product Price

Trigger on a specific price point. Useful when the same product has tiered pricing or limited-time discounts.

Allow Multiple — turn it ON for upsell flows

The Allow Multiple setting controls whether a contact can re-enter the workflow while an earlier instance is still running.

• ON: the workflow fires independently for primary, bump, and upsell purchases. Recommended for any flow that should react to upsells.
• OFF: a single contact only triggers the workflow once at a time. Upsells made while the primary instance is still active will not start a new workflow.

Keep Allow Multiple ON for revenue-driven flows so upsells and bumps actually fire their own confirmations and tasks.

Save and test

1. Click Save to lock in trigger settings.
2. Click Publish to activate the workflow.
3. Submit a test order and check Workflow History to confirm the trigger fired for each line item.