# Automations: agents, triggers and schedules

Agent + trigger + schedule = work that gets done while you're busy doing something else.

Here's the recipe for an automation:

> **An agent** (who does the work) + **a trigger** (when something happens) or **a schedule** (at a set time) = an **automation**.

## The three ingredients

| | What it is | Example |
|---|---|---|
| **Agent** | Your module's AI teammate, with its own instructions and the tools you gave it. | *The visitor assistant* |
| **Trigger** | Runs the agent the moment an event happens. | *When a visitor signs in…* |
| **Schedule** | Runs a job or the agent at set times. | *Every weekday at 7 am…* |

## Recipes to steal

- **When** a new request comes in, **the agent** reads it, files it under the right customer and tells the person who handles it.
- **Every morning**, check which certifications run out this month and send each person a reminder.
- **When** a job is marked done, write the summary, attach the photos and email the customer.
- **Every Friday**, total the week's hours and post them to Accounting.

## Who's in charge

- **Turn them on and off** under **System settings › Schedules**. A module's schedules and triggers are set up when you install it, and a Workspace Admin can switch any of them off.
- **The agent only does what its roles allow.** An automation runs as the agent, not as you, and the agent holds only the roles a Workspace Admin gives it under **System settings › Agents**.
- **Every run is recorded**, so you can see what it did and when.

## Building one?

Tell the Module Builder what should happen and when: *"every Monday at 8, remind supervisors about open inspections"*. More detail: [Schedules and triggers](article:6fdf08ad-f3dc-4641-9c6c-457de97ebf29), [Agents and AI models](article:adba700a-3847-4c47-a228-eddb8f0e579f) and [Events and live updates](article:db90fa30-3ef5-42e9-bc1a-9fee6fe3034e).


Source: https://datavisions.ai/docs/creators/automations-agents-triggers-and-schedules
