I would like to remove hubspot tasks associated to a deal contact when the deal reaches a certage stage of the pipeline.
For example, when a deal is started it creates a follow up task (though Zapier) when the deal moves to won/lost stage I would like to remove(ideally) or complete all tasks associated to the deal.
Trigger off the deal stage changing then maybe add a filter step for only the stages you want to allow through. You may need to grab the interal id of stages for the filter step like this:
Then, you'll use the find associations step. Notice you'll need to manually type in 'task'.
You mentioned potentially having multiple tasks, so you'll likely want to create a loop from text. This setup will still handle situations where only one task is associated with the deal. You also might want to have a filter step before the loop to ensure a task is actually associated with the deal.
Then, you'll use an API request step to complete the tasks.
If you want to archive the task, set it up like this.
Please let me know if anything is unclear from the screenshots.
@janek Thanks for the tag! I am pretty aligned with RSchweighart's solution here, The only thing I can think off is the governance & adoption part of this and ask questions:
What types of tasks are left open when a deal is closed?
Why are they open?
This will open up an opportunity with Reps to discuss and maybe remove / consolidate some tasks
The loop step looks good. To confirm, does your step 5 map to the output from step 4 like this?
Step 3 will only work if there's one deal being passed, so the find association step is finding all the tasks associated with the deal you have mapped in step 3, which is actually the deal that triggers the zap.
Hope that gets you there. Let me know if there are any more questions.
That's my bad, the error is due to incorrect mapping of step 4 in step 5. You will want to select the value 'Task' from step 4 in your case to map in step 5. It will be the first task id in the two you have listed. When the zap runs, it will loop through each task if there are multiple. I have mine labelled 'Tasks' but it looks like yours will be 'Task'.
@janek Thanks for the tag! I am pretty aligned with RSchweighart's solution here, The only thing I can think off is the governance & adoption part of this and ask questions:
What types of tasks are left open when a deal is closed?
Why are they open?
This will open up an opportunity with Reps to discuss and maybe remove / consolidate some tasks
Trigger off the deal stage changing then maybe add a filter step for only the stages you want to allow through. You may need to grab the interal id of stages for the filter step like this:
Then, you'll use the find associations step. Notice you'll need to manually type in 'task'.
You mentioned potentially having multiple tasks, so you'll likely want to create a loop from text. This setup will still handle situations where only one task is associated with the deal. You also might want to have a filter step before the loop to ensure a task is actually associated with the deal.
Then, you'll use an API request step to complete the tasks.
If you want to archive the task, set it up like this.
Please let me know if anything is unclear from the screenshots.
Firstly, a massive thank you to you and the others that replied. I can't believe there is a solution.
I found if there are more than one task assosiated to the deal, I get the following error. Do you know how I resolve it?
Another question, you mentioned a filter to check whether the task is linked to the correct deal (we very often have multiple deals, in different stages linked to the same contact), how do I set that up?
1. I have it set up as recommended and it works perfectly if there is only one task associated to the deal but if there are 2 or more tasks associated it gives an error. How do I solve that issue?
2. My filter question was in relation to ensuring it is removing tasks for that deal ONLY (as there are often multiple deals open for one customer), do I need to use a filter or will the current setup solve that issue?
The loop step looks good. To confirm, does your step 5 map to the output from step 4 like this?
Step 3 will only work if there's one deal being passed, so the find association step is finding all the tasks associated with the deal you have mapped in step 3, which is actually the deal that triggers the zap.
Hope that gets you there. Let me know if there are any more questions.
That's my bad, the error is due to incorrect mapping of step 4 in step 5. You will want to select the value 'Task' from step 4 in your case to map in step 5. It will be the first task id in the two you have listed. When the zap runs, it will loop through each task if there are multiple. I have mine labelled 'Tasks' but it looks like yours will be 'Task'.