You have custom statuses for everything. What you do not have is someone to fill in the thinking between them — the part where a task stops being a title and becomes a plan.
What it does
- Change a task to your analyze status, and the AI posts a plain-English breakdown grounded in your repository.
- Reply in the task comments, and it answers and refines the scope with you.
- Change it to your build status, and it opens a pull request.
- An HMAC-verified relay routes every ClickUp webhook event, so the whole workspace can wake it, not one list.
What it will not do
It never changes a status, reassigns a task, or merges a pull request. It writes, you decide. In a workspace with heavily customised statuses that matters more than usual — the agent cannot invent a transition your process does not have.
Verifying the webhook
Every incoming event is HMAC-verified before anything runs, so an unsigned request cannot trigger an AI run against your codebase. The signature check costs nothing and closes the most obvious way an open webhook endpoint gets abused.
Setup takes about five minutes
Clone the repo, run ./setup.sh, pick ClickUp, 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 still needs a live workspace to shake out. 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 task statuses?
No. It never changes a status, reassigns a task, or merges a pull request. In a workspace with heavily customised statuses that matters — it cannot invent a transition your process does not have.
Is the webhook endpoint safe to expose?
Every incoming event is HMAC-verified before anything runs, so an unsigned request cannot trigger an AI run against your codebase.
Does it work across the whole workspace?
Yes. The relay routes every ClickUp webhook event, so the workspace can wake it rather than a single list.
More in this series: Trello · Notion · 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.