---
title: Manage Automations
description: Edit, enable, disable, and delete Capawesome Cloud automations from the CLI or the Console, and review their trigger history.
---

# Manage Automations

Once an automation exists, you can manage it from the CLI or from the [Automations](https://console.cloud.capawesome.io/apps/_/automations){:target="_blank"} page in the Console. Each automation lists its trigger, its pattern, and when it **Last triggered**, so you can see at a glance what's active and what's recently run.

## Inspect automations

=== "CLI"

    List every automation with [`apps:automations:list`](../cli/commands.md#appsautomationslist), and inspect a single one with [`apps:automations:get`](../cli/commands.md#appsautomationsget):

    ```bash
    npx @capawesome/cli apps:automations:list

    npx @capawesome/cli apps:automations:get --name nightly
    ```

    Both commands accept `--json`, which makes them easy to pipe into other tools in a pipeline.

=== "Console"

    Open the [Automations](https://console.cloud.capawesome.io/apps/_/automations){:target="_blank"} page of your app to see every automation, its trigger, and its **Last triggered** timestamp.

Names are unique per app and compared case-insensitively, so `Nightly` and `nightly` are the same name.

## Edit an automation

=== "CLI"

    Update a trigger, a pattern, or any [build setting](attach-build-settings.md) with [`apps:automations:update`](../cli/commands.md#appsautomationsupdate):

    ```bash
    npx @capawesome/cli apps:automations:update \
      --automation-id 12345678-1234-1234-1234-123456789012 \
      --trigger-pattern "release/*" \
      --environment staging
    ```

    Updates are addressed by ID — use `apps:automations:get --name nightly --json` to look one up. `--name` sets a new name instead of selecting the automation.

    Pass an empty string to clear a value again — `--environment ""` detaches the environment, and `--commit-message-pattern ""` removes the commit filter.

=== "Console"

    Click **Edit** on the automation and update its trigger, pattern, or [build settings](attach-build-settings.md).

## Delete an automation

=== "CLI"

    Remove an automation with [`apps:automations:delete`](../cli/commands.md#appsautomationsdelete):

    ```bash
    npx @capawesome/cli apps:automations:delete --name nightly
    ```

    Add `--yes` to skip the confirmation prompt in a pipeline.

=== "Console"

    Click **Delete** on the automation and confirm the deletion.

Deleting an automation also removes the webhook it registered on your repository.

## Enable, disable, and history

Two actions are available in the Console only:

- **Enable / Disable** — toggle an automation on or off without deleting it. A disabled automation stays configured but doesn't trigger builds, which is handy during a code freeze or while you debug a pipeline.
- **History** — review the builds an automation has triggered, so you can trace a build back to the push that started it.

To temporarily stop builds for a single push without disabling anything, use a [skip keyword](filter-by-commit-message.md#skip-keywords) in your commit message instead.

## Next steps

- [Filter by commit message](filter-by-commit-message.md) — skip individual pushes without touching the automation.
- [Troubleshooting](troubleshooting.md) — what to check when an automation doesn't run.
- [Automations reference](reference.md) — trigger patterns, skip keywords, and build settings.