Recued
Menu
← Back to recipes

Fly.io fleet operations digest

by recued-core v1 8 views

Use “Fly.io fleet operations digest” in Recued. It provides a scheduled, read-only digest for provider records operations.

How it works 23 steps

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

Process (23 steps)
org_key trim
Trim whitespace from setting org slug
token_raw ?
apps_raw ?
machines_raw ?
volumes_raw ?
regions_raw ?
defaults defaults
Apply defaults
token_count count
Count items in tokens
app_count count
Count items in apps
machine_count count
Count items in machines
volume_count count
Count items in volumes
region_count count
Count items in regions
has_attention_items any
Check if any of the conditions are true
notify_enabled compare
Check if setting notify when attention needed equals true
should_notify all
Check if all conditions are true
notify ?
skip: step.should_notify not_equal true
app_rows slice
Take a subset of
machine_rows slice
Take a subset of
volume_rows slice
Take a subset of
app_table to_table
Format results as a data table
machine_table to_table
Format results as a data table
volume_table to_table
Format results as a data table
card to_summary
Format results as a summary card
Settings 9 configurable

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

flyio setting =
channels setting = in_app
end hour setting = 10
org slug setting = personal
weekdays setting = 1,2,3,4,5
page size setting = 50
row limit setting = 10
start hour setting = 8
notify when attention needed setting = true

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Send notificationsRead your Flyio connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

flyio flyiofly.iomachinesappsvolumesdigestnotificationpack:flyio

Details

23 steps 9 configurable settings recipe_id: fleet-operations-digest-flyio