# Automation actions can only create entities they are related to 🙁 **URL:** \ **Category:** Bugs & Issues\ **Tags:** automations\ **Created:** [November 18, 2022, 3:52am UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552 "2022-11-18T03:52:32Z")\ **Posts on this page:** 11\ **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:** [November 18, 2022, 3:52am UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/1 "2022-11-18T03:52:33Z")
An Automation Rule has some Actions to Create a new entity, but it can only create an entity of the Types/DB’s it is related to. **Use case:** I want to create a Rule that triggers when a `Client` entity has its status change to ‘Inactive’, and the action will be to create a new `Task` entity and assign to the Client’s manager. However, my `Client` DB is not related directly to the `Task` DB, so there is no option in the `Client` Rules Actions for “Create a new Task”. I am forced to do it in a script instead. ---
**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:** [November 18, 2022, 8:00am UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/2 "2022-11-18T08:00:10Z")
As a general rule, it’s kinda assumed that if you want to create an entity (e.g Task) based off a trigger on an entity in some other database (e.g. Client) that these types of entity are in some way related (and would therefore have a relationship). Of course, there are exceptions, but it’s interesting to hear the use cases before rolling out the ability for any automation to be able to create entities in every other possible database. FYI I have experienced a similar issue when there is a connection between the dbs, but it is an auto-linked relation 😕 ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [August 19, 2025, 10:47am UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/3 "2025-08-19T10:47:35Z")
I just encountered this situation where creating an entity in an unrelated database would be ideal. The 1st database is used for our recruitment team to manage roles/positions. Then, because of network permissions, an IT admin needs to upload the new/edited position into another system. This IT admin already receives notifications when a position is created or edited. We now want to create a Task for IT, but want to avoid relating Tasks to Positions because we want to minimize notification overload for recruitment personnel (they are Watchers to receive notifications on edits to the entity, but should not be notified of IT tasks becoming related to positions). So, for example, we’d like to do the following: Recruitment creates a position. An automation notifies the relevant IT personnel and creates an IT dept task. So, essentially, we have a situation where the entities are not related in workflows. They’re more-so related just in timing/creation. We want to avoid overbearing notifications whenever possible. The permissions matter might be a complication. It seems to require the user writing the rule to have creator access to both databases. ---
**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 19, 2025, 12:07pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/4 "2025-08-19T12:07:01Z")
> [@Michael\_Ichter](#): > > We now want to create a Task for IT, but want to avoid relating Tasks to Positions because we want to minimize notification overload for recruitment personnel It strikes me that the Tasks are in fact related to the position, but it’s the excessive visibility/notification that should be addressed. Is it possible to limit viewer rights to IT tasks for recruitment people? so they won’t get told about new IT tasks, because they can’t see them … ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [August 19, 2025, 12:15pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/5 "2025-08-19T12:15:44Z")
> [@Chr1sG](#): > > Is it possible to limit viewer rights to IT tasks for recruitment people? Would this limit the notifications that people receive? The one Watch notification setting says “Any event in an entity you are watching”, which I interpret as anything that shows up in the “Activity” log of an entity. I didn’t think this was affected by permissions. Tasks are already restricted to only appear for the users that need to use them. ---
**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 19, 2025, 12:20pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/6 "2025-08-19T12:20:27Z")
I need to double check, but I think that if something you can’t see is linked to something you can see, then you don’t get a notification, since it would be meaningless. ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [August 19, 2025, 12:22pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/7 "2025-08-19T12:22:36Z")
There have been a few times that people showed me in-app notifications that mentioned a restricted entity. But I don’t remember if this is one of those instances that created these types of notifications. ---
**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 19, 2025, 12:23pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/8 "2025-08-19T12:23:16Z")
Haha, I checked, and you do get a notification ☹ ![firefox_Lxy5KA1JfK](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/dcb2c79ccaed0f41691d1af8b40a7c459e5f99ad.gif) Back to the drawing board … ---
**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 19, 2025, 12:24pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/9 "2025-08-19T12:24:02Z")
I’ll ask the product guys if they want to think about this use case. Thanks for bringing it up ---
**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\ **Post date:** [August 19, 2025, 1:00pm UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/10 "2025-08-19T13:00:26Z")
I sometimes misremember these things. I’m happy you found this for the sake of my honor! 😂 But sorry for yall! ---
**Author:** ![rienheuver](https://avatars.discourse-cdn.com/v4/letter/r/278dde/32.png) [@rienheuver](https://community.fibery.io/u/rienheuver)\ **Post date:** [April 13, 2026, 8:23am UTC](https://community.fibery.io/t/automation-actions-can-only-create-entities-they-are-related-to/3552/11 "2026-04-13T08:23:46Z")
I would like to share my use case for something quite similar. I want to create an entity of a linked database, but one that is auto-linking. I have configured the IMAP integration and now want to link all emails to a contact in my CRM. However, sometimes the contact doesn’t exist yet in the CRM but the company they work for does. In such a case I want to creae a new Contact from an automation that detects that the email isn’t linked.