Allow AI Agents to set, change or remove task recurrence
future
Grace Robinson
After building and testing with lots of audit log fails, Brain finally admitted that my set up was correct but that it just can't do the request yet:
"However, your automation is likely failing because ClickUp’s API and Agent tools do not currently support programmatically setting or updating recurrence rules for tasks via automation or API. This is a known limitation: while you can update task fields, status, and other properties, recurrence settings (like "recur forever," "skip non-working days," or "on a schedule") are not exposed for automation or API updates. When it tries to set the recurrence, it fails because this action is not supported by the available automation tools. If ClickUp releases an update to allow recurrence to be set via automation or API, you’ll be able to automate this step in the future."
Log In
Nick Thue
This affects Brain-assisted setup too. Brain created 34 meeting-prep tasks for me, but I must manually configure identical 13-week recurrence on each. Please support this through Brain and Agents, and allow bulk editing of recurrence settings.
T
Troy Johnston
Zach - ClickUp We would be even very interested in AI agent being able to 'read' recurrence meta-data so it can even tally or report on it. If this is regarded as simpler or safer as a first tranche foray (instead of the ability to update such settings) then we would be very interested in it.
Zach - ClickUp
Merged in a post:
Super Agent Task Recurrence
Anika Lowman
I'd like to have my Super Agent remove the recurrence from the Due Date of a task (under certain conditions). Having tested this, this is not a tool that is available to the Agents.
Zach - ClickUp
updated the status to
future
Zach - ClickUp
Appreciate you sharing Brain's response directly — that's exactly what's happening. Recurrence settings aren't currently exposed via our automation or API layer, which means Brain can recognize the intent but can't execute it. It's a real limitation.
This one sits at an interesting intersection: it's partly an API gap (recurrence as a writable property), partly an AI Agent capability question. We're tracking interest in both. Can't give you a timeline, but this is a legitimate ask and the use case is clear.