Is there a way to create a project from a template? I have a project currently set as a template, and would like to create new projects from it using the API.
The only thing I found regarding templates is setting a project as a template with this(which is not what I am looking for):
PATCH /workspaces/{workspaceId}/projects/{projectId}/template
Thanks
Hi Jordan,
With the current API documentation is not possible to create a project from the template via API. I will forward your feedback as a feature request to our Product team so they can have it in mind for future development.
Cheers,
+1. Without this I will need to read all the tasks from the project template and then use these when creating my new project, which is a pain. Would be great just to specify a project template ID upon creation of a new project.
Hello Kurren,
Thank you for sharing this with us.
We have forwarded your suggestion to the team so they can review and consider it for future updates of the feature.
Thank you for taking the time to write a comment.
Cheers!
We need this too, please.
Hello Jenny,
Thank you for using the Clockify Forum.
I’ll add your vote for this feature as well.
Cheers!
Definately a useful addition to the API. We’d love to create projects automatically when they are tiggered by our other systems, but they’d need the template specifying.
Hi, is there an update on this? It has been over a year and it would be very useful to have this feature for our company’s automation.
Hi, still looking for this addition. I’m trying to add tasks to a newly created project via a zapier loop. It appears to work correctly in Zapier, but is very task hungry and expensive (47 tasks per standard project) and seems to fail to add a subset of tasks for no obvious reason (the audit in Zapier appears OK). It’d be SOOOOO much easire just to create a project from a template via the API. It’s such a common task. New standard project gets set up in an external project management system ----> add it to clockify so staff can log their hours against it. Please add this API modifictaion ASAP. Roland
Hi @Roly
Thank you for your feedback. We’ve added a vote to the feature to our product team for consideration in future updates. We appreciate your interest in improving our API.
All the best.
Adding projects via Zapier is functional but inefficient. An API method to create a project from a template would streamline the workflow significantly
Hi @jakasspeech9, thank you for sharing valuable feedback on this functionality. I will forward your suggestion regarding an API request that allows project creation from template to our product team for consideration. Kind regards.
Why not add to the API? I see other aspects of templates has been deprecated in API, but not sure why.
It’d be really helpful if I could “duplicate” a project (e.g., use an existing template project to create a new project), that way we don’t need to use the API to set tasks, budgets, default custom fields, etc.
Hello Jon,
The team is planning to add the improved endpoint in question in one of the future releases.
If you have any other questions, feel free to let us know.
Have a nice day!
Hi, still looking for this addition. I’m trying to add tasks to a newly created project via a zapier loop. It appears to work correctly in Zapier, but is very task hungry and expensive (47 tasks per standard project) and seems to fail to add a subset of tasks for no obvious reason (the audit in Zapier appears OK). It’d be SOOOOO much easire just to create a project from a template via the API. It’s such a common task. New standard project gets set up in an external project management system ----> add it to clockify so staff can log their hours against it. Please add this API modifictaion ASAP. Roland
Das Zapier-Loop-Problem ist klassisch. Neben den Kosten läuft man bei ~50 Tasks pro Projekt auch extrem schnell in API Rate-Limits (429 Errors), wenn man im Loop keine künstlichen Pausen (“Delay”) einbaut. Das erklärt oft, warum manche Tasks einfach verschluckt werden, obwohl der Audit “grün” aussieht.
Hoffen wir mal, dass Natalie recht behält und der Endpoint bald kommt. Das würde die Automatisierung massiv stabilisieren.
*Beste GrĂĽĂźe
*
The Zapier loop problem is a classic. Besides the costs, with around 50 tasks per project, you quickly hit API rate limits (429 errors) if you don’t build in artificial pauses (“delays”) within the loop. This often explains why some tasks are simply lost, even though the audit appears “green.”
Let’s hope Natalie is right and the endpoint arrives soon. That would massively stabilize automation.
Best regards