Hello Boris, Excellent question! I have requested the AW expert to review and address this. 

Hey Boris, the only time you can apply a project-level template is at the very instant a project is created. Therefore, the short answer is no, you could not have a workflow rule apply a template to a project that was created by an API call. But as you noted, the API calls do allow for specifying a template during project creation. So the trick would be to determine which template to use based on the data available to the API. You’ve got data in two systems, or maybe even three: First, the source system that’s providing the initial project data. Second, the destination (AdaptiveWork) has its own set of data, including the available templates. And third, if you have a robust iPaaS or web service making the API calls, it could also be a source of data. If you can put mapping information in one of those places that could be used to identify the proper template based upon the data from the source system, your iPaaS or web service could perform the function of selecting the template before creating the project in AW, and bypassing the need for a workflow rule.

Another approach would be to NOT have the integration/API calls generate the project, but instead have it create some other record to temporarily store the data in AW, and also have the creation of that record trigger a workflow rule that creates the project. In this way, the workflow rule could specify the template to be used.

Thanks Drew, 

My initial thought was creating a Request and then handling it using a workflow but that was not a desirable path. I provided the templates and criteria for the templates to be used as part of the creation of the projects by the API. 

Thanks for the feedback!