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

# Automations

> Create, run, and monitor Flow automations.

## What an automation does

An automation runs repeatable operational work. Describe what you need in plain language, and Flow
turns it into an automation you can review. As you refine the work, Flow updates the draft, adds
the inputs and integration actions the run needs, and flags issues to fix.

You stay in control throughout: review the draft, run Validation scenarios, try simulated or live
actions, and decide when to publish. Once published, an automation can start from a Flow request,
the API, MCP, a schedule, an event, or another automation.

Before building, define the outcome, participants, inputs, approvals, and systems involved. Flow
asks for missing process details instead of assuming what an unclear request means.

<Frame>
  <img className="block dark:hidden" src="https://mintcdn.com/encore-add3fa8c/BWNp6q1kPC_mNwd_/images/automations/you-and-builder-light.svg?fit=max&auto=format&n=BWNp6q1kPC_mNwd_&q=85&s=9cc2aa5639be915d3b0ea0aa4fd03055" alt="You describe the work in plain language and review, test, and publish. Flow drafts the automation, adds inputs and integration actions, and flags issues. You stay in control from first draft to publish." width="680" height="280" data-path="images/automations/you-and-builder-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/encore-add3fa8c/BWNp6q1kPC_mNwd_/images/automations/you-and-builder-dark.svg?fit=max&auto=format&n=BWNp6q1kPC_mNwd_&q=85&s=62c0bd9f09cddb8a1932d67dc3eae321" alt="You describe the work in plain language and review, test, and publish. Flow drafts the automation, adds inputs and integration actions, and flags issues. You stay in control from first draft to publish." width="680" height="280" data-path="images/automations/you-and-builder-dark.svg" />
</Frame>

## Core concepts

| Term | What it means |
| - | - |
| Automation | A repeatable set of steps that Flow can run. |
| Flow | The assistant that drafts and updates automations from natural language. |
| Integration | A catalog of provider actions that automations can call using an authorized provider account. |
| Action | A single operation defined by an integration, such as sending a message or updating a provider record. |
| Entry point | What starts a published automation, such as a Flow request, schedule, event, API call, or another automation. |
| Validation scenario | A saved check with fixed input, mocked actions, and an expected result that travels with each revision. |

## How automations move through Flow

1. **Describe the work.** Tell Flow what work should happen and what information the run needs.
2. **Review the draft automation.** Review the steps, inputs, and integration actions. Open the code
   only when you need implementation detail.
3. **Select integration access.** Choose or request the provider connections needed for live tests
   and published runs.
4. **Review Validation scenarios and test the draft.** Run Validation scenarios for the saved
   revision, then use simulated actions and live connections when you intend to call providers.
5. **Publish a version.** Publish the automation for a team or the organization.
6. **Trigger published runs.** Start the published version from a configured request, schedule,
   event, API, MCP, or parent automation.
7. **Monitor run history.** Check each run's status, version, provider calls, retries, and errors.

## Choose where to start

<Card title="First automation" icon="sparkles" href="/automations/build/first-automation">
  Create a simple automation with Flow and test it in Simulated mode.
</Card>

<CardGroup cols={2}>
  <Card title="Build automations" icon="bolt" href="/automations/build/overview">
    Review automation anatomy, integration actions, Validation scenarios, and publishing.
  </Card>

  <Card title="Set up integrations" icon="plug" href="/automations/connectors">
    Authorize provider accounts and allowed actions for automation runs.
  </Card>

  <Card title="Trigger automations" icon="play" href="/automations/trigger">
    Start published automations from any configured entry point.
  </Card>

  <Card title="Monitor automations" icon="chart-line" href="/automations/monitor">
    Inspect run status, versions, provider calls, retries, and errors.
  </Card>
</CardGroup>

## Frequently asked questions

<Accordion title="Can Flow help build an employee onboarding automation?">
  Yes. Define the onboarding steps, required information, approvals, and connected systems. Flow can
  draft the automation for you to review, test, and publish. It is not active until you publish it.
</Accordion>

<Accordion title="Can I create automation code myself?">
  Yes. You can write automation code yourself, then use Flow to review, refine, or extend it before
  publishing.
</Accordion>

<Accordion title="Can I test an automation before it calls real providers?">
  Yes. Use Validation scenarios for saved revision checks, start interactive runs in **Simulated**
  mode, then switch to **Live** when you intend to call providers.
</Accordion>

<Accordion title="Where can a published automation start from?">
  From any configured entry point, including a Flow request, schedule, event, API, MCP, webhook, or
  another automation.
</Accordion>

<Accordion title="How does an automation connect to an external provider?">
  Automations call providers through integration actions. Setting up integrations and authorizing provider accounts is covered in [Set up automation integrations](/automations/connectors).
</Accordion>

<Accordion title="Why do providers have separate integration connections?">
  The same provider can support different Flow surfaces. A Google Drive connection for knowledge search does not need the same permissions as a Google Drive integration used by an automation.

  Automation integrations are action-scoped. Administrators choose which team can use a connection,
  which actions are allowed, and which provider permissions Flow requests. This keeps automation
  access separate from knowledge, asset, and identity integrations.
</Accordion>


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