---
title: "Agents and automation: the system works while you sleep, and it does not spend"
description: "Background modules watch campaigns on a schedule, rules say \"if this happens, do that\", and flows reach outside systems. Money still goes through an approval."
canonical: https://adsbeast.pro/features/en/automation-agents
language: en
section: features
product_route: https://adsbeast.pro/agents
translations:
  - ru: https://adsbeast.pro/features/ru/automation-agents
  - uk: https://adsbeast.pro/features/uk/automation-agents
  - sk: https://adsbeast.pro/features/sk/automation-agents
  - es: https://adsbeast.pro/features/es/automation-agents
  - he: https://adsbeast.pro/features/he/automation-agents
  - ar: https://adsbeast.pro/features/ar/automation-agents
---
# Agents and automation: the system works while you sleep, and it does not spend

Dozens of background modules check campaigns on a schedule: delivery every 2 hours, placements every hour, creative fatigue every 12 hours, bids and structure every few hours. Each of them can propose an action. Not one of them can spend money without a person confirming.

## What runs in the background

- **Delivery**: Checked every 2 hours: campaigns with no delivery, account restrictions
- **Placements**: A guard every 1 hour: risky networks, junk traffic
- **Bids and structure**: Campaigns reviewed every 6 hours, scanned every 4 hours
- **Creatives**: Fatigue every 12 hours
- **Tests**: Running tests reviewed every 12 hours
- **Flows**: The scheduler checks the queue every 60 seconds

How much a module may do alone is set out loud in the Autopilot section: what it may only propose, and what it may apply after confirmation. Nothing may apply without confirmation.

## What the automation does

### Background modules instead of a daily tour of the accounts

Walking through twenty ad accounts by hand every morning is impossible, and a problem spotted on the third day costs three days of budget. The modules run on a schedule and bring only what changed: stalled campaigns, placements switched back on, burnt-out creatives.

- A list of what changed instead of a report about everything
- The schedule of each module in plain sight
- State: when the module last ran

### Rules that say "if this happens, do that"

A rule is written in words: on what condition, for which client and platform, what to do. The action can be a notification, a task for a person, or a change that goes into the approval queue. A rule can be tested against a past period before you switch it on.

- Your own rules by client and platform
- A rule tested against historical data
- A history of when it fired and what came of it

### Flows: the links to outside systems

The flow builder ties system events to outside services: a lead goes to the CRM, a deal goes to a platform as a server event, an alert goes to the team chat. The scheduler checks the queue every 60 seconds.

- Links to the CRM, to server conversions and to webhooks
- A log of every step in a flow
- A step retried after an outside system fails

### You set the trust level

The Autopilot section shows how far the system may act on its own for each type of action. The same rules cover the background modules, the chat and the assistant in Telegram: any tool that moves money leads to the queue.

- Autonomy levels by action type
- One path for modules, chat and Telegram
- A log: which module proposed what and who confirmed it

## How this gets switched on

The background modules work as soon as an account is connected. Rules and flows are added as you need them.

1. **Connect the accounts** - The modules start checking them on their own schedules.
2. **Choose a trust level** - What may be proposed, and what may be applied after confirmation.
3. **Add your own rules** - Condition, client, platform, action; tested against a past period.
4. **Link the outside systems** - Flows into the CRM, server conversions, webhooks and team chats.

## Figures from the code

- 60 sec - between flow scheduler runs
- 1 h - between placement guard runs
- 2 h - between delivery checks
- 4 h - between campaign scans

## What the automation does not do

- It does not spend money without a person confirming - no module, at any trust level.
- It does not bring the same recommendation back after you reject it.
- It does not run tools that are missing from the registry: an unknown tool is closed.
- It does not hide its own failures: a module that did not run shows in its last run time.

## Questions and answers

### Can the automation pause a campaign on its own?

No. It will form an action with the reason, the arithmetic and the expected effect, and send a notification. It is applied only after a person confirms, and then read back from the account.

### How do I test a rule before switching it on?

Run it against a past period: the system shows how many times it would have fired and on which campaigns. That tells a useful rule apart from one that would flood the feed with notifications.

### What do flows do?

They tie system events to outside services: a lead into the CRM, a deal as a server event to a platform, an alert into the team chat, a webhook into your own system. Every step is logged, and a failed one is retried.

### How do I know a module is working?

Each one shows its schedule and its last run time. A missing pulse is an alert, not silence: a module that has gone quiet looks exactly like a module with nothing to say.

## Connect an account and see what the automation notices in the first day

The first 14 days are free on any plan and you do not need a card to start. The trust level is yours to set and yours to change at any moment.

- Start free: https://adsbeast.pro/signup?lang=en
- Pricing: https://adsbeast.pro/pricing?lang=en

## See also

- [Approvals: automation proposes, a person decides, the system applies](https://adsbeast.pro/features/en/approvals): Automation proposes changes to budgets, bids and statuses, a person confirms them, and the system applies them and reads the result back from the account.
- [Assistant: a chat about your ad accounts, not generic advice from the internet](https://adsbeast.pro/features/en/assistant): The assistant answers from your ad account data, works in app and in Telegram, understands voice, and sends money-moving actions to the approval queue.
- [Alerts: with context, on the right channel, and without noise](https://adsbeast.pro/features/en/alerts): Alerts name the platform, account, period and amount: delivered every 5 minutes, escalated after 2 hours, 4 channels, quiet hours.
- [Budget guard: it will not let you blow the cap or buy junk traffic](https://adsbeast.pro/features/en/budget-guard): Monthly caps and pacing across every platform: checked every 2 hours, a placement guard every hour, overspend stopped through an approval.

