Get workflow template
get_workflow_templateReturns one shipped workflow chart template by key (see list_workflow_templates), with the child workflows it calls, every question it can ask (each prompt.id, with its options) and every way it can end, and the API calls that install and run it. Its whole usage contract, with example webhooks and answers, is GET /api/v2/workflow-templates/{key}/usage.md (or /usage for JSON), readable before anything is installed. Unmodified, install it with POST /api/v2/workflow-templates/{key}/install (body {"publish": true}), which installs its child workflows too ("replace": true re-installs over the ones the app already has); adapted (check with validate_workflow_chart), install it with PUT /api/v2/workflows/{key} (publish: true), each child first. Then run it with POST /api/v2/connections/{connection_id}/workflow-runs with an input matching the chart's declared inputs, on a realtime or simulated connection: a standard one answers 422 with errors.code realtime_required and nothing stored, so the same call starts the run once the connection is upgraded. An installed workflow is a copy: when the template changes later, GET /api/v2/workflows/{key} says so in template.status (update_available), and installing it again with "replace": true takes the new version.
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": {
"key": "<key>"
},
"name": "get_workflow_template"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | The template key. |