DeployHQ + Stream Deck
developer-tools · 0 triggers · 60 actions
Deployment made simple. We make it super easy to automate deploying projects from Git, SVN and Mercurial repositories. Add DeployHQ to your Stream Deck workflows with guided setup for the connection details it needs.
- No code
- Free tier
- One Stream Deck press
- Pairs with OBS & Elgato tools
- OAuth & keys handled in-builder
Popular ways to use DeployHQ
Add DeployHQ to a workflow and pair it with a Stream Deck button to run it in one press — handy for developer-tools tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.
Browse all templatesTriggers & actions
Steps your workflow can perform in DeployHQ.
Create Config File Deployment
Tool to create a new config file deployment for a project. Use when you need to deploy only configuration files to a server or server group without deploying code changes.
Create Project
Tool to create a new project in DeployHQ. Use when you need to initialize a new project with a name and optional zone configuration.
Get Project
Tool to view an existing project in DeployHQ. Use when you need to retrieve details about a specific project by its permalink or identifier.
Get Project Deployments
Tool to retrieve a paginated list of all deployments in a project. Use when you need to view deployment history for a specific project. Results are paginated with 10 deployments per page.
Get Project Servers
Tool to retrieve all servers configured for a project. Use when you need to view server configurations and deployment targets for a specific project.
Get Projects
Tool to retrieve all projects from DeployHQ account. Use when you need to list all available projects and their configurations.
Get Repository Branches
Tool to view all available branches in the connected repository for a project. Use when you need to list repository branches and their commit hashes.
Get Templates
Retrieves all deployment templates from the DeployHQ account. Templates in DeployHQ are reusable configurations that can be used to quickly set up new projects with predefined settings. This action returns the name, permalink (unique identifier), and description for each template. Use this when you need to: - List all available templates in the account - Find a template's permalink for use in other operations - Discover what templates exist before creating or modifying projects No parameters are required - this returns all templates in the account.
About DeployHQ
Deployment made simple. We make it super easy to automate deploying projects from Git, SVN and Mercurial repositories.
developer-tools
How to connect
1
Sign up for free
Create your Conductor Deck account: no credit card required.
2
Connect DeployHQ
Follow the setup prompts for DeployHQ. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
3
Build a workflow
Add a DeployHQ action to your visual workflow canvas. Configure the options you need, then connect it to other steps.
4
Assign to Stream Deck
Sync your workflow to any Stream Deck button. Press once to trigger the entire sequence.
Frequently asked questions
- How do I connect DeployHQ?
- Sign up for Conductor Deck, then add a DeployHQ step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
- Is it free?
- Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
- What's the difference between a trigger and an action?
- A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.
Automate DeployHQ with your Stream Deck
Sign up for free and start building DeployHQ workflows in minutes.