monday.com Automations: How They Work, Limits by Plan and 12 Recipes Worth Setting Up

How monday.com automations work

Every automation has three parts. monday's help center defines them like this: a trigger is the event that sets the automation off, a condition is a requirement the trigger must meet, and an action is what happens once both are met. A trigger can be a column changing (Status, People, Date) or an event such as an item being created or a set time arriving.

You build them from the board. Click Automate, then either pick a template from the automation center or choose Create from scratch and fill in "When this happens" and "Then do this". One automation can carry several actions in a row: click the plus sign next to the first action to add the next one. You can switch an automation off without deleting it, which is worth knowing because deleted automations can't be restored. You also can't change the trigger of an existing automation; monday's advice is to duplicate it, change the copy and delete the original.

Automations can also work across boards. Cross-board templates let a change on one board create, move or update an item on another, and many of them link the two items through a Connect Boards column. To find them, search the automation center for "in board" or "in another board". Two catches from monday's own article: a column you want to carry across must exist on both boards, and the updates section moves only with "move item" automations, not with ones that create a new item.

monday.com automation limits by plan

monday meters automations in actions, with a separate monthly quota for automations and for integrations (Gmail, Outlook and other connected tools). Automations and integrations are only available on Standard and above. The AI workflow builder has its own limit on how many workflows can be active at once, and running out of one limit doesn't touch the other.

What counts as an action, and when the quota resets

Most of the time, one run of an automation uses one action. monday's example is "When a status changes to something, delete the item": delete three items that way and you've used three actions. The exceptions are where quotas disappear faster than people expect.

Creating an item uses one action for the item, plus one more for each Status, Tag, People or Dropdown column, or update, that you map into it. A notification sent to board subscribers or a team uses one action per person, so 6 subscribers means 6 actions every time it runs. An email sent through the Gmail or Outlook integration to a text column with several addresses uses one action per address. Condition steps in the AI workflow builder count too.

Two other rules catch people out. A custom automation you build counts against the automation quota even if it contains only integration blocks. And apps installed from the monday marketplace can create automations or integrations that use actions in the background, so if the quota drains faster than your own rules explain, check the apps.

The quota resets with your billing cycle. On monthly billing it renews each month on the day you activated the account; on yearly billing it renews on the 2nd of every month. To see what's using it, open the Autopilot hub and the Usage tab, or Administration and then Usage stats, where you can download your top automations, boards and creators as a CSV.

What happens when you run out of automation actions

monday's help center describes the Standard plan this way. The first time you hit the 250-action quota, you get an email and nothing stops yet; the overrun rolls over to the next cycle as "actions debt". The next time, billing contacts are warned at 50% and 80%, and at 100% you get a 72-hour grace period before automation runs are paused. Once the month's actions are all used, the account can't edit or add automations or integrations either.

Debt can eat the next month too. monday says it's possible to use up the current month and the following one, and start a month with zero actions. In that case monday recommends moving up a plan.

There's no top-up below Enterprise. Only Enterprise customers can buy extra actions, and you can't pay to have actions reactivated after you run out. Your options are to switch off the automations that use the most, wait for the reset, or move up a plan. monday's own note on Standard is blunt: 250 actions a month "is typically exhausted within days" for accounts that notify several people or map several columns per automation.

12 monday.com automation recipes worth setting up

Each recipe below is written the way monday shows it in the automation center or its help articles, followed by what it's for. The words in braces are the parts you fill in. Where a recipe costs more than one action per run, the note says so.

• Sales and CRM, 1: "When an item is created in this board, connect the item where this column matches this column in another board by this logic." Links a new deal to its company or contact record by matching an email or a name. monday marks match automations as beta.
• Sales and CRM, 2: "When status changes to something, send an email to Text Column." Sends a follow-up from Gmail or Outlook when a deal reaches a stage. It counts as an integration, one action per address.
• Sales and CRM, 3: "When {date} arrives, notify someone and push {date} by 12 months." monday's help center shows it with a birthday column; pointed at a renewal date, it reminds the account owner every year.
• Projects, 4: "When status changes to something, set due date to current date plus some days." Gives a task its deadline the moment it starts.
• Projects, 5: "When status changes to something, start time tracking. When it changes to something stop." Logs time without anyone pressing a button.
• Projects, 6: "When a status changes to something, move item to group." Moves finished work into a Done group so the board shows what's still open.
• Operations, 7: "Every time period, create an item." Recurring tasks: a weekly report, a monthly stock check. Mapping Status or People columns into the new item adds an action each.
• Operations, 8: "When status changes to something, create an item in board." Hands work to the next team, for example a signed deal becoming a project on the delivery board. Mapping two Status columns makes it 3 actions a run.
• Operations, 9: "When due date arrives, move item to board." Moves items to an archive or a review board on their date.
• Notifications, 10: "Every day, if {due date} has passed and only if {status} is {something}, notify someone." A daily nudge on overdue items that aren't done yet.
• Notifications, 11: "When status changes from something to something else, notify someone." Tells one person about a specific move, such as Stuck to Working on it.
• Notifications, 12: "When a status changes to something, notify board subscribers." Useful for a small board. On a board with many subscribers it's the fastest way to burn the quota: one action per person, every run.

Where native monday.com automations stop

Native automations handle one board and the boards next to it well. They get harder in four places.

The quota. On Standard, a few multi-action recipes can use up 250 actions in days. A two-way sync with a tool your team uses every day "may not be a good fit" for Standard, monday says, and it points heavy Gmail or Outlook users to Pro or Enterprise.

Logic. A custom automation is one trigger, its conditions and a list of actions. The AI workflow builder adds if/else and branching paths, but every condition step uses actions, and the plan limits how many workflows can be active: 3 on Standard, 20 on Pro.

Systems monday doesn't connect to. If a tool has no monday integration, or the integration doesn't have the trigger you need, native automations can't reach it.

Errors. monday rate-limits automations per automation, board and account. When a limit is hit, runs are slowed down, delayed or cancelled, and a blocked run fails with an error; monday warns that a rising error rate can lead to an automation being switched off automatically. Loops, batch actions and automations triggered from the API are the usual causes. The help center also lists column types automations don't support at all, including Mirror, Phone, File, Link and Location.

Past those points, teams move the logic out of monday. Make has a monday.com app and n8n has a monday.com node, and both can run the multi-step parts, call other systems and handle errors, while monday stays the board people work in. The monday API is the third option when a connector doesn't expose what you need.

monday.com automations vs Make vs n8n

When we build on monday.com, native automations handle what stays on the board, and n8n, Make or the monday API handle the deeper logic and the other systems. The billing units differ, which matters when you compare costs: monday counts an action for each thing an automation does, Make charges credits per module action ("most actions consume 1 credit", says its pricing page), and n8n counts one execution per run of a whole workflow, however many steps it has. Our Make vs n8n vs Zapier comparison puts prices on the last two.

Real setups we've built

monday.com is the most common platform in our client records: 86 of the 258 clients with a recorded tech stack (May 2021 to October 2026) had it. Two examples we can describe, without names:

• A vending operator: a multi-location management system on monday.com.
• A construction company: a monday.com restructure for a team of 20+ people.

Getting help with monday.com automations

If your automations have grown into something nobody wants to touch, or you keep hitting the quota, the fix is usually a mix of trimming what runs and moving the heavy logic to Make or n8n. That's the work on our monday.com automation and implementation page. If you're still comparing who to hire, our guide on how to choose a monday.com consultant has the questions to ask, us included.

Our prices, from that page, checked there on 12 November 2026, are below. The fixed price is agreed on a free 30-minute call. monday.com seats are a separate bill, paid to monday.com. Retailbox Automation is a small agency (2–9 people, Orlando, FL, working since 2019).

Related services

Frequently asked questions