Send a short reply from a one-line instruction
A short reply, in the right thread, waiting for your approval before it goes. Built for anyone who knows what to say but not who to say it to.
Gmail
3 steps1 integrationRuns on demand
Finding the thread takes longer than replying. What it costs while the work is still done by hand.
- 01Finding the right thread takes longer than writing the reply.
- 02Short replies get postponed and become late replies.
- 03Context has to be re-read before every send.
- Instructionsay yes to Thursday
- Find threadContract review · 4 messages
- Draft reply2 lines · quoted context
- Approvesend_message · reply sent
One workflow, three steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Find the thread the instruction refers to.Gmail
- 02Draft the reply in the thread's own context.ModuleX
- 03Review 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.
Short replies, sent. Paste this into ModuleX chat, or hit Use this workflow.
send a short reply from a one-line instruction: find the thread the instruction refers to; draft the reply in the thread's own context; review and approve before it sends. 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.
Send a short reply from a one-line instruction. A short reply, in the right thread, waiting for your approval before it goes.
- gmail · send_message
A short reply, in the right thread, waiting for your approval before it goes.
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.
Assemble the evidence pack for a reviewAn evidence pack assembled from your systems, with the gaps named and assigned. Built for whoever collects the same screenshots and exports every audit cycle.
Build a one-pager on a company before you meet themA one-pager combining public background with your own record, reusable by whoever meets them next. Built for anyone walking into a meeting knowing only the company name.- Capture a request as a task without leaving the threadA task that carries the original request and links back to where it was made. Built for anyone who says yes in an email and then forgets.
About this use case.
You see the thread and the draft together before approving.