- 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.
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.
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.
Wrike Integrate recipe example
Iniciar sesión para dejar un comentario.