Get Started

Writing workflow requests

How to describe manual processes so PIILOT can build better automations.

PIILOT works best when the request describes the actual operating process, not just the tool you want to use. A strong request includes the trigger, source data, decision rules, connected tools, expected output, safety requirements, and success metric.

You do not need to write technical workflow syntax. Plain language is enough, but concrete plain language creates better automation drafts.

Inbox triage request

Weak

Automate my inbox.

Better

When a customer emails support, summarize the email, classify the issue, and create a task for the support team.

Best

When a customer emails support about billing, summarize the email, classify urgency, create a Google Task for the support lead, log the request in Google Sheets, and require approval before sending any customer-facing reply.

Recommended request shape

1 When this happens: define the trigger.
2 Use this information: name the source system and fields.
3 Decide this: describe branch logic and edge cases.
4 Do this: list actions and connected tools.
5 Pause here: identify approval gates or risky actions.
6 Success means: define the result or metric.

Request quality improves workflow quality

flowchart LR
  A[Vague request] --> B[More clarifying questions]
  B --> C[Less precise draft]
  D[Specific request] --> E[Clear trigger and actions]
  E --> F[Better graph, validation, and setup mapping]