Is it possible for an Automation where updating one Deal, triggers an action to update another Deal?
Hi everyone,
We are currently using an automation where we create a duplicate (Onboarding) Deal for an Onboarding Pipeline whenever a Deal is closed "Won." In our business, once we "win" a Deal, it takes 3 months or so to onboard the client and involves several key steps.
At various stages of the Onboarding process/pipeline, we enter information (for example: "Installation Date") in the custom fields of the duplicated (Onboarding) deal. These fields are necessary as we also need to create other automations off of these custom fields (for example, sending an email notification to the client for an upcoming contract renewal) off of the original deal.
As the Original Deal and the Duplicated (Onboarding) Deal are separate, we are trying to create an automation that updates custom fields in the "Original" deal, when the same custom fields in the duplicated (Onboarding) deal are updated. We haven't discovered how, or a work around, and are hoping someone has run into the same challange and discovered a solution.
Automation Request: Updating one Deal, triggers an action to update another Deal.
Trigger: Updating custom field in a (duplicated) Deal
Condition: Custom field (Installation Date) "has changed"
Action: Update "Custom field (Installation Date)" in Original Deal with the same information entered into the same "Custom field (Installation Date)" of the Duplicated Onboarding deal. (re: in this case 'date')
Thanks for any and all suggestions!
Answers
-
If you save the original deal ID in the duplicated deal, this may be possible.
A better thing to do would be to store such data at the person or org level.
0 -
Thank you, Amit. Much appreciate your quick response. We have a link to the original deal in the duplicated deal … but haven't found a way to make it work.
Great suggestion on storing the data at the Person and/or Org level, unfortunately our workflows won't allow this. Information needed is per Deal, which is specific to an address, and People and Orgs can have 50+ Deals … so it needs to captured in the Deal.
0 -
This can be easily implemented using a Pipedrive webhook event (deal update) and API, but it’s likely not possible with Pipedrive automations alone.
This is because in general Pipedrive automations are limited to the hierarchy of linked entities (e.g., a lead/deal and its associated people or organizations) and don’t work across entities.
If you’d like a quick demo of how this webhook/API solution would work, feel free to email me (it's free). Thanks!
0
