Webhook + Stream Deck
System
Trigger a workflow via an incoming HTTP webhook request. Start workflows with Webhook and configure the trigger in the workflow builder.
- No code
- Free tier
- Starts workflows automatically
- Pairs with OBS & Elgato tools
- OAuth & keys handled in-builder
Use cases
Receive real-time events from other apps
Generate a unique Conductor Deck webhook URL and paste it into Zapier, Pipedream, GitHub Actions, or your own server to trigger workflows remotely.
Start a workflow from a CI/CD pipeline
Kick off a Stream Deck notification, light show, or OBS scene switch the moment your deployment finishes by calling the webhook.
Bridge unsupported services
If a service is not in the Conductor Deck catalog yet, pipe its events through a generic webhook action and parse the JSON payload in your workflow.
Build two-way automations
Combine incoming webhooks with outgoing HTTP requests to create bidirectional sync between Conductor Deck and external platforms.
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 Webhook from the built-in tools. There is no OAuth connection or separate app authorization step.
Build a workflow
Add a Webhook trigger to your visual workflow canvas. Configure the options you need, then connect it to other steps.
Let it run on its own
Your workflow starts whenever its Webhook trigger fires. No key press needed; you can still sync it to a Stream Deck button for a manual run.
Frequently asked questions
- Where do I find my webhook URL?
- Create a Webhook trigger node in a Conductor Deck workflow. The URL is displayed in the node settings and is unique to that workflow.
- What payload format is accepted?
- Standard JSON bodies are parsed automatically. URL-encoded form data is also supported. Binary uploads are not accepted.
- Is the webhook URL authenticated?
- Each URL contains a unique token in the path. Keep it private — anyone with the URL can trigger the workflow. Rotate it from the node settings if needed.
- Can I inspect the payload inside the workflow?
- Yes. The JSON body is available as an output field (e.g. {{webhook.body}}) and can be referenced in later actions or condition nodes.
- What happens if the webhook receives too many requests?
- Requests are queued and executed in order. If the queue grows beyond a threshold, older unprocessed payloads may be dropped. Check the Activity Log for overflow warnings.
Automate Webhook with your Stream Deck
Sign up for free and start building Webhook workflows in minutes.