Do I need an API key?

Only if the target URL requires authentication. You can include API keys or Bearer tokens in the Headers (JSON) field.

Can I use this with local/internal endpoints?

Yes, as long as the Stream Deck desktop app can reach the URL on your network. Localhost, LAN IPs, and VPN-routed addresses all work.

What HTTP methods are supported?

GET, POST, PUT, and DELETE are available in the dropdown. PATCH and other verbs are not exposed yet.

Can I read the response in later actions?

Yes. The response body, status code, and headers are available as output fields. Insert one from the variable picker in a later step and it writes a reference like {{nodes. .output.body}}.

Is there a request timeout?

Yes — if the server does not respond within a sensible window the action will fail and trigger your workflow error path.

Web Request + Stream Deck

System · 1 action

Send or fetch data from any website or online service. Trigger Web Request actions from your Stream Deck with a single button press and configure any required fields in the workflow builder.

Build a Web Request workflow — free See how it works

No code
Free tier
One Stream Deck press
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Triggers & actions

Steps your workflow can perform in Web Request.

Web Request

Send an HTTP request to a URL.

Use cases

Call any REST API from your Stream Deck

Trigger POST, GET, PUT, or DELETE requests to internal tools, home-automation hubs, or third-party services with one button press.

Toggle IoT devices

Turn lights on/off, change thermostat modes, or start a 3D printer by hitting a Stream Deck button that calls your smart-home API.

Send webhook notifications on demand

Ping Slack, Discord, or a custom alert endpoint instantly — useful for stream-start announcements or panic buttons.

Chain HTTP with logic nodes

Use the response body from an HTTP request as input for later workflow steps, creating fully automated multi-step flows.

How to connect

Sign up for free

Create your Conductor Deck account — no credit card required.

Open the workflow builder

Start a new workflow and choose Web Request from the built-in tools. There is no OAuth connection or separate app authorization step.

Build a workflow

Add a Web Request action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Assign to Stream Deck

Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.

Frequently asked questions

Do I need an API key?: Only if the target URL requires authentication. You can include API keys or Bearer tokens in the Headers (JSON) field.
Can I use this with local/internal endpoints?: Yes, as long as the Stream Deck desktop app can reach the URL on your network. Localhost, LAN IPs, and VPN-routed addresses all work.
What HTTP methods are supported?: GET, POST, PUT, and DELETE are available in the dropdown. PATCH and other verbs are not exposed yet.
Can I read the response in later actions?: Yes. The response body, status code, and headers are available as output fields. Insert one from the variable picker in a later step and it writes a reference like {{nodes.<id>.output.body}}.
Is there a request timeout?: Yes — if the server does not respond within a sensible window the action will fail and trigger your workflow error path.

Automate Web Request with your Stream Deck

Get started free View pricing

Related System integrations