An automation builder for workflows that need to run the same way every time. You build a flow from steps, and none of the step types asks an AI model to decide what happens next.
What this demo shows in Hollow Cascade
Review an automation and its run history.
An automation shows the steps it follows.
The view switches to the automation’s run history.
Hollow Cascade demo
Step types and execution rules
Nine step types cover most of what a workflow needs to do:
HTTP calls out to any external HTTP or HTTPS endpoint, with server-side SSRF protection, and passes the status code and the parsed JSON body into whatever comes next.
Connector talks to OAuth integrations, Slack, GitHub, Notion, Google Sheets, using credentials secured server-side rather than in the flow itself.
Hollow runs an action in one of your Hollow apps directly as a step, such as creating tasks, setting workbook cells or creating and listing contacts.
Code runs your own logic in an isolated sandbox, written in HollowScript (with declared uses capability statements), JavaScript, or Python.
Filter checks one or more conditions (equals, contains, is set, greater than and so on, matching all or any) against earlier step outputs, then continues, branches or stops cleanly.
Loop runs one action for each item of an array a prior step produced, with a maximum-iteration guard (20 by default, never more than 50) so nothing runs away. A loop cannot contain another loop; use Call cascade for that.
Wait pauses the flow for a number of seconds before the next step.
Approval stops the flow until you, the cascade owner, approve or reject it, then follows the success or failure route.
Call cascade runs another of your cascades as a step, so a common routine can be built once and reused.
Data expressions and Secrets Vault
Pull a value from an earlier step with {{ steps.step-name.outputs.field }} (the step name in lower case with hyphens; HTTP responses are under body). Keep API keys and private tokens out of the flow entirely: store them in the Secrets Vault and reference them as {{ secrets.NAME }} in HTTP headers and bodies and in Hollow step inputs. Secrets Vault values are stored encrypted and are masked in run logs, outputs and previews.
Triggers and execution logs
Run a flow on demand, on a cron schedule (standard 5-field syntax), from an inbound webhook URL, or on a Hollow event. The Runs view keeps the 50 most recent runs of each cascade, with per-step status, timings, logs, errors and output, and a replay for runs that have a stored trigger payload. Settings can send an alert when a run fails.