- Integrations
- /
- Railway
- /
- Actions
- /
- Railway List Projects
ActionRailwayUpdated May 2026
What Railway projects do I have?
Short answer: Drop the "Railway → Railway List Projects" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Sample request
{}
Returns
{"data": {"projects": {"edges": [{"node": {"id": "proj123","name": "My App","createdAt": "2026-01-01T00:00:00Z"}}]}}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Railway List Projects.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Railway List Projects.
What does the Railway List Projects action do in Railway?
Returns every project in the org. Useful for resolving project IDs at workflow setup and for cross-project automation.
What inputs does Railway List Projects require?
Railway List Projects has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Railway returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Railway List Projects support batch operations?
Yes. Run Railway List Projects inside a Loop node to process arrays. Tiny Command handles Railway's rate limits automatically so you don't have to throttle manually.
More actions
Other Railway actions.
Send railway list projects from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.