Build a workflow pilot
build_workflow_pilotBuilds a pilot plan for one workflow, typically the first one prioritize_automation_workflows recommends, from 11 caller-supplied facts. Returns pilot steps, review gates, acceptance checks and a Markdown plan. It does not connect accounts, start provider work, store a plan, send messages or execute the workflow.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"workflowName": "<workflowName>",
"trigger": "<trigger>",
"inputDescription": "<inputDescription>",
"desiredOutput": "<desiredOutput>",
"sourceSystem": "<sourceSystem>",
"destinationSystem": "<destinationSystem>",
"currentSteps": "<currentSteps>",
"reviewOwner": "<reviewOwner>",
"riskLevel": "<riskLevel>",
"sensitiveData": "<sensitiveData>",
"successChecks": "<successChecks>"
},
"name": "build_workflow_pilot"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| trigger | Yes | What starts the workflow, e.g. 'a supplier invoice email arrives'. | |
| riskLevel | Yes | Cost of a wrong output: low, medium or high, as the user judges it. | |
| constraints | No | Limits the plan must respect. Optional. | |
| reviewOwner | Yes | Person or role who approves drafts before they are used. | |
| currentSteps | Yes | Today's steps in order, 1 to 8, in the user's words. | |
| sourceSystem | Yes | System the inputs come from, e.g. Gmail. | |
| workflowName | Yes | Short name of the workflow, as the user calls it. | |
| desiredOutput | Yes | The result the user wants at the end. | |
| sensitiveData | Yes | True if the inputs include personal, financial, health or confidential data. | |
| successChecks | Yes | 1 to 6 checks that show the pilot worked, from the user. | |
| inputDescription | Yes | The inputs the workflow reads, as the user describes them. | |
| destinationSystem | Yes | System the approved result goes to, e.g. QuickBooks. | |
| systemsAlreadyUsed | No | Other tools the team already uses. Optional. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| steps | Yes | ||
| tools | Yes | ||
| status | Yes | ||
| rollout | Yes | ||
| unresolved | Yes | ||
| limitations | Yes | ||
| reviewGates | Yes | ||
| workflowName | Yes | ||
| pilotMarkdown | Yes | ||
| suppliedFacts | Yes | ||
| recommendation | Yes | ||
| acceptanceChecks | Yes | ||
| readyToUsePrompt | Yes |