Use this file to discover all available pages before exploring further.
The WooCommerce Find Orders step allows your team to search for and view customer orders in your WooCommerce store directly from FlowEQ. This step can be particularly useful for quickly accessing order information without needing to switch between platforms, saving time and improving efficiency.After selecting an order, numerous variables will be populated, allowing you to use that information in later steps in your Flow. For example, you could use the order information to update a ticket in your CRM, or to trigger a notification to your team.
If only one store is connected to FlowEQ, that store will be searched by default. If multiple stores are connected, you can select which stores you want to search for orders in.
This defines which stores to search for customers in. This is because orders are tied to customers, so we first need to find the customer in order to find their orders. If a customer is found in any of the selected stores, all of their orders from those stores will be returned as options for the agent to select from when running the step.
When searching multiple stores, we must make an API request to each individual store. So, if you have a large number of stores connected and selected in this step, it may take longer for the step to load when running the Flow.
Enabling this option will allow FlowEQ to automatically search for customers based on the email address provided in the Email field. The agent will not have an option to manually search for customers when running the step, and will only see the orders that are returned based on the provided email address.
Enter the email address of the customer whose orders you want to search for.Remember, you can hit the button to insert a variable to pull data from other fields or other configured integrations.
Once the step has been added to a Flow and configured to your liking, when an agent runs the Flow, they will be able to search for customers based on the provided email address. If one or more customers are found, they will be able to select the correct customer, and then select from a list of that customer’s orders in the selected stores.
After entering an email address and hitting “Search”, if one or more customers are found, they will be displayed as cards for the agent to select. Each card will display the customer’s name, email address, and the stores they are associated with.After clicking the customer that the agent wants to view orders for, they can click “SEARCH ORDERS” to view that customer’s orders.
After clicking “SEARCH ORDERS”, if one or more orders are found for the selected customer, the orders will be displayed as cards for the agent to select. Each card will display the order number, order date, order status, the store it is associated with, and the total amount for the order.After clicking the order that the agent wants to view details for, they can click “SELECT ORDER” to select that order and populate the step’s variables with that order’s information. The step will then be completed, and any subsequent steps in the Flow can use the order information that was pulled in this step.
After selecting an order, we will populate a number of variables that can be used in later steps in your Flow. These variables will change depending on what data is available for the selected order.
FlowEQ uses dot notation to navigate through API response data returned by a step. Variables are automatically constructed (they won’t appear in the variable picklist). Each part of the variable breaks down as follows:
Part
Description
<%= and %>
Standard FlowEQ variable wrappers
woocommerce
The step name assigned to your WooCommerce step
selectedCustomer / selectedOrder / store
The top-level key in the response data
first_name, status, etc.
The specific field within that object
Example: To access the customer’s first name, you would write:
<%= woocommerce.selectedCustomer.first_name %>
For nested objects (like billing or shipping addresses), you add another level of dot notation:
This contains information about the chosen store for the selected order. This is especially helpful when searching across multiple stores, as it allows you to know which store the selected order is from.
Information about the selected customer based on the email address entered in the step. This will be populated regardless of whether you have “Automatically search for customers” enabled or not, as long as a customer is found with the provided email address.
These variables contain information about the chosen order. This is the main object that is returned in this step, and it contains a lot of information about the order, including nested objects for billing and shipping addresses. This is where you can pull most of the information about the order that you want to use in later steps in your Flow.
