Wrike Integrate - Example recipe to copy the value from a project-level custom field to all new tasks within that project

Prerequisites

  • Wrike Business or Wrike Enterprise (in order to use 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

  1. 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.

  2. 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.

  3. 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.

Wrike Integrate recipe example

https://www.workato.com/recipes/1102960

4
5 Kommentare
Spot On Innovative Approach Stellar Advice

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!


0
Spot On Innovative Approach Stellar Advice

Will this work if you are utlizing a Blueprint to create a new project with tasks?

0
Spot On Innovative Approach Stellar Advice

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

0
Spot On Innovative Approach Stellar Advice

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

0
Spot On Innovative Approach Stellar Advice

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☺️

Lisa K. Community Team at Wrike Wrike Product Manager Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

Lisa K. Wrike Team member Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

0

Folllowing List for Post: Wrike Integrate - Example recipe to copy the value from a project-level custom field to all new tasks within that project
[this list is visible for admins and agents only]

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