Monday automation works well for moving work along one board, such as assigning an owner, changing a status or notifying someone, and it gets fragile once the logic spans boards, subitems, outside systems or money. The cost is quiet: a deal that never reached invoicing, a task nobody was assigned, a client email never sent.
monday.com makes automations easy to add. What it does not make easy is knowing which ones still run, which count against the monthly action allowance, and which stopped when someone left. Benian Technologies builds and repairs this work through its Workflow Automation service, in accounts your business owns.
Where monday.com automation usually breaks
The action allowance runs out mid-month
Automation and integration actions are counted per month by plan. When a busy board uses the allowance, recipes stop running until the count resets or the plan changes, and teams often learn this from a missed handoff.
Subitems do not behave like items
Recipes that work on items often have no subitem equivalent, or behave differently on subitems. A project board that tracks real work in subitems ends up with manual steps nobody wrote down.
Mirror and formula columns cannot start anything
A value that only appears through a mirror or formula column generally cannot trigger a recipe. The board shows the right number, but nothing reacts when it changes.
Automations owned by people who left
Recipes and integration connections are tied to the person who created or authorized them. When that account is deactivated, loses access or has its connection revoked, the automation can stop with no visible warning on the board.
Monday automation recipes: triggers, conditions, actions
A monday.com automation is a recipe: a trigger, optional conditions and one or more actions. When status changes to Approved, and priority is High, assign the account manager and notify the channel. You can pick a ready-made recipe or build a custom one from the same parts, and each recipe belongs to a board.
Recipes are good at work that stays on one board: setting dates, moving items between groups, creating an item in another board, assigning people and sending notifications. They are weaker at anything that needs memory, such as checking whether a record exists elsewhere, looping over many records or retrying after a failure.
A practical test: if the rule fits in one sentence that names one board, a native recipe is the right home. If it needs the words unless, for each or in the other system, plan for something sturdier.
Automation and integration action limits
monday.com counts automation actions and integration actions against a monthly allowance that depends on your plan. The numbers change over time, so check the current figure in your account's administration area rather than trusting a blog post, ours included.
Every action a recipe takes is counted, so a recipe that notifies three people and updates two columns uses several actions each time. A busy status board, a form that creates many items or a large import can use a big share of a month in a day.
- Check the automation and integration usage shown in your account before adding more recipes to a busy board.
- Merge recipes that fire on the same trigger instead of stacking separate ones.
- Move high-volume syncs, such as every new form submission into a CRM, to an outside workflow, where they no longer use the board's allowance.
Subitems, cross-board work and mirror column gaps
Subitem automation is a frequent need on monday.com boards, because subitems hold the tasks while the parent holds the deal or project. Native subitem recipes are narrower than item recipes, and rolling subitem progress up to the parent often needs a workaround.
Cross-board work has a similar gap. The connect boards column links records, and a mirror column displays the linked values, but a change that only shows up through the mirror generally does not fire a recipe on the board that displays it. The reliable pattern is to trigger on the board where the real change happens, then write the result across. When those workarounds pile up, one outside workflow that reads every subitem through the API and writes a single status back to the parent is easier to maintain.
monday.com email automation
monday.com can send notifications to people inside the account, and integration recipes can send email through a connected Gmail or Outlook account when a status changes or an item is created. That covers internal alerts and simple confirmations, such as telling a client their request was received.
It is a poor fit for sequences, emails that must stop when someone replies, or messages built from outside data. The email also goes out under whichever mailbox was connected, so for client-facing mail we connect a shared mailbox the business controls.
monday CRM integrations, Pipedrive, QuickBooks and Google Sheets
The integrations center lists connectors for common tools, and the marketplace adds more. Before relying on one, check three things: which direction data moves, which fields it maps, and what happens when a record is edited on both sides. A connector that only creates new items will not keep a changed deal amount in sync.
- CRM: monday CRM is monday.com's own sales product. If sales already lives in Pipedrive, HubSpot or Salesforce, keep that as the record for deals and push won deals into a monday.com delivery board.
- Pipedrive integration: decide which system owns each field. A won deal creates the project item in monday.com, and delivery status flows back to one Pipedrive field. Two-way sync of every field is where duplicates start.
- QuickBooks integration: monday.com does not do accounting, so the link usually means creating an invoice or customer in QuickBooks when an item reaches a billing status. This step touches money, so we add a human approval before the invoice is created and a check that the customer does not already exist.
- Google Sheets integration: useful for reporting exports and for feeding a board from a sheet another team keeps. Add an ID column so edits do not create duplicate items.
Why monday.com automations stop working
When monday automations are not working, the cause is almost always one of these. The fix is rarely a new recipe; it is finding which one happened and adding an alert so the next stop is seen the same day.
- The monthly automation or integration allowance ran out.
- The person who created the recipe or authorized the connection was deactivated, lost board access or revoked the connection.
- A status label, column or group the recipe references was renamed or deleted.
- The trigger depends on a mirror, formula or subitem value that does not fire recipes.
- Two recipes conflict, so one reverses the other's change.
- An outside app's connection expired or its permissions were narrowed.
When Benian moves logic into an outside workflow
We keep simple, single-board recipes in monday.com, where the team can see and change them. We move logic out when it spans systems, handles money, runs at high volume or must never fail silently. In those cases the workflow runs in your own n8n account, reads and writes monday.com through its API and webhooks, and sends an alert to a named person when a step fails.
That workflow keeps a run history: every record it touched, when and with what result. What to measure afterwards: missed handoffs per month, items stuck in a status past an agreed time, and hours of retyping removed.
When not to hire us: if your boards are new, the process is still changing weekly, or you need one or two recipes on a single board, set them up yourself with the native builder. Automation fixes a process that is already agreed. It does not decide the process for you.
How a monday.com automation cleanup runs
- Inventory every recipe. List each automation and integration by board, creator, trigger and action usage.
- Map the real process. Write the handoffs as the team works them, including exceptions handled in chat today.
- Decide where each rule lives. Single-board rules stay native. Cross-system, high-volume and money-touching rules move out.
- Fix ownership. Move connections to an account the business controls, not one employee's login.
- Build with alerts and approvals. Add failure alerts, duplicate checks and a human approval on invoicing, then test edge cases.
- Hand over. Your team gets the workflow files, an operating guide and a walkthrough of what to do when an alert arrives.