# Automations

Automations run a workspace Agent on a schedule, from a webhook, or manually. Open **Agents → Automations** to create one, search existing tasks, or filter **All**, **Active**, and **Paused**. Management requires the workspace’s **Manage integrations** permission.

## Configure a task

1. Choose **New automation**, or start with **Knowledge base drift**, **Nudge overdue learners**, or **Sales calls to courses**.
2. Give it a name and choose the Agent it runs as. The Agent owns the model, connector, access policy, and guardrails; the automation does not add permissions.
3. Write the task in **Instructions**. Use `@` to reference a Knowledge Base document or folder that the Agent can access. Referenced material is read fresh for each run.
4. Select **Scheduled**, **Webhook**, or **Manual**. Scheduled tasks support hourly, daily, weekly, or custom schedules, an explicit time zone, and a preview of upcoming runs.
5. Save, then use **Test** or **Run now** to inspect the result. Switch **Active** off to pause normal triggering.

A webhook trigger receives work from an external system. Saving it provides a trigger URL and a signing secret; the secret is shown only when created or rotated. This is different from outbound event webhooks under **Developers**, which notify your systems about events in Honen.

## Results and run history

The overview shows an Agent, trigger type, enabled state, and available last/next run information. Open an automation’s **Runs** to inspect status, summary, errors, and the conversation. Repeated failures can pause a task and show why. Manual tests and normal runs are distinguishable.

The **Knowledge base drift** starter reports changed documents and affected courses without editing them. The **Nudge overdue learners** starter is a messaging task, so its configured Agent needs the relevant permissions. Read and customize starter instructions for the task you intend to run.

## Proposals for review

To maintain courses, give an Agent access to the relevant sources and permission to propose changes on selected courses. Tell it what to check and where to submit the proposal. Schedule the task, then review the proposed version through course-editor review or a catalog’s publishing review queue. Scheduling a task does not bypass human approval.

See [Agents](https://honen.com/llms/agents.md) for channels, models, permissions, and Agent Runs, and [Publishing and Review](https://honen.com/llms/publishing-and-review.md) for catalog approval workflows.
