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 Codex get access to my apps?

You connect an integration to the agent's tools handle and select which operations to expose. Codex then calls those operations as tools, authenticated with the credentials you connect in NoClick.

Is this the same Codex CLI?

Yes. NoClick runs the Codex harness for you and adds your connected apps as tools. You do not have to install or manage anything locally.

Can I trigger a Codex agent automatically?

Yes. Because it runs hosted, you can start it from a schedule, a webhook, or another app event, not just by hand.

Which apps can I connect?

Any of NoClick’s tool-provider integrations, from Slack and Linear to GitHub, Notion, Google Sheets, Postgres, and dozens more.

Codex

Connect Codex 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 Codex, 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 Codex first calls in. Codex connects when a session starts — run codex, or restart a running one.
Run this in your terminal
$codex 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 Codex 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 Codex

Codex is OpenAI's command-line coding agent. NoClick runs it as a hosted agent and lets you connect your apps to it as tools, turning it from a coding assistant into an operator that can act across your systems. Connect an integration to the agent and Codex can query, create, and update records in that app directly. You keep the Codex experience and give it real reach into the tools your team already uses.

Fast, capable code generation and editing

Good at well-scoped, concrete tasks

Strong at API and data manipulation

Familiar to teams already on OpenAI tooling

Good to know