Our use case:
A number of our Wrike Integrate recipes are intended to trigger only for new tasks, not when existing tasks are updated. Because Wrike's API & webhooks don't distinguish between new/updated tasks, we need a way to identify when a task is newly created vs. when an existing task has been updated.
We use a Wrike custom text field (available on the Business & Enterprise plans) named Wrike Integrate to identyify new vs. updated tasks. Our Wrike Integrate recipes are configured to trigger only when this custom field is empty/blank, and the first step of each recipe updates the task to add text to this field, which prevents the recipe from firing again on the same task regardless of how many times that task is updated.
To bulletproof this solution and prevent normal Wrike users from manually updating the value in this custom field, the field is shared only with our Wrike Admins.
Example Wrike Integrate recipe:
Iniciar sesión para dejar un comentario.