Empty Automations State
Empty automations panel pairing a build from scratch action with three starter template recipe rows and a facts row on run speed and quota.
Empty automations panel pairing a build from scratch action with three starter template recipe rows and a facts row on run speed and quota.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Empty Automations State is the panel shown before any rules exist. A New rule button sits beside the Automations heading, and the body centers a Workflow icon, the line No automation rules yet, and a note that rules watch for a trigger and run an action for you. A Start from a template list follows, each row rendered as a trigger to action recipe, auto triage new issues, close stale tickets, escalate urgent bugs, with its own Use template button. A facts row closes the panel with run speed, the monthly quota, and version history.
The templates and facts are separate const arrays, so the recipe rows and the closing bullets each live in one place. Pairing ready made recipes with the build from scratch action is the point: a blank canvas asks the user to invent a rule, while the templates show exactly what a trigger and an action look like before the first one is saved.
Reach for this block on an automations index when the workspace has no rules configured, wired to the empty branch of your rules fetch. Point New rule at your builder route and each Use template button at the prefilled recipe, and keep the facts row honest about run latency and the plan quota.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the first-time automations surface. Other empty rule states:
Tip: lead the empty state with real templates so the user sees what a trigger and an action look like before building.