Wrike Integrate - Example recipe to copy the value from a project-level custom field to all new tasks within that project
Prerequisites
- Wrike plan that includes custom fields
- Wrike Integrate (paid add-on)
- Wrike custom text field named Wrike Integrate (available to tasks, used to distinguish new tasks vs. updated tasks)
- Wrike custom field to be copied from project to tasks (available to both projects and tasks, example recipe uses a text field named Client)
When creating custom fields used in Wrike Integrate recipes, we share some of these fields only with our Wrike Admins as appropriate, so other users can't see or change the value in these fields. Keep in mind that the user linked to your Wrike Connector in Wrike Integrate will also need access to these fields in order to see/update them.
Recipe results
This recipe will trigger only for new tasks, and will drill upwards up to 4 levels looking for the task's project (allowing for up to 3 levels of nested sub-folders within each project). Any value found in the project-level Client custom field will be automatically copied to the task-level Client custom field.
Important caveats
-
Because this recipe triggers only for new tasks, it will work only if you create the task within a project. If you create tasks then move them into a project, this recipe will not populate those tasks' custom fields.
-
This example recipe only traverses 4 levels of parent folders to look for the task's project. If you use more than 3 levels of nested sub-folders in your projects, you will need to modify this recipe to handle your desired number of nested sub-folders.
-
This recipe doesn't update the custom field value on existing tasks if the project's custom field value changes. That's possible, but would require a different approach in a separate recipe.
Hi Laura - This is amazing and very helpful. I appreciate your work and documentation of the steps. I was able to get it to work after changing the variable names quickly. Below are my two use cases and associated error on the second one.
First Use Case: Simple task addition
Test Structure - Space > Folder > Folder > Project (with custom field) > Task
Status - Success! The custom field was copied as expected. :D
Second Use Case: Sub-task addition
Test Structure - Space > Folder > Folder > Project (with custom field) > Task > Sub Task
Status - Error - 400 Bad Request: {"errorDescription":"Operation is not allowed for logical folder","error":"invalid_request"}
It seems like the "Wrike - Get folder by id" action can't handle sub-tasks.
https://docs.workato.com/connectors/wrike/get-folder-by-id-action.html
Have you encountered this?
Thanks!
Will this work if you are utlizing a Blueprint to create a new project with tasks?
Hi Reiner Critides, I'm sorry for not getting back to you sooner! Have you been able to find the answer to your question? I can raise a ticket to our Support on your behalf if needed, just let me know 😊
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
I would also like to use Blueprints to create new projects via wrike integrate/workato. It would be great if you could post instructions here.
thanks
Hi Ralph Joedicke, thank you for your interest in Wrike Integrate. I noticed that you reached out to the Wrike Support team in regards to a similar query via email, and my colleagues assisted you. However, I believe the instructions could be helpful for other Community members, so I am additionally posting them here.
Indeed, in-built Wrike Integrate actions don't contain any step that allows one to create an item from the existing Blueprint. To launch a new project you'll need to use 'Custom action' step of the Wrike application that allows you to utilize additional capabilities of Wrike API. Here's the page where you can find all the necessary information about launching Blueprints via Custom Action: https://developers.wrike.com/api/v4/blueprints/#folder-blueprint-launch-async (step 'Folder Blueprint Launch Async'). To get an ID of your Blueprint, you can call the GET/folder_blueprints endpoint. For ease of use, you can retrieve the ID in the Postman application - here are the instructions on its installation and setup: https://help.wrike.com/hc/en-us/community/posts/115000282125-Beginners-Guide-Get-Data-From-Wrike-s-API-Without-Coding-via-Postman
Please note that the creation of Blueprint might take some time - we advise adding the 'Scheduler' > 'Wait for time interval' step to make sure that the necessary item gets created and then retrieve the Blueprint's status via GET/folder_blueprints endpoint.
Hope it helps. If any additional questions come up, please get back to us on the ticket☺️
The link for the recipe is no longer valid. It was a perfect solution for my issue.
The link for the recipe is no longer valid. It was a perfect solution for my issue.
Hey Rob Sweeney, welcome to the Community 👋 I can see it was posted by Laura 3+ years ago, but I hope the post is still helpful. Let me know if you'd like to talk to our Wrike Integrate experts form the Support team 🙂
Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover
Lisa Wrike Team member Become a Wrike expert with Wrike Discover
Sorry all, I was away from Wrike during COVID due to job changes, but I'm back and planning to edit my older Wrike Integrate posts to fix the now-broken recipe links. Workato changed the way they support shared recipes, so my older posts with links no longer work correctly. I'll do my best to update them.
Rob Sweeney For this one, here's the recipe from several years ago that I created with that post. The user interface for Workato has changed a bit in the years since, as have some other features, so your mileage may vary until I get a chance to rewrite this recipe in current environment.
https://app.workato.com/recipes/1102960?st=e5026de2b1ce6a72ba341314f298b77931ea8b97ba46cd20e3b236e5342c2736
Oh my, thank you so much!
Seems kind of unreasonable that we need to pay for Wrike integrate and use a third party service to do something that we should be able to do in Wrike natively.