The status column is green, yellow and red. None of those colours explain what the work actually is — they summarise a conversation that may never have happened.
What it does
- Set an item's status column to analyze, and the AI posts a repo-grounded breakdown as an update.
- Reply on the item, and it answers and sharpens the scope with you.
- Set the status to build, and it opens a pull request.
- It talks to Monday over GraphQL, with a challenge-echo relay that routes every board event.
What it will not do
It never changes your status column, never edits other columns, and never merges. On a board where the status column drives automations of your own, an agent that cannot write to it is the only kind that is safe to leave on.
GraphQL, and the challenge echo
Monday's API is GraphQL, so the recipe asks for exactly the fields it needs instead of pulling whole boards. Setting the webhook up means answering Monday's challenge request correctly on the first call; the relay handles that echo, which is the step that usually costs an afternoon.
Setup takes about five minutes
Clone the repo, run ./setup.sh, pick Monday.com, and answer a few questions — your IDs, your tokens, your conventions. The installer copies the recipe into your repository, sets your secrets, and prints whatever manual steps are left with your real values already filled in. No server to host, no database to run, nothing to pay for beyond the AI you already use.
Honest status: beta. It is built and smoke-tested, and it carries a live-fire checklist in its README that I am working through one tool at a time. It is waiting on live boards. If you hit an edge, open an issue — that is exactly what the beta label is asking for.
The recipe is MIT-licensed and open source: ai-automations. It is one of 35 — see the series overview for the full list and the rules every recipe follows. If your tool is not on the list, name it and I will build the automation for it, free.
FAQ
Will it change the status column?
No — and that matters most here, because the status column often drives automations of your own. It never changes status, never edits other columns, never merges.
How does it talk to Monday?
Over GraphQL, asking for exactly the fields it needs rather than pulling whole boards.
What about Monday's challenge request when setting up the webhook?
The relay echoes it correctly on the first call. That step is usually the one that costs an afternoon.
More in this series: Asana · GitHub Issues · all 35 automations
Working on something similar?
If you are wiring AI into the tools your team already uses, I am happy to look at it with you. Thirty minutes, no deck — bring the workflow that costs your team the most time and we will work out whether it is automatable. Get in touch.