Before
A user or process would need to manually send the command payload to the MCP server and wait for the response. The returned result would then need to be copied or passed back to the requesting process.
How it works
- Receive the command payload through the flowhook trigger.
- Send the payload as a JSON request to the MCP server, retrying the request when configured attempts are needed.
- Return the server response body to the calling workflow or process.
Workflow details
- Trigger: The workflow starts when a flowhook receives a command payload intended for an MCP operation.
- Request relay: The payload is packaged as JSON and sent through an HTTP POST request to the configured MCP server endpoint.
- Reliability handling: The request is configured to retry up to four times, while an unsuccessful execution stops the workflow rather than producing an incomplete result.
- Response delivery: The response body returned by the MCP server is captured as the workflow's MCP response for use by the calling process.
What changed
Command delivery and response capture now occur automatically in one workflow invocation. The calling process receives the MCP server response directly, while failed executions stop after the configured retry handling.
Work removed
Manually submitting each command payload, waiting for the server response, copying the returned response, and retrying failed requests.
Expected outcome
At least one manual request-and-response handoff is removed for each invocation, with the result returned automatically after the MCP operation completes.
