Trigger Workflow on Record Deletion

Smart CRM & Sales Hub CRM
1

Is there a way to trigger a workflow once a custom object record is deleted?

As far as I know, there is no possibility to enroll the same object-type, as this record is now deleted and cant be subject of a workflow anymore.

Is it possible however, that another object is enrolled once a record is deleted?

I was thinking about creating a workaround with a list, where the trigger is the object leaving the list (which will happen when deleting it), however, I think this is not possible.

Is there another way to start a workflow everytime a custom object record is deleted?

Thanks in advance.

2

Hi @maulpaurer,

The short answer is no, this is unfortunately not possible - at least not without custom development based on the HubSpot API or third party solutions based on it.

The long answer, including an attempt at a workaround is still a “no (not reliably)”. It shows the limitations but could still serve as a workaround.

Let’s assume you have object A and B. Object B is the one being deleted and the one you’d like to be notified about.

  1. Create a custom calculation (rollup) property on object A to count how many records of B are associated (‘Number of associated Bs’)
  2. Create a custom number property ‘Number of associated Bs (delayed by 10 minutes)’
  3. Create a custom object A workflow that re-enrolls records when ‘Number of associated Bs is known’, then delays for 10 minutes, then copies the value into ‘Number of associated Bs (delayed by 10 minutes)’
  4. Create a custom calculation property (custom equation), ‘Change in number of associated Bs’ that outputs ‘Number decreased’ when ‘Number of associated Bs’ minus ‘Number of associated Bs (delayed by 10 minutes)’ is smaller than 0 and ‘Number increased’ when ‘Number of associated Bs’ minus ‘Number of associated Bs (delayed by 10 minutes)’ is greater than 0
  5. Create a custom object A workflow that sends you a notification when ‘Change in number of associated Bs’ is ‘Number decreased’

The big caveat is that someone might simply have removed an association and not deleted a record.

Best regards!