Approval-gated Heroku app creation workflow. It reads current account, regions, stacks, and existing apps for context, then creates exactly one app through recued-core.heroku.app.create. It does not create dynos, builds, domains, config vars, add-ons, pipelines, teams, spaces, log sessions, or arbitrary Heroku API calls.

How it works 17 steps

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

Process (17 steps)

■ app_key trim

Trim whitespace from setting app name

■ region_key trim

Trim whitespace from setting region

■ stack_key trim

Trim whitespace from setting stack

■ has_app_name compare

Check if app key has data

■ account_context ?

■ regions_raw ?

■ stacks_raw ?

■ existing_apps_raw ?

■ created_app ?

skip: step.has_app_name not_equal true

■ created_app_read ?

skip: step.has_app_name not_equal true

■ regions default

Apply default

■ stacks default

Apply default

■ existing_apps default

Apply default

■ region_count count

Count items in regions

■ stack_count count

Count items in stacks

■ existing_app_count count

Count items in existing apps

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

stack setting = heroku-24

heroku setting =

region setting = us

app name setting =

feature flags setting =