Notify on a status change
When Status changes to Stuck, notify the item's owner and their lead. The single most useful recipe on most boards.
A monday.com automation is a sentence: when something happens on the board, and only if a condition holds, then do something. monday calls these recipes. They cover notifications, status moves, assignments and recurring items without any code. Below: where to build one, which to set up first, how the monthly action allowance gets used up, and what to do when the logic needs facts that live outside your boards.
Open the board and click Automate in the top right. The Create tab lists ready-made recipes by category, and Manage shows what's already running on this board.
Board › Automate › CreatePick a template, fill in the underlined parts of the sentence (which status, which person, which group), and create it. For anything the templates don't cover, start a custom automation and build the trigger, condition and action yourself.
Automations are a paid-plan feature. On monday's pricing page, Standard includes 250 automation actions a month, Pro 25,000 and Enterprise 250,000.
All of these run entirely inside monday, and none needs anything built.
When Status changes to Stuck, notify the item's owner and their lead. The single most useful recipe on most boards.
When Status changes to Done, move the item to the Done group, so the active part of the board stays short.
When Status changes to Ready for review, assign the reviewer. No one has to remember who's next.
When the due date is one day away, notify the person assigned, and only if Status isn't Done.
Every Monday, create an item for the weekly report. A fixed schedule works well. A rhythm that depends on something else, like how often a client reorders, doesn't.
Type "match" into the automation center search to find recipes that link or update items across boards, such as creating a project item when a deal closes on the sales board.
How you'll know: Recipes that worked last week do nothing, and there's no error on the item.
Fix: You've likely used the month's automation actions. Every action a recipe takes counts, and a recipe that notifies three people or updates several columns uses more than one. Marketplace apps draw on the same pool. Check usage in the automation center, trim recipes that fire on every small edit, and move high-volume jobs elsewhere. Note that monday's newer Workflow Builder has its own separate cap on active workflows.
How you'll know: You can build "when status changes" for items, but the same option is missing or narrower for subitems.
Fix: That's how monday works, not a broken recipe. Subitems have a smaller set of triggers and actions than top-level items. Some teams roll the subitem status up into a parent column and automate on that, others use a marketplace app or the API.
How you'll know: A recipe moved the item on schedule, and later someone finds the customer was on credit hold or the part was out of stock.
Fix: A recipe only sees what's in monday's columns. If the real answer lives in your accounting system, ERP or e-sign tool, something has to fetch it before the status changes. That's not a recipe job.
How you'll know: Every new client board needs the same set of automations clicked in by hand, and old boards drift when the standard changes.
Fix: Build the recipes into a board template so new boards start with them. monday's public API reads and writes board data but doesn't create recipes, so updating existing boards in bulk means scripting the automation center itself.
The gap isn't in monday's automation builder. It's in what monday can know. A recipe can react to a date, a status or a person, but it can't ask QuickBooks whether the invoice was paid, ask your inventory system whether the part is on the shelf, or confirm that the contract came back signed.
n-frames builds the piece that sits between monday and those systems. It listens for the item reaching a stage, runs the real check, and writes the answer back into a column or sets the status itself, so the board reflects what's true. The same connection can carry jobs that would burn through the action allowance. Our monday.com CRM API page covers what monday's GraphQL API can reach, and monday integrations covers the built-in connectors.
It depends on the plan. monday's pricing page lists 250 a month on Standard, 25,000 on Pro and 250,000 on Enterprise. When you run out, automations stop running until the allowance resets, so check usage before building anything critical on them.
Yes. A recurring recipe such as "every week, create an item" handles a fixed schedule well. When the timing depends on something variable, like when a project phase finishes or how often a client reorders, a fixed recurrence can't follow it.
Subitems get a narrower set of triggers and actions than top-level items. If the option you want isn't offered for a subitem, that's usually the reason, not a mistake in your recipe.
No. monday's GraphQL API reads and writes board data, but the recipes themselves are built in the automation center. You can't create or edit a recipe through the API.
Notifying someone by email or Slack when a status changes, moving an item to another group when it's done, assigning a reviewer on hand-off, reminding before a due date, and creating an item on a schedule. All run on information already in your boards.
No. Automations come with the paid plans from Standard upward, and each plan's monthly action allowance is listed on monday's pricing page.