Integrations / Railway
Railway
Cron schedules on services, with deployment state.
Why connect it
Railway cron services run on a schedule you set once. The API exposes the schedule and the latest deployment's status — enough to see a schedule whose service is crashed.
What you'll see
- Every service instance with a cron schedule
- Latest deployment status as the failing signal
- No per-run history: the page says so
What the credential can and cannot do
Where to get it: railway.app → Account Settings → Tokens (account token reads all projects).
It grants: Read on projects, services, deployments. Account tokens can also deploy; GitDoctor only reads.
It cannot: GitDoctor never deploys or changes schedules.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.