Automation loop in campaign review handoff
A 10-person marketing team runs 12 campaigns a month across email, paid social, and webinars. The Campaigns board has a status column with New, In production, Ready for review, Approved, and Live. A form creates campaign items and assigns the team lead. One automation creates a review item on a separate Review board when campaign status becomes Ready for review; another updates the campaign status to Approved when the review item’s status becomes Approved; a third posts to Slack whenever any status changes. Last month the team saw 38 review items for 12 campaigns, reviewers received duplicate Slack alerts, and two campaigns sat in Ready for review for nine days. The team also connected a shared Gmail inbox so every incoming email creates a campaign item, including newsletters and invoices. The account uses 78% of its monthly automation action quota. The marketing lead owns most automations and is moving to a different team next month.
1. Diagnose the most likely cause of duplicate review items and the stalled campaigns, and describe the evidence you would collect before changing recipes.
Read the worked answer
Start with the automation activity and item history, because duplicates and stalls usually have different causes. Duplicates most likely come from a re-entrant status path: a campaign moves to Ready for review, the review item is created, approval sets the campaign to Approved, and another rule or a manual edit moves it back to Ready, creating a second review item. Two recipes with the same trigger would produce the same symptom. The nine-day stall points to execution failure: recipes run as the automation owner, and the owner is leaving; if that user loses access to the Review board or is deactivated, the create or update action can fail silently. I would collect the recipe run history, the owner of each recipe, board permission changes, and timestamps of status changes and Slack posts. I would also check the Gmail integration, because unrelated email items can enter the same status path and consume actions.
2. Redesign the handoff so it is idempotent and survives staff changes.
Read the worked answer
Make the handoff idempotent by adding a gate on the campaign item: a checkbox or status called Review created. The create-review automation should fire only when status changes to Ready for review and Review created is unchecked; the same recipe then checks the box. That prevents a second review item if the status bounces. The return path should set the campaign to Approved and close the review item, and it should not set the campaign back to Ready. Use one cross-board automation with a condition rather than two recipes that can chase each other. Move ownership of all recipes to a service account or a team admin with access to both boards, and document the owner in the board description. Finally, filter Slack notifications to Approved and Blocked only. This is idempotent because repeated status changes cannot create duplicate reviews once the gate is set, and it survives staff changes because the owner is a durable role account.
3. What should the team do about the Gmail integration and the automation quota?
Read the worked answer
Treat the shared inbox as an intake problem, not a campaign board problem. The Gmail integration should watch a dedicated address or label such as campaigns@, not the whole inbox, so invoices and newsletters never create items. For campaign requests, use a form with required fields and a routing rule; for everything else, route to a triage board or shared inbox outside monday.com. The 78% quota is a warning: count actions per campaign and remove redundant Slack posts, batch notifications into a daily digest, and avoid recipes that fire on every column change. I would set an alert at 80% and a monthly review of the top recipes by action count. If the team cannot stay under quota, consolidate the review handoff into one automation and use a scheduled digest rather than real-time alerts.