Create a Fly.io app intake
Use “Create a Fly.io app intake” in Recued. It runs the provider records app creation workflow with approval before changes are made.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (16 steps)
app_key
trim
Trim whitespace from setting app name
org_key
trim
Trim whitespace from setting org slug
network_key
trim
Trim whitespace from setting network
has_app_name
compare
Check if app key has data
has_org_slug
compare
Check if org key has data
token_raw
recued-core.flyio.token.current
Current token on flyio
regions_raw
recued-core.flyio.region.search
Search region on flyio
existing_apps
recued-core.flyio.app.search
Search app on flyio
skip_create
any
Check if any of the conditions are true
created_app
recued-core.flyio.app.create
Create app on flyio
skip: step.skip_create equal true
created_app_read
recued-core.flyio.app.read
Read app on flyio
skip: step.skip_create equal true
token_count
count
Count items in token raw result
region_count
count
Count items in regions raw result
existing_app_count
count
Count items in existing apps result
skipped
compare
Check if skip create equals true
card
to_summary
Format results as a summary card
▼
Output
summary
card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
network
setting
=
app name
setting
=
org slug
setting
=
personal
enable subdomains
setting
=
true
Uses (5 operations)
Pack operation
Current token on flyio
recued-core.flyio.token.current
Pack operation
Search region on flyio
recued-core.flyio.region.search
Pack operation
Search app on flyio
recued-core.flyio.app.search
Pack operation
Create app on flyio
recued-core.flyio.app.create
Pack operation
Read app on flyio
recued-core.flyio.app.read
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.