What can the HTTP Request node connect to?

It can call any service that exposes an HTTP REST API or webhook. This makes it the way to integrate tools that do not yet have a dedicated NoClick node, from internal services to niche SaaS products.

Which HTTP methods does the node support?

The node supports GET, POST, PUT, PATCH, and DELETE. Each method lets you set a target URL and custom headers, and the write methods accept a JSON request body.

Can I pass data from earlier nodes into a request?

Yes. You can reference upstream output inside the URL, headers, or body using the {{nodeId.output.field}} syntax. This lets you build dynamic requests from data produced earlier in the workflow.

How do I authenticate HTTP requests?

The node supports API key authentication via a custom header, HTTP Basic authentication with a username and password, and Bearer token authentication. You can also pass credentials through custom headers if a service needs a different scheme.

Can the node both send and receive webhooks?

It handles the outbound side: you can POST to any webhook URL to notify external systems. To receive inbound webhooks that start a workflow, use NoClick's dedicated webhook trigger instead.

How does OpenClaw act on my apps?

You connect an integration to the agent's tools handle and select operations. OpenClaw calls those operations as tools while it runs.

Is there anything to install?

No. NoClick runs the OpenClaw harness for you in a hosted sandbox.

Can I run it on a schedule?

Yes. A hosted agent can be started from a schedule, a webhook, or another app event.

Which apps can it use?

Any of NoClick’s tool-provider integrations across communication, CRM, developer tools, databases, and more.

Connect OpenClaw to HTTP Request

Point an AI agent at the HTTP Request tool and it calls any REST API on its own instead of describing the call. It can send GET, POST, PUT, PATCH, and DELETE requests, so it reads data, creates records, and updates them across any service that speaks HTTP. Wire it into a hosted coding agent in NoClick and it reaches an API you have no dedicated node for and acts on the response.

Loading preview…

Opens a workflow with 5 tools ready to use.

What happens next

Set up in minutes

The open button drops you into a guided setup. It asks exactly this, nothing else:

Choose where it runs
On your computer through your own OpenClaw, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in HTTP Request
A preset of real HTTP Request operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect HTTP Request
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your OpenClaw first calls in. OpenClaw probes the server while adding it, so this lights up during openclaw mcp add.
Run this in your terminal
$openclaw mcp add noclick --url https://mcp.noclick.app/s/<your-link>
<your-link> is your personal server URL — setup mints it for you.

Exact capabilities

Tools OpenClaw gets

Pick the operations you want and each becomes a tool the agent can call directly while it works.

HTTP Request

5 tools

Send Http Get Request

HTTP GET request configuration

Send Http Post Request

HTTP POST request configuration

Send Http Put Request

HTTP PUT request configuration

Send Http Patch Request

HTTP PATCH request configuration

Send Http Delete Request

HTTP DELETE request configuration

Starting points

What you can build

Call an internal microservice API with a POST request and pass the response into the next node.

Fetch JSON from a third-party REST endpoint with a GET request and parse the fields you need downstream.

Send an outbound webhook to notify an external system when a workflow reaches a certain step.

Update a record in a SaaS tool that has no dedicated node by sending a PATCH request with the changed fields.

Delete a stale resource in an external system with a DELETE request triggered on a schedule.

Chain several API calls together, using the output of one HTTP request as the input body of the next.

Meet the runner

About OpenClaw

OpenClaw is an open command-line agent. NoClick runs it hosted and lets you connect your apps to it as tools, so it can take real actions across your systems. Wire an integration into the agent and OpenClaw can call that app’s operations directly. It is a good fit when you want an open, no-fuss agent with real tool access and nothing to install.

Open and approachable

Simple to point at a task

Solid general tool use

Hosted, with nothing to install

Good to know