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

# Build your first workflow

> Turn a useful chat answer into a versioned workflow, run it, and put it on a schedule.

export const DocMeta = ({type, applies, owner}) => {
  const LABELS = {
    tutorial: "Tutorial",
    "how-to": "How-to guide",
    explanation: "Explanation",
    reference: "Reference"
  };
  return <div className="e6-meta">
      <span className={type === "how-to" || type === "tutorial" ? "e6-eyebrow" : "e6-eyebrow e6-eyebrow--quiet"}>{LABELS[type] || type}</span>
      {applies ? <span>Applies to: {applies}</span> : null}
      {owner ? <span>Owner: {owner}</span> : null}
    </div>;
};

<DocMeta type="tutorial" applies="All deployments" />

A workflow connects an answer worth repeating to an operation the business can trust. In this tutorial you describe a workflow in chat, check it, run it, and schedule it. This moves you from **Ask** to **Automate**.

**Before you start:** you have a ready project. See [Ask your first question](/agentflow/get-started/first-answer).

<Steps>
  <Step title="Describe the workflow in chat">
    Open a project chat and describe what you want, including the business rules. For example:

    > Create a workflow that runs every Monday morning, pulls last week's defect rates per line, ranks the worst three, and emails the plant managers.
  </Step>

  <Step title="Answer the clarifying questions">
    AgentFlow asks about anything ambiguous: steps, inputs, tool choice, branching, model needs and approvals. Answer each one.
  </Step>

  <Step title="Review the plan and confirm">
    Read the proposed plan, then explicitly confirm that AgentFlow should create the workflow. Nothing is created before you confirm.

    AgentFlow then checks every deterministic step, validates the whole spec with the runtime compiler, repairs errors, and saves the workflow only once it compiles.
  </Step>

  <Step title="Review the saved workflow">
    Open **Workflows** and select it. Check its inputs, graph, steps, tools, assertions and outputs. See [Edit and version a workflow](/agentflow/automate/edit-and-version).
  </Step>

  <Step title="Run it">
    Select **Run**, fill in the inputs, and start the run. Follow the step timeline, then review the final artifacts. See [Run a workflow](/agentflow/automate/run-a-workflow).
  </Step>

  <Step title="Schedule it">
    Create a cron trigger for the workflow, for example every Monday at 09:00 UTC. See [Schedule a workflow](/agentflow/automate/schedule).
  </Step>
</Steps>

## Next

<Columns cols={3}>
  <Card title="Add an approval" icon="badge-check" href="/agentflow/automate/actions-and-approvals">Route side effects through email or Slack approval.</Card>
  <Card title="Bring your own tools" icon="wrench" href="/agentflow/extend/custom-tools">Call your ERP, MES or KPI logic from steps.</Card>
  <Card title="How it works" icon="lightbulb" href="/agentflow/concepts/how-it-works">Why a compiled workflow beats one big agent.</Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.