Understanding Workflow Triggers: Order Submitted vs. Order Form Submission
Where To Find These Triggers
Both the Order Form Submission and Order Submitted triggers are located within the Workflow Builder under the Payments category.
Trigger - Order Submitted
This trigger activates when a customer completes a purchase and a payment transaction is successfully processed in your CRM. It is specifically tied to finalized orders where payment has been made.
Use Case
Use this trigger to automate actions following a successful sale, such as sending order confirmations, updating contact records, notifying your team, or initiating fulfillment processes.
Example Workflow Actions
- Send a thank you email for the purchase
- Generate an invoice or process payment details
- Trigger shipping notifications or alert the fulfillment team
Trigger - Order Form Submission
This trigger fires when a customer submits a form that includes order-related information, regardless of whether a payment was made. It focuses on the form submission event itself.
Use Case
Ideal for capturing leads or inquiries, such as quote request forms, pre-orders, or interest expressions where no transaction has occurred yet.
Example Workflow Actions
- Send an acknowledgment email for the inquiry
- Notify a sales representative about a new lead
- Start a follow-up sequence to nurture the prospect toward a sale
Key Differences Between Order and Order Form Triggers
Order Submitted: This trigger is associated with a completed purchase and payment. It does not require an order form to have been submitted.
Order Form Submission: This trigger is based on the submission of a form containing order details, with no dependency on payment being made.
Available Values: Certain values related to the order are exclusively available in workflows using the Order Submitted trigger. For instance, when using the Order Submitted trigger, the Shopping Cart element in email templates will automatically populate with the items from the order.