Railway
Connect Railway to Ploy to see everyone in your Railway workspace, their workspace role, and who has a role on each project. Ploy can also remove people from the workspace, change their workspace role, and change who has access to a project.
This integration is in beta
The Railway integration is in beta. It was built from Railway's documented API and has not yet been run against a live Railway workspace, so some behaviour may differ from what is described here until it has.
The first step of setup is a consent checkbox. Ticking it lets Ploy send redacted error data to its own monitoring when a call to Railway fails. Redacted means secrets, tokens and personal details are removed before anything is stored. Ploy uses it only to fix problems with the integration. You need to tick it to continue.
What Ploy reads
Every member of the connected Railway workspace, with their email address and name.
Each member's workspace role. Ploy shows it as an Admin, Member or Viewer entitlement on the workspace. Railway's dashboard calls the Viewer role Deployer.
Every project in the workspace, and each person's own role on it (Admin, Member or Viewer). People given a project from outside your workspace are shown too.
People removed from your workspace lose their access in Ploy on the next scan. Railway has no suspended state for members. Deleted projects are archived. Roles given through an access group, two-factor status and sign-in activity are not read yet.
Ploy scans every six hours. Railway's Free plan allows 100 API requests an hour, and a scan uses only a few.
What Ploy can change
Remove a person from the workspace, from a flow's "Remove user in integration" step.
Change a member's workspace role to Admin, Member or Viewer.
Grant or remove project access from a project's page in Ploy. Ploy can only add people who are already members of the workspace.
Ploy does not invite people to Railway yet; invite them from the Railway dashboard. To make changes, the token must belong to a workspace admin.
Before you start
You need a Railway token:
Sign in to Railway as a workspace admin.
Open Account Settings, then Tokens.
Create a token and choose the workspace you want Ploy to scan. This makes a workspace token, which reaches only that workspace.
Copy the token and keep it somewhere safe. Treat it like a password.
An account token (created with "No workspace") also works, but it carries everything its owner can do in every workspace they belong to, so a workspace token is the better choice. Project tokens cannot be used.
Connect Railway
In Ploy, open Integrations and choose Railway.
Tick the beta consent checkbox.
Paste the token and continue.
Choose the workspace to scan. The list shows every workspace the token can reach.
Select Test. Ploy reads the workspace's members to confirm the token works.
Save the connection. The first scan starts straight away.
Ploy scans one Railway workspace per connection. Add another connection for another workspace.
Troubleshooting
Railway refused that token for this workspace: check the token was copied in full and has not been deleted, and that it belongs to this workspace or to one of its members. Railway gives the same answer for a deleted token and one without access.
Railway could not find that workspace: choose the workspace again.
Railway is limiting requests: the plan's hourly request limit was reached. Wait a few minutes and test again.
Railway refused the change: removing people, changing roles and changing project access need a workspace admin's token.