Create a Fly.io volume intake
Approval-gated Fly.io volume creation workflow. It reads the target app, existing volumes, and platform regions for context, validates the caller-supplied name, region, and size, then creates exactly one volume through recued-core.flyio.volume.create. It does not create machines, attach or delete volumes, extend existing volumes, mutate secrets, or call arbitrary Fly.io API routes.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (15 steps)
app_key
trim
Trim whitespace from setting app name
volume_key
trim
Trim whitespace from setting volume name
region_key
trim
Trim whitespace from setting region
has_app_name
compare
Check if app key has data
has_volume_name
compare
Check if volume key has data
has_region
compare
Check if region key has data
app
?
existing_volumes
?
regions_raw
?
skip_create
any
Check if any of the conditions are true
created_volume
?
skip: step.skip_create equal true
existing_count
count
Count items in existing volumes result
region_count
count
Count items in regions raw result
skipped
compare
Check if skip create equals true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
flyio
setting
=
region
setting
=
size gb
setting
=
10
app name
setting
=
encrypted
setting
=
true
volume name
setting
=
snapshot retention
setting
=
7
auto backup enabled
setting
=
true
require unique zone
setting
=
false
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.