How to set up Monday.com automations without breaking your boards

Trigger = the event that starts the automation. Examples: "When status changes to X," "When a date arrives," "Every Monday at 9am," "When item is created."

Condition = an optional filter. Examples: "Only if owner is empty," "Only if Priority = High."

Action = what happens. Examples: "Notify person," "Move item to group," "Change status to Y," "Create item on another board," "Send email."

Recipes are pre-built Trigger+Action combos from the Automation Center. They cover ~80% of common patterns and are safer to use than custom (they handle edge cases for you).

Custom Automations are the IF/THEN builder. Use when no recipe matches your need. They are more error-prone but unlock cross-board flows and multi-step actions.

Open any board → click the Automations icon (lightning bolt) in the top-right.

"Add automation" → "Browse automations" opens the Automation Center with categories: Status Changes, Notifications, Recurring, Item Creation, Dependencies, Date, Cross-Board, Email, Integrations.

Start with these 5 high-value recipes for any sales/ops team: (a) "When status changes to Done, notify person," (b) "When date arrives, notify person," (c) "Every Monday at 9am, create item in group," (d) "When status changes to X, move item to group Y," (e) "When item is created, assign to person Y."

Add the recipe → configure the parameters (which status, which person, which group) → Save. Test by triggering the condition manually and confirming the action fires.

Automation Center → Custom Automations → Create custom automation.

Pick a trigger. Common: "When a column changes," "When an item is created," "When a date arrives," "Every time period."

Optionally add a condition: AND/OR filters. Example: "When status changes AND priority = High AND owner is empty."

Add one or more actions. Multi-action examples: "Notify person AND change status AND move to group AND set date."

Save and label the automation clearly. Bad: "Untitled automation 4." Good: "[Deals] Notify AE when deal moves to Proposal stage."

Common pattern: "When status on Deals board changes to Closed Won, create item on Onboarding board." This hands deals from Sales → CS automatically.

In Custom Automation: pick the trigger on Board A → action "Create item in board" → choose Board B → map fields from A to B.

Field mapping is the dangerous part. If Board A has "Deal Value" (Numbers) and Board B has "Account Value" (Text), the mapping will silently lose precision.

Always map keys (Account Name, Contact Email) AND the Connect Boards column itself so the new item is linked back to the source — without this, you cannot trace the parent record.

Test on one record. Verify the new item has every expected field populated. Verify the Connect Boards link works in both directions.

Board → Integrations icon (next to Automations) → Browse integrations.

Key integrations to set up early: Slack (post item updates to channels), Gmail / Outlook (log emails to items, send emails from items), Google Calendar (sync dates), Microsoft Teams.

Each integration adds its own automation recipes: "When item created → post to Slack #sales," "When email received from X → create item."

Prefer native integrations over Zapier/Make. Native = faster, fewer failure points, included in your Monday plan. Zapier = more flexibility but $20-100/mo extra and adds latency.

Document every integration in the same registry as automations (next step). Integrations break silently when tokens expire; you need the registry to find them.

Create a Monday Doc in your "Team Handbook" workspace called "Automation Registry."

Columns: Automation Name, Board, Trigger, Action, Owner (who is responsible for it), Date Created, Last Reviewed.

Document every non-trivial automation as you create it. Skip "notify me when status changes" but document every cross-board flow, every email-sending automation, and every recurring schedule.

Review quarterly. Disable automations that have not fired in 90 days. Reassign owners when people leave the team.

Without this registry, automations become tribal knowledge that breaks when 1-2 people leave. With it, the system is auditable.

Account → Administration → Automations & Integrations → Activity log.

Filter by board, automation, status (success / failure), date range. Failed automations show the reason — usually permissions, missing data, or external integration timeout.

Set a weekly habit: review failed automations every Friday. Fix or disable the recurring failures.

High-impact automations (sales handoffs, billing alerts, SLA timers) should have a backup human check until you trust the automation. The cost of a missed "Closed Won → notify CS" is real — a $20K deal that sits 2 weeks without onboarding outreach is a measurable churn risk.