Project Creation from Template via REST API – CRM Triggered Integration

[Dimitris Tranoudis]

Hi all,

A prospect customer is interested in automating the creation of projects in Clarity, based on the following integration scenario:

• A new project should be created automatically from a specified project template (identified in the call)

• The trigger event is an opportunity marked as "Closed-Won" in an external CRM system (Salesforce)

I would like to confirm the following:

1. Does Clarity REST API v1.0 support specifying a template (e.g., template.id) when creating a new project?

2. If this is not currently supported, what are the alternative options to implement this integration?

Thanks in advance for your support and suggestions.

[Paul Schofield]

Looks like my original answer got lost. Try this in the JSON  "originTemplate": "string"

If using that doesn't work, you could use a GET to pull the template in, then adjust the name and ID (plus anything else that needs to change) and then POST the updated JSON to create the new project. You'll most likely need to do this in stages. Create the project first, and then GET/Post the tasks etc.

[Later]

I just tried this but it appears that parameter just tells you which template was used to create the project. It's ignored when creating the project, so the GET/POST might be the way to go.

[Paul Schofield]

I've made this work, but it's probably not supported as it uses a private API call /private/investmentTemplateCopier with this POST payload

{
    "templateId": "5000004",
    "name": "CCCCC",
    "objectAlias": "projects",
    "_objectAttributes":{},
    "scheduleStart": "2025-06-12T15:39:00",
    "scheduleFinish": "2025-06-12T15:39:00",
    "code":"ccccc"
}

The templateId is the OOTB Major Project Template. CCCCC and ccccc are the name and ID for the newly created project. It copied the Team and Tasks across, but it's your choice of whether you want to go down this route.

Good luck,

Paul

[Luis Palacios]

Agree with Paul, just take into account MUX/REST API endpoints related to templates are all considered private. Which means they can change across versions / not documented. If you go this route just make sure its part of your maintenance / upgrade checklist.