> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations.md).

# Workflows & Automations

Workflows let DevAlly audit accessibility in places a public site audit can't reach: pages behind a login, multi-step user journeys, content that only appears after setup. There are two ways to create one.

***

### Two paths

{% tabs %}
{% tab title="Recording with Wendy" %}
**The fast path. Recommended for most users.**

Wendy is a Chrome extension that captures your interactions and turns them into a complete workflow. You walk through your app once and Wendy assembles the workflow for you. No selectors to write, no actions to chain.

→ [Get started with Wendy](/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations/recording-with-wendy.md)
{% endtab %}

{% tab title="Workflow builder" %}
**The control path. Used for surgical edits and edge cases.**

The form-based builder lets you author every block, automation, and action by hand. It's the right tool when you need to update a variable, fix one drifted selector, or build a workflow whose interactions Wendy can't capture.

→ [Get started with the builder](/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations/workflow-builder.md)
{% endtab %}
{% endtabs %}

***

### Which one should I use?

| If you want to…                                                  | Use         |
| ---------------------------------------------------------------- | ----------- |
| Create a new workflow from scratch                               | **Wendy**   |
| Edit a workflow against the live page                            | **Wendy**   |
| Update a password or environment URL                             | **Builder** |
| Fix a single selector that drifted                               | **Builder** |
| Add a `Wait for…` action you can't record                        | **Builder** |
| Recover a workflow that's broken without re-recording everything | **Builder** |

{% hint style="success" %}
Both paths edit the same underlying workflow, so you can switch between Wendy and the builder at any time.
{% endhint %}

***

### How they map to each other

Wendy and the builder write to the same model. If you've used the builder before, the Wendy concepts translate cleanly:

| Wendy term           | Builder term               |
| -------------------- | -------------------------- |
| **Setup**            | A "Before each" automation |
| **Each flow**        | A block in the workflow    |
| **Recorded actions** | Steps inside an automation |

Reading more about the builder's underlying model: see [Workflow anatomy](/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations/workflow-builder/explanation/workflow-anatomy.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/workflows-and-automations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.