> For the complete documentation index, see [llms.txt](https://docs.mercuri.cx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mercuri.cx/features/flows/managing-existing-workflows.md).

# Managing Existing Workflows

Once a workflow is created, you can view and manage it from the **Workflows dashboard**.

<figure><img src="/files/JiLjnnrN2n83ryMVxNVq" alt=""><figcaption></figcaption></figure>

Each workflow card shows:

* **Workflow name**
* **Trigger event**
* **Channels used** (for example, WhatsApp or SMS)
* **Creation date**
* **Workflow status (On / Off)**

From this page, you can also perform the following actions:&#x20;

***

### <mark style="color:$primary;">1. Viewing Workflow Logs</mark>

Logs help you track how the workflow is performing.

To view logs:

1. Click the **Logs icon** on the workflow card.
2. The logs will show details of workflow executions, such as:
   * When the workflow was triggered
   * Which messages were sent
   * Whether the action was successful or failed

This helps you monitor and troubleshoot your automations.

***

### <mark style="color:$primary;">2. Editing a Workflow</mark>

If you want to modify an existing workflow:

1. Click the **Edit icon** on the workflow card.
2. The workflow builder will open.
3. You can update:
   * Triggers
   * Logic conditions
   * Actions
   * Message templates
4. Click **Save Changes** after making updates.

***

### <mark style="color:$primary;">3. Deleting a Workflow</mark>

If a workflow is no longer needed, you can delete it.

To delete a workflow:

1. Click the **Delete icon** on the workflow card.
2. Confirm the deletion.

Once deleted, the workflow will no longer run.

***

### <mark style="color:$primary;">4. Turning a Workflow On or Off</mark>

You can also quickly enable or disable a workflow using the **toggle switch** on the workflow card.

* **On** → The workflow runs automatically when triggered.
* **Off** → The workflow is paused and will not execute.

This allows you to temporarily stop an automation without deleting it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mercuri.cx/features/flows/managing-existing-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.