# Rule to trigger on "Entity Deleted" **URL:** \ **Category:** Ideas & Features\ **Tags:** automations\ **Created:** [June 16, 2022, 5:03pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962 "2022-06-16T17:03:08Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 16, 2022, 5:03pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/1 "2022-06-16T17:03:08Z")
It would be useful to have a “Destructor” Rule that can trigger when an entity is about to be deleted. E.g., If the entity has linked Documents, I might want to move them elsewhere so they don’t become orphaned. **Related:** [Run rules on delete event](https://community.fibery.io/t/run-rules-on-delete-event/2013) ---
**Author:** ![nvee](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nvee/32/6860_2.png) [@nvee](https://community.fibery.io/u/nvee)\ **Post date:** [July 20, 2023, 1:44pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/2 "2023-07-20T13:44:01Z")
We also need this functionality. We have a use case where we would like to delete a Google Calendar item when an entity is deleted, but currently I can’t find a way to do this. I also noticed that the webhook doesn’t feed any data about the entity when deleted either, so webhooks via [make.com](http://make.com) is not an option either. ---
**Author:** ![Jordan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jordan/32/9845_2.png) [@Jordan](https://community.fibery.io/u/Jordan)\ **Post date:** [August 27, 2024, 4:10am UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/3 "2024-08-27T04:10:55Z")
@Chr1sG Would the back-end on this be messy? Is there a way to do this using ‘Entry unlinked’ or ‘Updated’? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 27, 2024, 7:05am UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/4 "2024-08-27T07:05:08Z")
> [@Jordan](#): > > Is there a way to do this using ‘Entry unlinked’ or ‘Updated’? Certainly, if entity A is linked to entity B, then deleting entity A can be detected with an automation in the B database (using an unlinked/updated trigger). However, there are challenges with this method - there is no way to detect something being deleted if it is not linked to something else - the actions available are limited to actions for entity B - the values of entity A prior to deletion are not accessible - you can get ‘caught out’ with false triggers, e.g. if someone decides that B should be linked to C instead of being linked to A, this will manifest as A being unlinked, even though A has not actually been deleted. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [August 27, 2024, 3:14pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/5 "2024-08-27T15:14:10Z")
The only way I can figure to accomplish this is to never actually _delete_ such entities directly, but instead create an “Action” field that you can use as a trigger. When this field is set to “DELETE” for example, this would trigger the automation to do all the interesting pre-deletion things and then actually delete the entity. But there is no way way to prevent entities from being deleted in the normal ways (manually or via automations), so this approach depends on everyone following the special “delete procedure” correctly for this DB. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [August 27, 2024, 3:27pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/6 "2024-08-27T15:27:07Z")
> [@Matt\_Blais](#): > > But there is no way way to prevent entities from being deleted in the normal ways (manually or via automations), so this approach depends on everyone following the special “delete procedure” correctly for this DB. The delete capability can actually be separated out from other capabilities when using custom access templates for sharing an entity, but this doesn’t help in the case of a database that has been shared. ---
**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\ **Post date:** [December 4, 2025, 9:20pm UTC](https://community.fibery.io/t/rule-to-trigger-on-entity-deleted/2962/7 "2025-12-04T21:20:43Z")
With automations getting some love at the moment, this would also be a lovely thing to add!