Some store tasks start with a form rather than a cart: a custom quote, a vendor listing, a return request or a stock count. FlowMattic takes each Fluent Forms entry and turns it into a WooCommerce order, product, coupon or order note on the same WordPress site, then shows the visitor a message or page based on what happened.
45 triggers 59 actions 7 example workflows 3 ready-made templates Unlimited runs
When this happens in Fluent Forms2 triggers
Do this in WooCommerce57 actions
1. TriggerNew Form Submission2. ActionCreate New OrderWhen Fluent Forms fires New Form Submission, FlowMattic runs Create New Order in WooCommerce with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateMade-to-order and wholesale shops take requests on a form. Each entry becomes an order with the customer's details, so it sits in the same order list as checkout sales.
New Form SubmissionCreate New Order
View the template Ready-made templateMakers or suppliers fill in a product form with a name, price and description, and a product is created from the entry, ready for you to review before it goes on sale.
New Form SubmissionCreate New Product
View the template A newsletter or survey form creates a one-off WooCommerce coupon and shows the code in the success message, so the reward appears on screen as soon as the form is sent.
New Form SubmissionCreate CouponSet Custom Response
Customers enter their order number and reason on a returns form. The order is found and the request added as an order note, so staff see it next to the order itself.
New Form SubmissionGet Order by IDAdd Order Note
Look up the email from the form. A Router sends people who already shop with you to their account page and first-timers to a welcome offer page.
New Form SubmissionGet Customer by EmailRouterRedirect to Custom URL
Warehouse or shop-floor staff submit a SKU and counted quantity from their phone. The product is found by SKU and its stock set, with no wp-admin access needed.
New Form SubmissionGet Product by SKUUpdate Product Stock Quantity
Deposits and bookings paid through a Fluent Forms payment form are added as a customer and an order, so store reports include money taken outside the cart.
New Payment Submission (Pro)Create a CustomerCreate New Order
When you finish, each request sent through your form appears as a new order in WooCommerce.
Add fields for name, email, phone, address and the product or SKU wanted, plus quantity and any notes.
Create a workflow with the Fluent Forms New Form Submission trigger, pick the form and submit a test request. Both plugins run on this site, so no extra account is needed.
Add a WooCommerce step with Create New Order and map the customer, address, product and quantity fields from the entry.
Run the test, open the new order in WooCommerce to check it, then switch the workflow on.
1. Trigger in Fluent Forms
New Form Submission
2. Action in WooCommerce
Create New Order
Fields mapped from the earlier steps (a typical setup)
| From Fluent Forms | To WooCommerce |
|---|---|
| Name | Billing first and last name |
| Billing email | |
| Phone | Billing phone |
| Address | Billing and shipping address |
| Product ID or SKU | Line item product |
| Quantity | Line item quantity |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Fluent Forms and WooCommerce connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Quotes, vendor listings, returns and stock counts get into WooCommerce through a form your customers or staff can fill in from any page.
Fluent Forms, WooCommerce and FlowMattic all run in your WordPress install, so customer details never leave your server on the way.
Runs are unlimited on every plan, so a busy returns season or a big vendor drive costs the same as a quiet month.
Yes. Use New Form Submission with Create New Order and map the customer, address and product fields. Add Change Order Status afterwards if the order should start in a status other than the default.
Yes. Create the code with Create Coupon, then use Set Custom Response to put it in the form's success message. Add Email(s) to Coupon if it should work only for that address.
Not usefully. The two Fluent Forms actions shape the response to a form submission, so WooCommerce triggers pair better with other apps or with FlowMattic tools.
Yes. Look the order up with Get Order by ID or Get Orders by Email and show its status with Set Custom Response, so customers get an answer without logging in.
No. WooCommerce and Fluent Forms are plugins on the same WordPress site as FlowMattic, so their triggers and actions are available once the plugins are active.
Did not find your answer? You can browse the help center or ask us directly.
Fluent Forms and Slack42 shared templates
Fluent Forms and FluentCRM30 shared templates
Fluent Forms and Google Sheets23 shared templates
Fluent Forms and AI Agents19 shared templates
Fluent Forms and ClickUp18 shared templates
Fluent Forms and OpenAI (ChatGPT)8 shared templates
Fluent Forms and Notion6 shared templates
Fluent Forms and Airtable6 shared templatesWooCommerce and Google Sheets20 shared templates
WooCommerce and Slack18 shared templates
WooCommerce and WhatsApp Cloud API13 shared templates
WooCommerce and FluentCRM10 shared templates
WooCommerce and AI Agents8 shared templates
WooCommerce and Telegram5 shared templates
WooCommerce and Gmail3 shared templates
WooCommerce and ClickUp2 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Fluent Forms integration 2.1.4, WooCommerce integration 2.2.2.