Order Placed Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Order Placed trigger fires when a customer submits an order. Use it for confirmation emails, loyalty tagging, and CRM updates, with optional cart value filters.

The Order Placed trigger fires a workflow the moment a customer places an order. Use it for confirmation emails, CRM updates, inventory adjustments, and any other action that should run as soon as the order is captured.

What it does

This trigger activates on order creation — before fulfillment. It pairs with Order Fulfilled for full lifecycle coverage: Order Placed handles the moment of purchase, Order Fulfilled handles delivery completion.

Configure the trigger

Pick the trigger — select Order Placed from the trigger list.
Name it — for example, Order Placed - Loyalty.
Set filters — optional Cart Value filter with comparison operators.

Filters

Filter	Description	Required
Cart Value	Total value of items in the cart.	Optional
Operator	Equals to, Greater than, Greater than or Equal to, Less than, etc.	Optional

Example

Goal: thank customers who spend $150 or more and reward them with a coupon.

Trigger: Order Placed
Filter: Cart Value Greater than or Equal to $150
Actions: send a thank-you email with a next-purchase coupon, and tag the customer for loyalty benefits in the CRM.

Frequently Asked Questions

What's the difference between Order Placed and Order Form Submission?

Order Placed fires only on actual orders. Order Form Submission also fires on opt-ins, bumps, and upsells, so it's broader.

Does it fire if payment fails?

Order Placed fires on successful order creation. Failed payments don't create the order, so the trigger doesn't fire.

Can I send different emails based on cart size?

Yes. Build separate workflows with different Cart Value thresholds, or branch a single workflow with conditional steps based on the order total.

Does Order Placed fire before or after the customer sees the confirmation page?

It fires the moment the order is recorded, which happens at the same time the confirmation page renders. Workflow actions run asynchronously, so the customer sees the page first while the automation runs.