Skip to content
Recued
Menu
← Back to recipes

Create Railway service

by recued-core v1

Approval-gated Railway empty-service creation workflow. It reads the target project and creates exactly one service with a caller-provided name through recued-core.railway. It does not connect repositories, deploy code, mutate variables, create domains or volumes, delete resources, or call arbitrary Railway GraphQL.

How it works 6 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (6 steps)
target_project_id trim
Trim whitespace from setting project id
target_service_name trim
Trim whitespace from setting service name
request_reason trim
Trim whitespace from setting reason
project ?
created_service ?
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

reason setting =
railway setting =
project id setting =
service name setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Railway connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.projectdata.servicecreate

About

Tags

railway railwayservicecreateapprovalpack:railway

Details

6 steps 4 configurable settings recipe_id: create-railway-service-intake