Workfront Web vs API - attach template to a project | Community
Skip to main content
P
Pavlo
Level 2
February 27, 2026
Solved

Workfront Web vs API - attach template to a project

  • February 27, 2026
  • 2 replies
  • 10 views

Hi,

I’m trying to attach a template to the project, and when I’m doing it via Web interface it attaches template and all templates tasks. But when I’m using API, it assigns a template but doesn’t create tasks from the template.

 

.../attask/api/v21.0/proj/{PROJECT_ID}/attachTemplate

 

body - 
 

{

"templateID": "***"

}

 

I’ve tried a lot of variations for body, with "options": [], without, with "excludeTemplateTaskIDs": [] and without. Nothing helped. 

Is it possible to attach a template to the project and trigger template’s task creation?

Thank you.

Best answer by Pavlo

I’ve found that if I use
/proj/{PROJ_ID}?action=attachTemplate
body - 

{

"templateID": "{templateID}",

"options": [],

"excludeTemplateTaskIDs": []

}

it will asign the template and will create tasks.

 

2 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
March 2, 2026

​@Doug_Den_Hoed_AtAppStore ​@KIMBERLYREA ​@Daniel_Clarke ​@anupampat Would appreciate your perspective if you have handled something similar before.

Kautuk Sahni
P
PavloAuthorAccepted solution
Level 2
March 2, 2026

I’ve found that if I use
/proj/{PROJ_ID}?action=attachTemplate
body - 

{

"templateID": "{templateID}",

"options": [],

"excludeTemplateTaskIDs": []

}

it will asign the template and will create tasks.

 

    Terms & ConditionsAccessibility statement

    Loading footer...