> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/automate/build-a-workflow/workflow-copilot.md).

# Workflow Copilot

{% hint style="warning" %}
Workflow Copilot is temporarily unavailable while it is being improved. The Copilot panel, workflow generation, Auto Fix and Copilot-guided template setup are currently disabled. Workflows can still be built and edited manually.
{% endhint %}

This page describes the Copilot behaviour for reference while the feature is unavailable.

### Capabilities

When enabled, Workflow Copilot can:

* create a Workflow from a natural-language description;
* edit existing actions and canvas structure;
* explain Workflow configuration;
* suggest or apply fixes;
* connect supported apps during setup;
* show the proposed canvas changes for review.

### Create a Workflow

1. Open a new Workflow.
2. Describe the trigger, inputs, business outcome and important constraints.
3. Submit the request.
4. Review the generated actions and connections.
5. Configure missing Connections or business-specific values.
6. Run representative cases before publishing.

### Edit an existing Workflow

Describe the required change and name the relevant action or part of the Workflow when useful.

Examples:

* “Add a Request Decision before the ERP write.”
* “Use the customer number from the trigger in this lookup.”
* “Change this branch so missing price data goes to review.”

The Copilot can use selected canvas context for a more targeted edit.

### Change review

Copilot changes are presented as **Added**, **Edited** or **Deleted**.

Review the actual change before running or publishing it. Individual changes can be inspected and, where supported, undone separately.

### Connections

When a change requires an external provider:

* connect the required account if none exists;
* select the intended existing Connection when several are available.

The Connection still defines system authority. Copilot configuration does not create authority beyond the selected Connection.

### Auto Run and Auto Fill

When available, Copilot permissions can allow it to:

* run Workflows without a separate confirmation;
* fill required test or run inputs automatically.

Keep these disabled when the Workflow can create consequential external side effects that you still want to review manually.

### Fix and rerun

Copilot can inspect some execution failures, propose changes and rerun the Workflow.

A successful rerun does not prove the business post-condition is correct. Verify external changes where the process requires it.

### Guidelines

* Describe the business outcome, not only the desired canvas shape.
* Name systems and authoritative inputs.
* State where a human decision is required.
* Review every material change.
* Test side effects with safe data.
* Prefer direct deterministic configuration when the logic is already known.


---

# 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.lleverage.ai/build-and-improve/automate/build-a-workflow/workflow-copilot.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.