Appearance
Railway
Deploy and manage projects, services, and environments on Railway.
| Detail | Value |
|---|---|
| Category | Cloud & Infra |
| Base URL | https://backboard.railway.app/graphql/v2 |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | railway |
Using Railway in a workflow
- Go to Connections and click New Connection.
- Pick Railway from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /projects | List projects |
POST /projects | Create a project |
GET /projects/{projectId} | Get project details |
GET /projects/{projectId}/services | List services |
POST /projects/{projectId}/services | Create a service |
GET /projects/{projectId}/deployments | List deployments |
POST /deployments/{deploymentId}/redeploy | Redeploy |
GET /projects/{projectId}/environments | List environments |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /projects
List projects
| Detail | Value |
|---|---|
| Operation ID | cloud.listProjects |
| Method | GET |
| Path | /projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listProjects. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
POST /projects
Create a project
| Detail | Value |
|---|---|
| Operation ID | cloud.createProject |
| Method | POST |
| Path | /projects |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
GET /projects/{projectId}
Get project details
| Detail | Value |
|---|---|
| Operation ID | cloud.getProject |
| Method | GET |
| Path | /projects/{projectId} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.getProject. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
GET /projects/{projectId}/services
List services
| Detail | Value |
|---|---|
| Operation ID | cloud.listServices |
| Method | GET |
| Path | /projects/{projectId}/services |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listServices. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
POST /projects/{projectId}/services
Create a service
| Detail | Value |
|---|---|
| Operation ID | cloud.createService |
| Method | POST |
| Path | /projects/{projectId}/services |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.createService. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
GET /projects/{projectId}/deployments
List deployments
| Detail | Value |
|---|---|
| Operation ID | cloud.listDeployments |
| Method | GET |
| Path | /projects/{projectId}/deployments |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listDeployments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
POST /deployments/{deploymentId}/redeploy
Redeploy
| Detail | Value |
|---|---|
| Operation ID | cloud.redeployDeployment |
| Method | POST |
| Path | /deployments/{deploymentId}/redeploy |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.redeployDeployment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.
GET /projects/{projectId}/environments
List environments
| Detail | Value |
|---|---|
| Operation ID | cloud.listEnvironments |
| Method | GET |
| Path | /projects/{projectId}/environments |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Railway connection from the Connection dropdown.
- In the Operation dropdown, select
cloud.listEnvironments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Railway API reference.