> ## Documentation Index
> Fetch the complete documentation index at: https://help.casaconect.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Workflows are multi-step procedures the agent runs the same way every time. Learn what they are, how to start one and how they differ from an ordinary conversation.

In an ordinary conversation the agent decides, message by message, what to do next. That flexibility is what you want for most work. For a few high-stakes jobs you want the opposite: a fixed procedure, with the same steps in the same order, checks built in, and a clear record of what happened. That is a **workflow**.

Casa Conect has two workflows today.

<CardGroup cols={2}>
  <Card title="Populate" icon="file-input" href="/workflows/populate">
    Fill a template from the project's documents. Every value is traced to its source and verified before it lands.
  </Card>

  <Card title="Anonymize" icon="eye-off" href="/workflows/anonymize">
    Turn a drafted document into a reusable template. Sensitive values are replaced with placeholders as tracked changes you review.
  </Card>
</CardGroup>

## Conversation or workflow?

|              | Conversation                                             | Workflow                                                             |
| :----------- | :------------------------------------------------------- | :------------------------------------------------------------------- |
| **Steps**    | Chosen by the agent as it goes                           | Fixed and always in the same order                                   |
| **Model**    | The one you pick in the [model picker](/models/overview) | Fixed per step by Casa Conect, matched to the difficulty of the step |
| **Progress** | Messages and tool activity                               | A workflow card with named stages                                    |
| **Checks**   | Your review of the result                                | Built-in verification, then your review                              |
| **Best for** | Open-ended work                                          | Repeatable work where consistency matters                            |

## Start a workflow

<Steps>
  <Step title="Open the Workflows menu in the composer">
    In a project or matter conversation, open **Workflows** in the composer and choose **Populate** or **Anonymize**. The workflow is attached to your next message. Choose **Remove workflow** to detach it.
  </Step>

  <Step title="Say what you want">
    A default message is filled in for you, such as *"Populate a template from this project's documents."* Replace it with specifics: which template, which documents matter, anything the agent should know.
  </Step>

  <Step title="Follow the workflow card">
    A card labelled **Workflow** appears in the conversation and shows each stage as it runs. It ends as **Completed**, **Failed** or **Stopped**, with a button to open the resulting document.
  </Step>
</Steps>

You can also ask in plain words, for instance *"fill in the purchase deed template from this project's files"*, and the agent starts the right workflow. On a matter, the **Populate** quick action does the same.

## What happens when a workflow finishes

A completed workflow is recorded on the timeline of the conversation and of any linked matter as **Workflow completed**, with the person or agent that ran it. The output is an ordinary document in the project's vault: open it, review it, and carry on working in it with the agent or by hand.

## Workflows and cost

Workflow usage appears on its own lines under **Settings → Access & billing → Usage**: *Filling in templates* and *Anonymizing templates*. Because each step runs on a model matched to its difficulty, a workflow typically costs less than asking a frontier model to do the whole job in conversation. See [AI credits](/admin/ai-credits).

<Note>
  Casa Conect does not currently offer a builder for custom workflows, triggers or schedules. For repeatable work of your own, write a [skill](/agent/skills): it records your method, and the agent follows it whenever the skill is used.
</Note>