Approval-gated Render workflow for triggering one deploy on one service. It reads service and recent deploy context, then calls recued-core.render.deploy.create with the documented clearCache body field. It does not update service settings, create jobs, mutate env vars/secrets, suspend/resume services, delete resources, reveal credentials, or call arbitrary Render API routes.

How it works 11 steps

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

Process (11 steps)

■ normalized_service_id trim

Trim whitespace from setting service id

■ normalized_clear_cache trim

Trim whitespace from setting clear cache

■ normalized_reason trim

Trim whitespace from setting reason

■ service ?

■ deploys_before_raw ?

■ trigger_deploy ?

■ deploys_before default

Apply default

■ deploy_count_before count

Count items in deploys before

■ deploy_rows slice

Take a subset of

■ deploy_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 4 configurable

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

reason setting =

render setting =

service id setting =

clear cache setting = do_not_clear