Approval-gated Railway custom domain workflow. It reads the target service context, creates exactly one custom domain through recued-core.railway, then lists service domains for DNS review. It does not delete domains, mutate variables, deploy services, change ports beyond the requested target port, or call arbitrary Railway GraphQL.

How it works 11 steps

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

Process (11 steps)

■ target_project_id trim

Trim whitespace from setting project id

■ target_environment_id trim

Trim whitespace from setting environment id

■ target_service_id trim

Trim whitespace from setting service id

■ target_domain trim

Trim whitespace from setting domain

■ request_reason trim

Trim whitespace from setting reason

■ service ?

■ created_domain ?

■ domains_raw ?

■ custom_domains default

Apply default

■ domain_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 7 configurable

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

domain setting =

reason setting =

railway setting =

project id setting =

service id setting =

target port setting = 0

environment id setting =