Map a workflow before connecting apps

Use this before connecting apps or adding an agent. Map the process first so every step has an input, an owner, and a way to recover when something goes wrong.

Prompt template

Help me design a practical workflow for [task].

Current process: [what people do today].
Trigger: [event, schedule, or manual request].
Approved inputs: [data and sources].
Desired output: [artifact or action].
Available apps: [confirmed apps, or unknown].
Important constraints: [privacy, quality, cost, time, and review].

Return a table with: step, input, output, rule or AI contribution, validation, human owner, and failure path.

Identify where ordinary rules are enough, where AI interpretation could help, and whether an agent is needed. Include permission boundaries, duplicate-event handling, review before consequential actions, stop conditions, and a small test plan.

Do not assume the apps are connected or claim a measured time saving. Mark unknown capabilities and propose a reversible first pilot.

Boundary: Produce a workflow design and a proposed test plan only. Keep supplied facts, names, numbers, and meaning intact; leave source records, the current process, and connected systems unchanged. List proposed changes separately. Don't connect apps or execute the workflow.

Fill in this prompt in the builder

What to supply

  • The current process and its trigger.
  • Approved input, desired output, and confirmed available apps.
  • Privacy, cost, timing, and review constraints.

Worked example

Illustrative example: the input and result below are invented.

Input

Maya, 34, copies supplier delivery notices into a stock worksheet. She wants a draft row for review. Email and a spreadsheet are available, but no connection is confirmed. Duplicate notices sometimes arrive. Nothing should update stock automatically.

Filled-in prompt

Show the complete prompt
Help me design a practical workflow for preparing draft stock rows from supplier delivery notices.

Current process: Maya reads each notice and copies its item and quantity into a worksheet.
Trigger: a manual request after Maya selects a notice.
Approved inputs: an approved supplier notice with no customer data.
Desired output: a draft stock row for Maya to approve.
Available apps: email and spreadsheet; connection availability unknown.
Important constraints: no automatic stock update; keep item names and quantities intact; reject duplicate notices.

Return a table with: step, input, output, rule or AI contribution, validation, human owner, and failure path.

Identify where ordinary rules are enough, where AI interpretation could help, and whether an agent is needed. Include permission boundaries, duplicate-event handling, review before consequential actions, stop conditions, and a small test plan.

Do not assume the apps are connected or claim a measured time saving. Mark unknown capabilities and propose a reversible first pilot.

Boundary: Produce a workflow design and a proposed test plan only. Keep supplied facts, names, numbers, and meaning intact; leave source records, the current process, and connected systems unchanged. List proposed changes separately. Don't connect apps or execute the workflow.

Result

1. Select notice. Input: Approved notice. Output: Selected source. Owner: Maya. Failure: Missing notice stops the process.
2. Extract draft row. Input: Notice. Output: Item and quantity with a source locator. Contribution: Interpretation where wording varies. Validation: Compare with the notice.
3. Check duplicate. Input: Notice identifier. Output: Duplicate flag. Rule: Match a stable identifier where available; ask if none is supplied.
4. Review. Owner: Maya. Output: Accepted or rejected draft.
5. Record accepted row manually. No app connection or stock write is assumed.
Unknown: Which app can enforce the duplicate check and review boundary?

What I’d check or correct

I'd check that 'draft row' didn't become an automatic stock write. I'd also ask how duplicate identifiers work before accepting a plan that promises to catch every repeated email.

What to check

  • Each step has a clear input, owner, validation, and failure path.
  • The plan leaves source records, facts, names, quantities, and the live process intact; any proposed changes are listed separately.
  • Connections, duplicate handling, and review gates are supported by the actual apps.

Related pages

Sources

Share this page