> ## Documentation Index
> Fetch the complete documentation index at: https://flowglad.com/docs/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 a New Automation

Automations belong to one Space. In an external MCP client, describe the repeatable work and the Space where it belongs. The client uses `automations.create` to create the Automation and its initial revision. Use `automations.update` to create a later revision and explicitly select or activate the intended revision. Publishing a referenced Skill never creates, revises, or activates an Automation automatically.

## Configure Triggers

When asking your MCP client to create or revise an Automation, specify when it should run. Available choices include **Schedule**, **File Upload**, and Connection events supported by the Space. For scheduled work, specify the intended cadence, time, and timezone.

## Add Instructions and Connections

Describe what the Automation should do and which connected systems it should use. Before creating it, open the target Space → **Connections** and confirm that every required Connection is available there. If one is missing, configure it from the **organization menu** → **Connectors**, expose it to the Space, and then ask your MCP client to create or revise the Automation.

## Save the Automation

Review the proposed behavior, triggers, inputs, Skill revision references, and Connections before allowing the MCP client to call `automations.create` or `automations.update`. Activation is explicit. Saving or publishing a Skill does not create a Task or mutate an Automation.

## Run and Inspect an Automation

Open the Automation. **Overview** shows its configuration; **Runs** shows past and current runs. Select **Run now** for a manual run when the action is available, review the confirmation, and 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

Use `automations.get` and `automations.list_revisions` to inspect the current definition and history. Use `automations.update` to publish a revised definition and explicitly activate the intended revision. Historical definitions and runs remain readable but are not themselves executable unless selected as the active valid revision.

To delete an Automation, open its **More actions** menu, select **Delete**, and confirm. Deleting it stops all future runs.