Command Automations

Command Automations run things for you at the moment a page opens, instead of you typing a command. An automation combines:

• When — a form opens, a list opens, or either
• Where — which instances (hostname match) and tables (wildcards like sys_* allowed), optionally a URL fragment
• Then — run one of your slash commands with optional arguments, or show a reminder banner
• Controls — run at most once per page (or keep re-applying on a cooldown), and per-automation enable/disable

Manage them under Settings → Commands → Automations (/manage.html#automations).

Built-in automations

Built-ins are ready-made UX hacks — and every one of them is a working example of how automations are meant to be composed: the logic lives in a slash command you can open, read, and copy, and the automation only defines when it runs. There is no hidden behavior.

The first built-in, Expanded messages & filters (included with Community), fixes one of the platform's oldest annoyances: the form message output area and the list filter condition builder are capped at a 260px strip, and multi-select filter boxes show only a few options. It simply runs the /expand command automatically on every form and list, re-applying on a cooldown so it also catches the condition builder after you expand it. Want different sizes? Open /expand under Commands, duplicate it as a custom command with your own values, and point your own automation at it — that's the whole pattern.

More built-in UX hacks will follow. Every built-in can be scoped to specific instances or tables after activation.

Building your own (Pro)

With Pro you can build automations that either run any of your slash commands or show your own reminder banner — for example:

• Open your timer command whenever an incident form opens on production
• Run a list-formatting command every time you open a specific table's list
• Show a custom warning ("Careful — {table} on {host}") on tables your team considers sensitive
• Auto-apply your own page tweak as a script command — uncheck run at most once per page so it re-applies (on a cooldown) and also catches elements that appear later

Automations pause while the slash command palette is open, so a repeating automation never interferes with what you're typing.

Banner messages and command arguments support the placeholders {table}, {sysid}, and {host}. Banners come in three styles: info and warning auto-dismiss, alert stays until dismissed.

The Pro Trial includes up to three automations. If the trial ends, your automations are kept — visible, editable, exportable — but they pause until you upgrade, then resume exactly as configured.

Safety

• Automations never block a save; they only react after a page is ready.
• A failing automation can never break the form — errors are isolated and logged to the console.
• Each automation can be disabled individually, and built-ins never touch data by design.