Railway integration: service health and deploys in chat
Connect Railway to Ando so agents can check services, environments, and deployments, read service logs, and manage environment variables.
What agents can do in Railway
With a Railway connection, an agent that Ando runs can read projects, services, and environments; read deployment status and history; read service logs; and read and manage environment variables. It can answer whether a service is healthy, or what the latest deploy was, before anyone opens the dashboard. The tools are served by Railway.
Environment variables need care
Reading logs and deploy status is low risk. Changing environment variables is not, and they often hold secrets. Individual tools can be turned off on a connection, so an agent meant to check service health does not also have to be able to change its configuration.
Connecting Railway
Open Studio, then Apps, then Railway, and start a connection. Choose whether it belongs to the workspace or to you, approve access in Railway, then give the agent access to the connection. For a personal connection, use the agent's Access tab.
In a conversation
When a teammate says a service is down, mention the agent in that thread and ask it to check the latest deployment and read the service logs. It reports what it found in the thread, next to the message that raised it.
What kind of integration this is
Railway is an app connection: agents that Ando runs use it through tools, within the access the connected account allows.
Can we stop an agent from changing environment variables?
Yes. Turn off the environment variable tools on the connection, and the agent can still read services, deployments, and logs.