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

# Automations

> Turn repeatable instructions into reviewable operational work

Automations turn repeatable instructions into operational work. They use workspace context, connected sources, pages, and skills to prepare analysis or next steps on a schedule or in response to an event.

An Automation is owned by one Space. Its Instructions may invoke a reusable Skill with `/<slug>`. A Skill does not schedule itself, and an Automation run does not automatically create an assigned Task.

## An automation can

* Read from connected systems and source files
* Combine source data with workspace context
* Draft analysis, updates, or proposed actions
* Record the run and its supporting evidence

## Reviewable actions

When an automation would affect another system or produce a client-facing output, it should produce a proposal or reviewable result first. A reviewer can inspect the rationale, evidence, and intended action before approving it.

## Runs

Each run should make its progress and outcome understandable. Runs provide the context needed to distinguish a successful action, a failed attempt, a pending review, and a result that needs follow-up.

## Create an Automation in a Space

Automations belong to one Space. Open the intended **Space** → **Automations** → **New Automation**. Chat can explain this path and inspect existing Automations, but it does not create or save a new Automation for the user.

## Configure Triggers

Under **Triggers**, choose **Add Trigger**. Real choices include **Schedule**, **File Upload**, and Connection event triggers that are shown for the Space. A Schedule supports the **Daily**, **Weekdays**, **Weekly**, and **Monthly** presets; set the intended time and timezone.

## Add Instructions and Connections

Enter what the Automation should do in **Instructions**. Confirm the required provider appears under **Available Connections in \<Space>**. If the editor says **No active connections**, use **More prompt options** → **Add Connection**, finish the Space-scoped connection flow, and then return to the editor.

## Save the Automation

Review the trigger, Instructions, and available Connections, then select **Save**. Saving an Automation does not create a Task, and a chat starter does not save an Automation automatically.

## Run and Inspect an Automation

Open the Automation. **Overview** shows its configuration; **Runs** shows past and current runs. Select **Run** for a manual run when the action is available, then open the run to inspect its activity and result.

Use the Space-level **Automations** → **Runs** view to review runs across that Space.

## Edit or Delete an Automation

Open the Automation and edit its Instructions, Triggers, or available Connections, then select **Save**. Use **Delete** from the Automation's actions to stop all future runs when permitted; review the confirmation before deleting.

## Start From an Automation Template

In the Space's **Automations** view, choose a template when the templates section is available and select **Add**. The template creates a draft in that Space. Review its Instructions, Triggers, and Connections, then select **Save**; adding the template does not run it.

## Programs When Available

Some organizations show **Programs** under a Space's Automations. A Program is a structured, input-driven workflow. Open **Programs**, choose or create one, supply the requested inputs, and select **Run Program**. If the **Programs** view is absent, use the standard Automation flow.