monday.com · Workflow Clinic
monday.com Automation Actions Explained: Limits by Plan and How to Use Them Well
Your plan sets how many automation actions you get each month, from 250 on Standard to 250,000 on Enterprise, and a few common automations use them much faster than you'd expect.
Worktables 14 min read

A monday.com automation action is one thing an automation does when it runs, such as sending a notification or creating an item. According to monday.com, Standard plans include 250 automation actions a month, Pro 25,000 and Enterprise 250,000, with a separate allowance for integrations. Some automations use several actions every time they run.
This guide is for monday.com admins, operations leads and anyone who has seen the "you've used 80% of your monthly actions" banner and wondered where the actions went. It is also for teams choosing a plan, since the action allowance is one of the most common reasons we see accounts outgrow Standard.
We explain what counts as an action, the limits by plan and what happens when you run out, which automations quietly use more than one action, how to estimate your monthly usage, and how to cut usage without breaking the workflows people rely on.
What an action is and how monday.com counts it
Every monday.com automation has three parts. monday.com's automation guide describes them as a trigger (the event that starts it), an optional condition (a requirement the trigger must meet) and one or more actions (what happens as a result). Only the actions are counted against your allowance.
monday.com's own example is simple. In "when a status changes to something, delete the item," the trigger is the status change and the action is deleting the item. If the automation runs three times, three items are deleted and three actions are used. Triggers and conditions that do not lead to an action cost nothing.
That is the rule for most board automations: one run, one action. The exceptions are covered in the next sections, and they are where most surprises come from.
Two separate allowances: automations and integrations
Every account has two monthly limits, not one. According to monday.com's documentation, one covers automations and the other covers integrations, such as syncing with Gmail, Outlook or other external tools. Each plan gets the same number of actions in both buckets.
The split has a few edge cases worth knowing:
Custom templates that mix both. When a custom automation includes both automation and integration blocks, monday.com counts all of its actions against the automation limit.
Workflows from the AI workflow builder. monday.com's article on the workflow builder says active workflows consume automation actions, never integration actions, even when a block talks to a third-party tool. Condition steps inside a workflow also count.
Marketplace apps. Actions consumed in relation to monday.com apps count against the automation limit, and some apps create automations that run in the background.
In practice, this means the automation allowance is the one most teams run out of first. The integration allowance is easier to predict because it mostly tracks how often external tools sync.
What does not use actions
Only runs use actions. Building, editing or switching off an automation is free, and so are Formula columns, Mirror columns, dashboards and manual work. A board automation whose condition is not met performs no action, so a well-chosen condition is often the cheapest way to stop runs that nobody needs.
Action limits by plan
Automations and integrations are only available from the Standard plan up. monday.com's pricing article for automations and integrations lists these monthly allowances, checked in November 2026:
| Plan | Automation actions per month | Integration actions per month | Can buy more actions? |
|---|---|---|---|
| Free and Basic | None | None | No |
| Standard | 250 | 250 | No |
| Pro | 25,000 | 25,000 | No |
| Enterprise | 250,000 | 250,000 | Yes, through monday.com |
Workflows built in the AI workflow builder also have a separate cap on how many can be active at once, and that cap varies by plan and product. Plans, limits and prices change, so check the current numbers on monday.com before you make a buying decision.
The jump between plans is large. Pro has 100 times the automation actions of Standard, and Enterprise has 10 times Pro. That gap is why the question is rarely "how many more actions do we need?" and usually "which plan matches the way we work?"
What Standard is really for
monday.com is candid about this. Its pricing article recommends Standard for occasional, simple automations or a single workflow, and notes that 250 actions are typically used up within days by accounts that notify several people or map several columns per automation. It also says Standard is not well suited to automations that use more than one action.
We agree, and we would add one point from implementation work. Standard is fine for a team testing automations on one board. It is rarely enough for a live operational process, such as order handling or production tracking, where every item triggers several handoffs.
When the allowance resets
The cycle depends on how you pay. According to monday.com, monthly billing resets on the same day of the month you activated the account, while yearly billing resets on the second day of every month. Knowing your reset date matters when you are close to the limit, because waiting a few days can be cheaper than an emergency change.
What happens when you run out
monday.com describes the behavior in its actions article, and it is more nuanced than a hard stop:
Usage over the limit carries forward. The extra actions are deducted from the next month's allowance. monday.com's example: a Pro account that uses 28,000 automation actions in April starts May with 22,000.
Warnings come first. Admins and billing contacts receive emails as usage climbs, and a banner appears on boards that cannot be dismissed until the cycle resets or the plan changes.
On Standard, enforcement has a grace period. The first time a Standard account reaches its quota, monday.com sends a notice and rolls the overage forward. On later occasions, reaching 100% starts a 72-hour grace period before automation runs are paused.
Editing is blocked at zero. When all of the current month's actions are used, the account cannot edit or add automations, integrations or workflow blocks.
You cannot pay to reactivate. Only Enterprise accounts can buy extra actions. Everyone else either upgrades or waits for the reset.
The carry-forward rule is the one that hurts. A heavy month does not just end early; it can eat into the next month, or even start the following month with no actions at all.
Automations that use more than one action
Most runaway usage comes from a small group of automation patterns that use several actions per run. monday.com's actions article lists them, and they are worth knowing by heart before you design anything.
| Pattern | How monday.com counts it | Example run |
|---|---|---|
| Creating an item with mapped columns | One action to create the item, plus one for each mapped Status, Tag, People or Dropdown column and the Updates section | Create an item and map two Status columns: 3 actions |
| Notifying board subscribers or a team | One action per person notified | Notify six subscribers: 6 actions |
| Sending email to several addresses | One action per email sent, for example when a Text column holds more than one address | Email two addresses: 2 actions |
| Recurring "every time period" templates | One action each time it runs, plus mapped columns as above | Create a daily item: about 30 actions a month, before mapping |
| Custom templates with several steps | Each action step counts | Change status, assign and notify: 3 actions |
| AI workflow builder | Each action block counts, condition steps count too, notifications count per person and emails per email | A workflow with a condition and two actions: at least 3 actions |
The pattern behind all of these is the same. The cost of an automation is not the number of automations on the board. It is the number of runs multiplied by the actions in each run, and the recipient count is part of that.
The notification trap
Notifications are the most common surprise. "Notify board subscribers when status changes" looks like one automation. On a board with eight subscribers, it is eight actions every time any status changes. If 300 items on that board each change status five times in a month, that one automation can use 300 × 5 × 8 = 12,000 actions.
That is almost half of a Pro account's monthly automation allowance, spent on notifications that many subscribers probably mute.
The item-creation trap
The second common surprise is cross-board item creation, which is popular for handoffs. "When status changes to Approved, create an item on the Delivery board" sounds like one action. Map the Status, People and two Dropdown columns, and every run uses five actions: one to create the item and one for each mapped column.
Neither pattern is wrong. Both are often exactly the right design. The point is to count them on purpose, before go-live, instead of finding out from the banner.
How to estimate your monthly usage
You can estimate usage before go-live with a simple worksheet. For each automation, write down three numbers: how many times it will run in a month, how many actions each run uses, and which allowance it counts against. Monthly actions for that automation are runs multiplied by actions per run. Add them up per allowance and compare the total with your plan.
The hard part is the run count, and the best source is your own data. Count last month's orders, tickets or work orders, and how many times each one changed status. If you are migrating from spreadsheets, a rough count from the old file is good enough.
A worked example (hypothetical)
The following example is hypothetical. The team, the volumes and the automations are illustrative assumptions, not a Worktables client.
Imagine an operations team that handles 200 customer orders a month on one board. About 40 of those orders get stuck at some point. The team has six board subscribers and uses these automations:
| Automation | Runs per month | Actions per run | Monthly actions | Allowance |
|---|---|---|---|---|
| When status is Approved, create an item on the Delivery board, mapping Status, People and one Dropdown column | 200 | 4 | 800 | Automations |
| When an owner is assigned, notify that person | 200 | 1 | 200 | Automations |
| When status is Stuck, notify board subscribers | 40 | 6 | 240 | Automations |
| When the due date arrives, notify the owner | 200 | 1 | 200 | Automations |
| Every day, create a daily check item with one mapped Status | 30 | 2 | 60 | Automations |
| When status is Shipped, send a Gmail confirmation to the customer | 200 | 1 | 200 | Integrations |
The automation total is 800 + 200 + 240 + 200 + 60 = 1,500 actions a month. The integration total is 200.
On Standard, 1,500 automation actions is six times the 250 allowance, so the account would hit the limit within the first week. On Pro, 1,500 is 6% of 25,000, which leaves plenty of room for growth and for a second board. The integration usage of 200 would fit within Standard's 250 on its own, but with no margin for a busier month.
What the example teaches
Two lines account for most of the usage: the cross-board item creation (800) and the subscriber notification (240). Neither is the automation people would guess. That is typical. The automations that look simple and fire on every item usually matter more than the clever ones that fire rarely.
It also shows why planning per allowance matters. A team that only looks at total actions might pick a plan for the wrong bucket. The integrations allowance and the automations allowance are measured and exhausted separately.
How to use fewer actions without breaking the workflow
Cutting actions should never mean cutting the handoffs a process depends on. The goal is to remove waste: notifications nobody reads, data copied instead of linked, and automations that fire when nothing needs to happen. These are the changes we make most often when we review an account.
Notify the person who acts, not the audience
Replace "notify board subscribers" with "notify the person in the Owner column" wherever one person is expected to act. On the eight-subscriber board from earlier, that turns eight actions per run into one. If several people genuinely need to know, a dashboard or a filtered view often serves them better than a notification.
Link and mirror instead of copying
Cross-board item creation copies data, and every mapped Status, People, Tag or Dropdown column costs an extra action. If the receiving team only needs to see the information, link the items with a Connect Boards column and show the details with a Mirror column. Mirror columns update on their own and do not run automations, so they cost nothing in actions.
When you do need to create an item, map only the columns the next team works with. Each mapped column you drop saves one action per run.
Add conditions
"When status changes" fires on every status change. "When status changes to Approved" fires only when it matters. Adding a condition, such as a specific label, a priority or a group, is the cheapest way to stop runs that nobody needed.
Retire what nobody needs
A daily recurring item costs about 30 runs a month and a weekly one about four or five, and many checks work just as well weekly. Boards also collect automations that overlap or that nobody remembers creating: two that notify the same owner on the same change double the cost for no benefit. Review each board's automations every quarter and switch off anything without a clear owner.
Check what apps are doing
monday.com notes that apps installed from the Marketplace can create automations or integrations that consume actions in the background. If usage jumps without a new automation, check apps first.
How to track action usage
You do not need to wait for a warning email. According to monday.com's actions article, there are two places to see usage:
Autopilot hub, Usage tab. Shows how many automation and integration actions have been used and how many remain this cycle.
Administration, Usage stats. Shows the top automations, top boards and top creators by usage, each with a CSV download.
We recommend a short monthly check of the top consumers list. It takes five minutes and usually points straight at the one automation responsible for most of the usage, which is far easier to fix early than after the account runs into the following month's allowance.
Common mistakes
These are the action-related problems we see most often in accounts we are asked to review:
Choosing Standard for an operational process. The plan works for light use, but a process where every item triggers several handoffs usually outgrows 250 actions in days.
Counting automations instead of actions. Ten automations on a board say nothing about usage. Runs multiplied by actions per run is the only number that matters.
Notifying everyone. Subscriber and team notifications multiply by headcount. They are the single biggest source of surprise usage.
Ignoring the carry-forward. Going over the limit is not a one-month problem. The overage comes out of next month's allowance.
When to upgrade, and when to redesign
Running out of actions has two very different causes, and they need different answers.
If the automations are well designed and the business has simply grown, upgrading is usually the right decision. More orders, more work orders and more customers mean more legitimate runs. Fighting that with workarounds costs more in staff time than the plan difference.
If the usage comes from waste, such as subscriber notifications, copied data or duplicate automations, upgrading only hides the problem for a while. Redesign first, measure for one cycle, and then decide. Sometimes a review alone brings usage down enough to change the answer.
A third option is moving some logic to an integration platform such as Make or Zapier, or to a custom integration. These tools are genuinely good at multi-step logic across many systems, but they bring their own pricing, limits and failure points, so we recommend them when the logic needs them, not just to avoid monday.com's action count.
For broader setup issues that tend to show up alongside action problems, see our article on whether your monday.com setup is holding your team back. For an example of designing automations around handoffs from day one, see our blueprint for tracking work orders on monday.com. You can also see how our managed services keep monday.com accounts tidy as they grow.
Frequently asked questions
How many automation actions do I get on monday.com?
It depends on the plan. monday.com's support documentation lists 250 automation actions a month on Standard, 25,000 on Pro and 250,000 on Enterprise, plus the same number of integration actions on each plan. Free and Basic plans do not include automations or integrations. These figures were checked in November 2026, and monday.com can change them, so confirm on its pricing page before buying.
Do automation actions roll over to the next month?
Unused actions do not carry over in your favor, but overages do carry over against you. According to monday.com, actions used beyond the monthly limit are deducted from the following month's allowance. A Pro account that uses 28,000 automation actions in one month would start the next with 22,000. In extreme cases, an account can begin a month with no actions available.
Can I buy extra automation actions?
Only on Enterprise. monday.com's documentation says Enterprise customers can purchase additional actions through their monday.com contact, while Standard and Pro accounts are limited to the actions included in their plan. You also cannot pay to reactivate automations after running out, so the options are upgrading, reducing usage or waiting for the monthly reset.
Do integrations use the same actions as automations?
No. Every account has two separate monthly allowances, one for automations and one for integrations, each with the same size for a given plan. There are exceptions: custom templates that mix automation and integration blocks, workflow builder workflows and actions from monday.com apps all count against the automation allowance, even when they talk to an external tool.
Why are my actions running out so fast?
Usually because a few automations use several actions per run. The common causes are notifications to board subscribers or teams, which cost one action per person, cross-board item creation with mapped columns, and recurring daily templates. Marketplace apps can also run automations in the background. The Usage stats page lists the top automations and boards by usage, which normally points to the cause within minutes.
What happens to my automations when I hit the limit?
You get warnings first, by email and through a board banner. On Standard, monday.com describes a grace period before automation runs are paused, and an account that has used all of its current actions cannot add or edit automations, integrations or workflow blocks. Manual work on boards is not affected, so people can still update items while automations are paused.
Do Formula or Mirror columns use actions?
They are not automations, so they do not run or count as automation actions. Formula columns calculate from other columns, and Mirror columns display values from linked items on other boards. That is why replacing copied data with a Connect Boards and Mirror pair is one of the most effective ways to reduce item-creation automations. Note that Mirror columns cannot be used as triggers in board automations.
Is the Pro plan enough for a midsize company?
It depends on usage, not headcount. Pro includes 25,000 automation actions and 25,000 integration actions per month. Accounts with several departments, frequent two-way syncs or heavy email integrations can go through that faster than smaller ones. Before deciding, estimate your usage: count how often each automation runs in a month, multiply by the actions each run uses, and add the results across boards. Then compare the total with your real numbers in Autopilot hub → Usage. Keep in mind that Pro accounts cannot buy extra actions; only Enterprise can, and Enterprise includes 250,000 per month. If your estimate sits close to the Pro limit, redesign the heaviest automations first, then decide.
Sources
monday.com Support. Automation and Integration actions and limits
monday.com Support. Automations and integrations pricing
monday.com Support. Get started with monday automations
monday.com Support. The AI workflow builder: active workflows and actions
monday.com Support. The Mirror Column
Want a second opinion on your automations?
Find out where your monday.com actions go and what to change, in a free 30-minute working call or a two-minute readiness check.