Railway project operations digest
Scheduled read-only Railway digest for one project. It reads the project, environments, project members, and recent deployments through recued-core.railway, renders compact operations tables, and can send an in-app notification when deployments are present. It does not create, deploy, restart, stop, roll back, mutate variables, mutate domains or volumes, delete resources, or call arbitrary Railway GraphQL.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (22 steps)
target_project_id
trim
Trim whitespace from setting project id
project
?
environments_raw
?
members_raw
?
deployments_raw
?
environments
default
Apply default
members
default
Apply default
deployments
default
Apply default
environment_count
count
Count items in environments
member_count
count
Count items in members
deployment_count
count
Count items in deployments
has_deployments
compare
Check if deployment count is greater than 0
notify_enabled
compare
Check if setting notify when deployments equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
environment_rows
slice
Take a subset of
member_rows
slice
Take a subset of
deployment_rows
slice
Take a subset of
environment_table
to_table
Format results as a data table
deployment_table
to_table
Format results as a data table
member_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
railway
setting
=
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
row limit
setting
=
15
project id
setting
=
start hour
setting
=
8
notify when deployments
setting
=
true
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.