Quick answer: Flow Get data actions return lists. Even when the maximum result is one, the result is still list-shaped, so fields can render blank if you treat the output like a single order. Use For each or loop through the result in a supported Liquid field.
The real symptom
- A WhatsApp, email, or HTTP action receives blank order values.
- The Get order data action finds a result in run history.
- Maximum results is set to one but variables still do not render.
- The workflow works when triggered directly by an order but not after Get data.
Likely causes
- The workflow references
getOrderData.nameinstead of iterating overgetOrderData. - The receiving action does not support the Liquid loop being used.
- The query returns no records because the filter is wrong.
- Two Get order data actions created similarly named variables such as
getOrderData1.
Fix path
- Open the failed workflow run and inspect the Get order data output.
- Add a For each step after Get order data.
- Place actions that need order fields inside the For each branch.
- Reference the current item from the loop, not the list itself.
- If the target field supports Liquid, loop through the returned list explicitly.
- Retest with a known order ID or simple query.
Simple checks
- Use the run log to confirm whether the list contains zero, one, or many orders.
- Rename actions clearly so variables are not confused.
- Avoid sending a list into connectors that expect a scalar string.
Do not do this
Do not assume “maximum results: 1” converts a Flow list into a single object. It only limits the number of list items returned.