As your automations multiply, you want one to call another without copy-pasting logic between them. This bridge turns every workflow into a callable tool with a clear contract.
sonnet1 weekWebhookRESTRedisPostgres
Claude
85ROI
84Scale
$3.7k93Saved
ROI for
README.md
Why this subagent
As your automations multiply, you want one to call another without copy-pasting logic between them. This bridge turns every workflow into a callable tool with a clear contract.
It validates each call against the target's schema, forwards it with a correlation id, and returns the typed result. That gives you a composable backbone where an agent can chain workflows together, and every hop shows up in one run log you can trace end to end.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Validate an incoming call against the target workflow's schema before forwarding it.
pending
Invoke the downstream workflow, carrying a correlation id so the chain stays traceable.
pending
Return the result to the caller and record the call in a shared run log.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Given a tool call naming a registered workflow and arguments, validate against its schema, invoke it, and return the typed result with a correlation id.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.