Skip to content
Recued
Menu
← Back to recipes

Create a Fly.io app intake

by recued-core v1

Approval-gated Fly.io app creation workflow. It reads current token metadata, platform regions, and existing apps for context, validates the caller-supplied app name and organization slug, then creates exactly one app through recued-core.flyio.app.create. It does not create machines or volumes, delete apps, mint deploy tokens, mutate secrets, assign IPs, or call arbitrary Fly.io API routes.

How it works 16 steps

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 ?
regions_raw ?
existing_apps ?
skip_create any
Check if any of the conditions are true
created_app ?
skip: step.skip_create equal true
created_app_read ?
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
Settings 5 configurable

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

flyio setting =
network setting =
app name setting =
org slug setting = personal
enable subdomains setting = true

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 Flyio connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

flyio flyiofly.ioappcreateintakeapprovalpack:flyio

Details

16 steps 5 configurable settings recipe_id: create-flyio-app-intake