VibeControls
Ask AI
Automation3 illustrations

Actions and One-Click Ops Decks

Turn commands, scripts and webhooks into reusable actions, then pin them to one-click decks your team and on-call rotation can run.

These images are illustrations of the concept, not screenshots of the actual product.

Overview

Actions and ops decks are the concept for capturing the operational work a team repeats every week, such as restarting a service, running migrations, tailing an error log, paging on-call or rolling back a release, and making it runnable in one click. An action wraps a command, a script or a webhook call with its trigger, tags and run history. A deck arranges chosen actions as large tiles on a command board, and a shared deck gives a narrow, safe version of that board to people who should be able to run operations but not change them.

The problem is that runbooks tend to live in wikis, shell history and a few senior engineers' heads. Every incident becomes a hunt for the right command and the right machine, and every run is hard to trace afterwards. The design envisions a single library where each operation is defined once, labeled by type and trigger, counted every time it runs, and guarded by a confirmation when it is risky.

The illustrations move from definition to execution. The Actions library shows cards with type badges for command, script and webhook, trigger labels such as manual, on demand, event and scheduled, tags like deploy, prod and on-call, run counts and the time of the last run, alongside search, type and trigger filters and bulk execute, duplicate and delete. The Vibe Deck screen presents a board per context, with sample decks for production ops, staging, an ML pipeline and incident response, and tiles flagged with warnings for risky operations like a production rollback. Preview and edit modes, Share deck and Public link controls sit in the header. The phone illustration shows a shared on-call deck: a title, a short promise of safe, pre-approved operations, a Can execute badge and six tiles showing running, succeeded and caution states.

Actions are also the building blocks for the rest of the Automation section. Scheduled jobs are designed to run an action on a timetable, and every run is meant to land in the audit trail, so one definition serves an engineer at a desk, a teammate on a phone at night and a nightly schedule.

What this concept shows

  • Action library covering commands, scripts and webhooks with manual, on-demand, event and scheduled triggers
  • Run counts, last-run times and tags on every action card
  • Search plus type and trigger filters, with bulk execute, duplicate and delete for selected actions
  • Confirmation requirement flagged on risky actions such as a production rollback
  • Multiple named decks per workspace, such as production ops, staging, an ML pipeline and incident response
  • Large one-click tiles grouped by labels like ops and alerts, with warning markers on risky operations
  • Share deck and Public link controls with a preview and edit toggle
  • A shared phone deck limited to pre-approved operations, showing running, success and caution states per tile

How it works

  1. Create an action for a command, script or webhook and give it a trigger and tags.
  2. Find and manage actions with search and the type and trigger filters, or select several to execute, duplicate or delete together.
  3. Build a deck, such as a production ops board, by adding actions as one-click tiles and labeling them.
  4. Switch between decks for staging, pipelines or incident response and run an operation with a single click, confirming the risky ones.
  5. Share the deck or create a public link so on-call teammates can run the pre-approved tiles from their phones.

Who it's for

  • On-call and site reliability engineers
  • DevOps and platform engineers who maintain runbooks
  • Developers who repeat the same operational commands across machines
  • Engineering managers who want safe self-service operations for the wider team

Illustrations

3 illustrations of this concept. Select one to view it full size.

Actions Library

Every repeatable command, script or webhook becomes an action with a trigger, tags and a run history.

This illustration shows the Actions page in the Automation section, described as a way to run commands, scripts or webhooks on your agents. The header offers Create Action, an overflow menu and Refresh, and an info banner frames actions as reusable one-click automations. A search field and Type and Trigger dropdowns sit above a bulk bar with Select all visible, a selected count and buttons to execute, duplicate or delete the selection. Cards in a three-column grid show the action name, a type badge for command, script or webhook, a trigger label for manual, on demand, event or scheduled, tags, a run count and the time of the last run. Samples include restarting an API service, running database migrations, tailing an error log, alerting on-call through a chat webhook with its request shown, a production rollback marked as requiring confirmation, and a nightly backup. One card is highlighted as selected.

Vibe Deck One-Click Ops Board

A deck turns chosen actions into large tiles, with separate boards for production, staging, pipelines and incidents.

This illustration shows the Vibe Deck page, described as a digital command board for executing commands or triggering webhooks with one click. The header has a Preview and Edit toggle, Share deck and Public link buttons and a refresh control. Tabs switch between sample decks for production ops, marked as a favorite, staging, an ML pipeline and incident response, with a New deck option at the end. The board is a grid of large gradient tiles. Each shows an icon, an operation name, the underlying action identifier in monospace and a group label such as ops or alerts. Sample tiles include restarting an API, running migrations, rolling back production, clearing a cache, alerting on-call, tailing logs, restarting a worker and scaling up a GPU machine. The migration and rollback tiles carry warning markers, and the rollback tile is tinted red to signal a higher-risk operation.

Shared On-Call Deck on a Phone

A shared deck gives on-call teammates a minimal, safe set of operations they can run from a phone.

This illustration shows a shared deck opened on a phone, without the full application navigation. At the top, a deck icon sits beside the title of a production on-call deck and a subtitle describing safe, pre-approved operations for the on-call rotation. A green Can execute badge tells the viewer they are allowed to run the tiles, and a thin progress bar sits beneath the header. Six tiles fill a two-column grid: restarting a staging API, shown mid-run with a spinner; clearing a cache, marked with a success check; rerunning a health check, with a short run identifier; tailing an error log; alerting on-call; and restarting a worker. The last three carry caution markers, signalling operations that call for more care. A small Powered by VibeControls footer closes the page. The design keeps the shared view to only the operations the deck owner chose.

Topics

  • one-click ops
  • runbook automation
  • ops command board
  • reusable server scripts
  • webhook actions
  • on-call self-service
  • incident response runbook
  • mobile ops deck
  • shared runbook buttons
  • ChatOps alternative

Related concepts

All VibeControls concepts
Get started freeBrowse all concepts

We use cookies for essential site functions and, with your consent, for analytics to improve VibeControls. We don't use advertising or cross-site tracking cookies. See our Cookie Policy.

Preferences