Trigger
Read delivery
Every morning at 8, or when a metric crosses a value.
- Spend
- $1,842
- ROAS
- 1.74
- Frequency
- 2.8
Ad automation
Adrails automations read your campaigns on a schedule or when a metric crosses a line, ask an agent what the rows mean, post the result to Slack, Discord or email, and pause what should stop. Agents handle the work that needs judgment around them.
Reviewed Oct 3, 2026
Product view
Read account signals, open the affected campaign and keep each pause or change attached to the figures behind it.
Product workflow
A workflow reads the accounts, keeps the rows that cross your line, tells the team and pauses what should stop.
Trigger
Every morning at 8, or when a metric crosses a value.
Filter
The team decides what counts as an actionable exception.
Send
The rows and an agent's summary are posted where the team works.
Pause
Checked on the platform first, then paused and logged with its figures.
Illustrative workspace data. Values show the product flow and are not customer results.
FAQ
Yes. A workflow with a Pause ads step can pause what crosses your threshold at once, or leave each pause for someone to confirm, within the accounts and the limit per run you choose.
Meta Ads and Google Ads, one platform per step, so a workflow can read both. Google Ads opens once Google finishes verifying Adrails. Connect Meta for now. TikTok Ads is coming soon.
No. An agent step in a workflow only reads. Budget changes are prepared by the Media Buyer agent with their evidence and applied from the workspace.
Every hour. A threshold workflow fires at most once a day for each item that crosses the line.