What counts
An automation action counts when it really changes something, for example it sets a value, creates an item or sends a notification. These are free:- Conditions. They decide whether an automation runs, they are not actions.
- Actions that failed, or that Work did not allow.
- Actions waiting for an approval.
- Actions that did nothing, for example when the Agent it needs is switched off.
See your usage
Open Usage in Work (/work/usage). It shows your plan, how many actions you used this month, the percent, and the day the count starts again. The count restarts on the first day of each month, in UTC.
The automation screens show a banner when you are close to the limit or over it. The banner has a button that opens Usage.
Warnings and the limit
- At 80% the workspace owners get one notification in the inbox, and the automation screens show a banner.
- At 100% automations pause. A paused automation does not run its actions. Its run history shows a skipped run with the reason, and the owners get one notification.
- When the month restarts, or the plan changes, automations run again. You do not need to turn anything back on.
Read usage from the API
GET /v1/usage is open to every member of the workspace. It returns the plan, the start and the reset time of the period, the warning level (80), whether automations are paused, and one entry for each meter with used, limit, percent and state (ok, warning or exceeded). A meter with limit: null has no limit.
You cannot change a plan from the API or the app. Your Worksong operator moves a workspace to another plan.
Source: worksong-ai/worksong:services/work/docs/plans-and-usage.md@f8b76d6, worksong-ai/worksong:services/work/src/Boardy.Workers/UsageMeter.cs@f8b76d6, worksong-ai/worksong:services/work/src/Boardy.Authority/Application/Usage/Plans.cs@f8b76d6. Docs version: Worksong 2.0 with Work 1.2.