> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/administration/9.-triggers.md).

# Automations and Execution Logs

Automations let repeatable work run on a schedule or recurring cadence. They help teams keep routine monitoring, reporting, review, and follow-up work moving without manual prompting every time.

**Location:** Administration -> Automations

Automation management is an Administration surface. Members usually see the results of automated work as tasks, notifications, files, or project activity.

Execution history is reviewed in **Execution Logs** at `/runs`.

## Automations vs. Triggers

The user-facing product section is **Automations**. A trigger is the scheduled instruction or event that starts automated work.

You may still see older technical references to triggers in URLs or internal names. In the product, use Automations for the section and triggers for the underlying scheduling concept.

## How Automations Work

An automation defines:

* What work should run
* Which agent, task, or workflow should perform it
* When it should run
* What inputs or context it should use
* How results should be reviewed
* What notifications or follow-up behavior should occur

Automations should not bypass required review or approval steps. They initiate work according to the configured schedule and permissions.

The Automations page shows workspace-level automation health, including active automation count, run count, success rate, and agents covered. Each automation can show its schedule pattern, enabled state, linked agent, run count, success rate, and last update.

## Common Uses

Use automations for:

* Daily monitoring
* Weekly summaries
* Recurring research
* Scheduled reporting
* Follow-up reminders
* Periodic task creation
* Operational checks

Use manual tasks or agent chat for work that needs fresh human judgment before it starts.

## Execution Logs

Execution Logs show run history for automation and execution activity. Use them to review:

* Whether an automation ran
* When it ran
* Whether it succeeded or failed
* Which trigger and agent were involved
* How long the run took
* The run identifier
* Error states and follow-up needs

Execution Logs are especially important when an automation depends on external integrations, because connection or provider failures may only appear at run time.

The log list is backed by the trigger execution feed. It can be filtered by automation, agent, status, trigger, and time window where those filters are available. Current run statuses include **Pending**, **Success**, **Failed**, and **Timeout**.

The list shows columns such as **Trigger**, **Agent**, **Status**, **Started**, and **Action**. Use **Open** to inspect a specific run.

## Run Detail

Run detail gives the full execution trail for one automation run. Depending on the run, it can include:

* Trigger name and status
* Linked agent
* Start and completion timestamps
* Total duration
* Linked conversation
* Files or attachments captured with the run
* Trigger context payload, such as scheduled time, actual time, timezone, and cron expression
* The conversation transcript tied to the execution

Use run detail when you need to understand why an automation produced a result, missed context, hit setup requirements, or depended on a particular schedule payload.

Run detail can load the linked conversation, messages, and files attached to that conversation when the run has an associated chat.

## Managing Automations

Depending on the workflow, automation setup may happen from an agent, task, project, Task Type schedule, or automation-specific surface. When configuring an automation:

1. Confirm the workflow is ready to run repeatedly.
2. Confirm required integrations and connections are active.
3. Set the schedule and inputs.
4. Review notification and output expectations.
5. Check the first run in Execution Logs.

Opening an automation can show actions such as **Enabled**, **Edit schedule**, **Run now**, and **Delete**. It can also link back to the agent builder, filtered runs, recent runs, and notification channels.

## Pausing Or Disabling

Pause or disable an automation when the workflow should stop running but the configuration should be preserved. Delete only when the automation is no longer needed and its history or setup is not required for future work.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/administration/9.-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.