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.

What makes OpenCode different here?

OpenCode is open and model-agnostic, so you have flexibility over the underlying model. NoClick handles running it and connecting your apps as tools.

How do I give OpenCode tools?

Connect an integration node to the agent's tools handle and choose the operations to allow. Each becomes a tool the agent can call.

Do I manage any infrastructure?

No. NoClick runs the OpenCode harness in a hosted sandbox and resolves credentials for the apps you connect.

Can it combine several apps?

Yes. Add as many integrations as you need and the agent can use them together in one run.

Connect OpenCode 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 OpenCode, 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 OpenCode first calls in. opencode mcp add only saves the config. OpenCode connects when it starts — run opencode, or restart a running one.
1. Run this in your terminal
$opencode mcp add
2. Choose Remote and paste your server URL
https://mcp.noclick.app/s/<your-link>
3. Choose No when asked about OAuth authentication — the link itself is the key
<your-link> is your personal server URL — setup mints it for you.

Exact capabilities

Tools OpenCode 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 OpenCode

OpenCode is an open, model-agnostic command-line coding agent. In NoClick it runs hosted and gains your apps as tools, so it can act on real systems rather than just edit files. Wire an integration into the agent and OpenCode can use that app’s operations directly while it works. It is a flexible choice when you want an open agent with broad model support and real tool access.

Open and model-agnostic

Flexible across many underlying models

Good general-purpose tool use

Lightweight to point at a focused task

Good to know