Web request

Calls an HTTP API, which is useful for systems Malleable doesn't have a built-in integration for. Supports JSON and file-upload payloads.

The universal fallback: if a service has an API, a workflow can use it, whether that's internal tools, niche industry systems, or automation webhooks (Zapier, Make, n8n). Secrets like API tokens are stored as secret values the agents never see.

What the architect sets up

• The URL, method, and headers. API tokens are stored as secrets the agents never see
• The shape of the request body (JSON, or file uploads)
• When it runs, and what a failure should mean for the run

How it behaves in a run

• Runs when the agent decides it's needed, or automatically when a stage begins or completes.

Related

• Stages & components: how components fit into a workflow
• Showcase: see components like this at work in real workflows

For developers: the API and MCP server identify this component as web_request.