What are Automations

Automations are how Buron's Agent works when you're not in chat. The Agent reacts when you ask. Automations run on their own.

You can use Automations for anything that runs on a trigger. Common patterns are daily reviews, weekly reports, alerts when something breaks, and snapshots when a build ships.

How they work

Every automation has three things:

• A trigger sets when it runs: a cron schedule, a webhook from another tool, an in-product event, or a manual run.
• A scope sets what it works on: an account, a set of campaigns, a channel, or your whole workspace.
• An output is what it produces: a finding, a report, a notification, or an action you approve.

The Agent does the work in every case. The trigger and scope just decide when and where.

What runs by default

Each domain in Buron comes with a few automations preconfigured. Connecting a Google Ads account turns on:

• The daily optimization review. The Agent scans your accounts every morning and writes findings for whatever it turns up.
• More than 30 health checks that run on a schedule. Their status appears in the Health tab.
• The weekly Google Ads report, which is off by default. Turn it on and the Agent emails a narrative every Monday.

Future domains will have their own defaults. The mechanism is the same.

Where the output goes

Each automation produces something durable. Findings land in your Findings queue. Reports get emailed and saved. Notifications go to your inbox, Slack, or a webhook. Actions queue up for your approval.

You can always open an automation to see what it did on any past run.

Next steps

For concrete examples, check out Example automations. To turn one on or tune one, check out Manage your automations. To build your own, check out Build your own automation.