Include recurring-information on task payload and being able to set recurring settings through API
Anders Jessen
As of now there is no information about the recurring settings on a task in the payload when you fetch task information through the public API.
It would also be great to being able to set recurring settings on a task through the API when you update or create a task.
Log In
J
John Smith
I want agents to be able to create, inspect, update and stop recurring tasks through the official ClickUp API and MCP connector. A task with a Friday due date is not a weekly recurring task.
My concrete case is a task every Friday after 16:00, in Europe/Sofia, recurring indefinitely on a schedule. The agent can create the task, but has to switch to the browser UI to configure recurrence. That defeats the point of an agent workflow.
If this is an intentional restriction, it is a senseless product limitation. If it is an omission, it is unacceptable for a product that promotes automation and AI agents.
Please add documented recurrence fields or endpoints covering cadence, timezone, schedule versus completion triggers, new-task versus reuse behavior, and end conditions. The API must also return the saved recurrence so an agent can verify it. MCP needs the same capability under the user's normal task permissions.
Is this intentional, and what is the plan to fix it?
R
Rex Stevens
Would love this. Our entire workflow is all around recurring tasks so like 80-90% of our tasks are recurring and we can't set this up via the API which really limits our automation capabilities