> ## 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.

# Build automations

> Learn how Flow automations are built, connected, tested, and published.

## How building works

An automation is a repeatable set of steps that runs work in Flow. Builders describe the work,
review the generated automation, choose the integration access it needs, test it, then publish it for
selected teams or everyone in the organization.

## Example automation

This example creates a Jira Service Management request, then posts a Slack message for the support team.

```mermaid theme={null}
flowchart LR
  request["Requester submits details"] --> validate["Validate required fields"]
  validate --> jira["Create Jira Service Management request"]
  jira --> slack["Notify support in Slack"]
  slack --> result["Return run result"]
```

The automation has:

| Piece | What the builder configures |
| - | - |
| Input | The fields the automation needs, such as requester email, summary, and support channel |
| Steps | The ordered work the automation performs |
| Integration actions | Calls to providers, such as creating a Jira request or posting a Slack message |
| Output | The result Flow records for the run |
| Trigger | What starts the run, such as a user request, schedule, event, API call, MCP tool, or parent automation |

## Build pages

<CardGroup cols={2}>
  <Card title="Build your first automation" icon="bolt" href="/automations/build/first-automation">
    Walk through one support-intake automation from prompt to publish.
  </Card>

  <Card title="Automation anatomy" icon="diagram-project" href="/automations/build/anatomy">
    Understand inputs, steps, integration actions, approvals, triggers, outputs, and versions.
  </Card>

  <Card title="Use integration actions" icon="plug" href="/automations/build/connectors">
    Learn how integration actions use provider connections and required access.
  </Card>

  <Card title="Test and publish" icon="rocket" href="/automations/build/test-and-publish">
    Save drafts, run Validation scenarios, fix issues, and publish a version.
  </Card>
</CardGroup>

## Build an automation

<Steps>
  <Step title="Open Automations." />

  <Step title="Select New automation.">
    Alternatively, open an existing automation from the list.
  </Step>

  <Step title="Describe the work.">
    Tell Flow what the automation should do, what input it needs, and which systems it should call.
  </Step>

  <Step title="Review the visual automation.">
    Use **Code** when you need to inspect the generated automation code.
  </Step>

  <Step title="Set up integration access.">
    Select, connect, or request the provider connections required by the integration actions when
    you test or publish the automation.
  </Step>

  <Step title="Save the draft." />

  <Step title="Run Validation scenarios when configured." />

  <Step title="Publish the automation.">
    Choose the audience: the current team or the organization.
  </Step>
</Steps>

## Related topics

* [Automation integrations](/automations/connectors)
* [Trigger automations](/automations/trigger): worked schedule and event examples
* [Monitor automations](/automations/monitor)


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