Use case
Workflows in Athenous Automate run on schedule (including weekdays), events, manual runs, or polls for spend, ROAS, campaign status, and connector health—connector probes can emit events too. Live steps: notify, Slack, signed webhook, pause or update a flight, notes, delay, and log—while Post and Campaigns stay where work is approved.
New automation rule
When a post is published
The rule
Weekday or cron schedule, ads/social/connector events (including health probe signals), manual run, or polled spend/ROAS, campaign status, and connector health.
AND/OR condition blocks on channel, status, and event context so the workflow waits for the right case.
Live steps today: notify, Slack, webhook with optional HMAC signing, pause or update campaign, notes, delay, log. Email, create-post, and CRM sync remain planned—see the capabilities API.
How it works
A reminder, a handoff, or a notice that already happens the same way each week.
Start a rule or edit a template. The guide walks through trigger, conditions, and action.
Point the event at Post or Campaigns, then add only the actions you want.
Each run shows pending, running, success, or failed in run history and the activity feed; dry-run preview and 7-day analytics help before and after you ship.
Why teams use it
Schedule (weekdays included), event, manual, and poll triggers; live actions include notify, Slack, signed webhook, pause/update campaign, notes, delay, and log. Planned: email, create-post, CRM sync. The full honest list is on Athenous Automate and the /capabilities API.
Lab still writes the draft. The rule picks up after the post or campaign moves.
Questions
After the post or campaign already has an owner. A workflow runs on a weekday or cron schedule, on events (including connector health probe signals), on manual trigger, or on polls when spend, ROAS, status, or connector health crosses your thresholds.
It matches the trigger you choose—schedule, event, spend/ROAS poll, campaign status, or connector health—then runs live steps where wired today: in-app notify, Slack (Incoming Webhook), outbound webhook with optional HMAC signing, pause/update campaign, notes, delay, and log. Email, create-post, and CRM sync remain planned. Conditions keep rules quiet until the right case.
No. A rule does the steps you attach. People still choose what publishes unless that action is one of the steps—and create-post is not live yet.
Automation workflows
Pick a trigger, match the case, and keep the log next to Post and Campaigns.