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

# Automations

> Run Felan automatically from schedules and connected-system events.

Automations start Felan sessions without a teammate manually entering the same request each time. Every automation has a name, plain-language instructions, and one or more triggers.

## Create an automation

<Steps>
  <Step title="Open Automations">
    Select **Automations** in the team sidebar, then **New automation**.
  </Step>

  <Step title="Name the workflow">
    Use a name that makes its purpose recognizable in the automation list and session history.
  </Step>

  <Step title="Add triggers">
    Add at least one trigger. A trigger can be a schedule with a cron expression and timezone, or an event type available from the team's integration configuration. One automation can contain multiple triggers.
  </Step>

  <Step title="Write the instructions">
    Describe the outcome Felan should produce when any trigger fires. These plain-language instructions become the agent task prompt.
  </Step>

  <Step title="Create the automation">
    Save it as active when at least one trigger is enabled. Triggered runs appear as sessions with automation origin information.
  </Step>
</Steps>

## Manage automations

The list shows each automation’s state, trigger summary, trigger details, and instructions. From the list you can:

* Pause or activate the automation
* Edit its name, instructions, or triggers
* Delete the automation and all triggers it contains

## Write effective instructions

Include the target, evidence to inspect, expected output, and important boundaries.

```text theme={null}
Review the deployment event and the affected repository changes. Run the
smallest relevant verification, summarize risks, and identify any blocker
that needs a teammate.
```

<Info>
  An event trigger requires the corresponding integration and event type to be available to the team. Configure external services under [Integrations](/docs/integrations/overview).
</Info>