Project ID comes back as taskId

When you change the status of a project, the webhook payload includes its ID as taskId instead of the more intuitive folderId/projectId - see below for an example payload.

Despite the counter-intuitiveness of the naming convention - is this something safe to rely upon? (meaning, it is stable enough to build automation on top of?)

Thanks!

 

{
"status": "Production",
"taskId": "IEAEEHCOI4UTOY3X",
"eventType": "ProjectStatusChanged",
"oldStatus": "Backlog",
"webhookId": "IEAEEHCOJAAAZWIU",
"eventAuthorId": "KUAJKXWU",
"customStatusId": "IEAEEHCOJMBX722Q",
"lastUpdatedDate": "2021-05-19T20:03:40Z",
"oldCustomStatusId": "IEAEEHCOJMAAAAAA",
}

0
1 comment
Spot On Innovative Approach Stellar Advice
Avatar

Hello Cristian Rasch, welcome to the Community 👋🏻

My colleagues from the Support team are in touch with you via email, please let me know if I can help with anything else 🙋🏻‍♀️ 

Cansu Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Cansu Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink

Folllowing List for Post: Project ID comes back as taskId
[this list is visible for admins and agents only]

Top
Didn’t find what you were looking for? Write new post