Answer an order question with the order in hand
A reply that answers with the real order status instead of asking the customer for their order number. Built for an ecommerce team answering the same three questions about where a package is.
Gmail
Shopify
Stripe
5 steps3 integrationsRuns on every new record
The answer is in the order record, one tab away. What it costs while the work is still done by hand.
- 01The answer needs the order record, which is in another tab.
- 02Every reply is retyped from scratch.
- 03Customers wait for something the system already knows.
- Read messageshared inbox · 1 thread
- Find order#1042 · shipped 2 days ago
- Check paymentretrieve_payment_intent · paid
- Draft replytracking link · 2 lines
- Approve sendsend_message · sent
One workflow, five steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the incoming message.Gmail
- 02Find the matching order.Shopify
- 03Check payment status where it matters.Stripe
- 04Draft a reply with the order's actual status.ModuleX
- 05Review and approve before it sends.Gmail
The workflow is an editable graph. Reading runs freely; review and approve before it sends waits for your opt-in approval until you loosen it. The graph is the receipt.
Answers with the order attached. Paste this into ModuleX chat, or hit Use this workflow.
answer an order question with the order in hand: read the incoming message; find the matching order; check payment status where it matters; draft a reply with the order's actual status. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Answer an order question with the order in hand. A reply that answers with the real order status instead of asking the customer for their order number.
- gmail · send_message
- shopify · search_orders
- stripe · retrieve_payment_intent
A reply that answers with the real order status instead of asking the customer for their order number.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
- Answer support questions using your own documentationA drafted answer grounded in your own material, showing what it drew from, behind an approval step. Built for support teams whose answers already exist, just not where the question arrives.
See which accounts went quiet this weekOne weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.
Turn a customer email into a tracked issueA tracked issue an engineer can pick up without opening the email, and a customer who knows it was logged. Built for support and product teams where bug reports die in an inbox.
About this use case.
This workflow reads the order; it does not modify it.