deployment_trigger
Trigger new deployments for Railway services to deploy code changes, apply configuration updates, or roll back to previous states using specific commit SHAs.
Instructions
[API] Trigger a new deployment for a service
⚡️ Best for: ✓ Deploying code changes ✓ Applying configuration updates ✓ Rolling back to previous states
⚠️ Not for: × Restarting services (use service_restart) × Updating service config (use service_update) × Database changes
→ Prerequisites: service_list
→ Alternatives: service_restart
→ Next steps: deployment_logs, deployment_status
→ Related: variable_set, service_update
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"projectId": "<projectId>",
"serviceId": "<serviceId>",
"environmentId": "<environmentId>",
"commitSha": "<commitSha>"
},
"name": "deployment_trigger"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | ID of the project | |
| serviceId | Yes | ID of the service | |
| environmentId | Yes | ID of the environment | |
| commitSha | Yes | Specific commit SHA from the Git repository |