Railway + Stream Deck
developer-tools · 0 triggers · 59 actions
Railway is a deployment platform for building and shipping applications with instant deployments, automatic scaling, and managed infrastructure. Add Railway 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 Railway
Add Railway 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 Railway.
Cancel Deployment
Cancel a Railway deployment that is queued or building, preventing that in-progress deployment from completing. This does not stop a running deployment and requires confirm=true.
Collect Deployment Evidence
Collect a bounded, best-effort Railway deployment evidence bundle from live-validated deployment, snapshot, event, service-instance, log, and metric sources. Results may be partial and report completeness and errors for each source. This tool performs no AI reasoning or root-cause diagnosis and does not modify code or open pull requests.
Commit Environment Changes
Commit existing staged changes for a Railway environment, completing a staged STAGE_TEMPLATE or create-environment workflow. This irreversible update can start deployments unless skip_deploys=true and requires confirm=true.
Configure Buckets and Private Network
Commit an explicit Railway patch for bucket creation, updates, or deletion and the environment private-network enabled state. Existing staged changes are not committed or replaced, and this tool does not change services, variables, or volumes. Bucket deletion is irreversible and requires confirm_destructive=true.
Create Domain
Create either a generated railway.app domain or a caller-owned custom domain. Custom-domain responses include every DNS setup record plus Railway's verification token and state.
Create Environment
Create an empty Railway environment or clone an existing environment, with explicit initial-deployment and change-staging behavior.
Create Plugin
Creates a new plugin in Railway for the specified project. Use this action when you need to add a custom plugin to a Railway project, such as for integrating external services or extending project functionality. The action requires a valid project ID (found in the Railway dashboard URL) and a descriptive name for the plugin. The plugin will be created with default settings and can be further configured after creation.
Create Project
Create a Railway project in an accessible workspace and return its project and default-environment IDs. Optionally connect a repository branch for deployment and configure the runtime, public visibility, and pull-request deployment settings.
About Railway
Railway is a deployment platform for building and shipping applications with instant deployments, automatic scaling, and managed infrastructure.
developer-tools
How to connect
1
Sign up for free
Create your Conductor Deck account: no credit card required.
2
Connect Railway
Follow the setup prompts for Railway. Conductor Deck handles the app authorization or required connection details inside the workflow builder.
3
Build a workflow
Add a Railway 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 Railway?
- Sign up for Conductor Deck, then add a Railway 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 Railway with your Stream Deck
Sign up for free and start building Railway workflows in minutes.