# Update \[Step 1 linked Entity\] without a script

**URL:** <https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668>\
**Category:** Get Help\
**Created:** [September 24, 2025, 12:14pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668 "2025-09-24T12:14:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [September 24, 2025, 12:14pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/1 "2025-09-24T12:14:33Z")

</div>

[UPDATE: the goal is actually to have an easy way to trigger an automation when entities of various databases are linked, without multiplication of automations or complicated scripts.]

A very common automation needed, yet as far as I know, a linked entity cannot be ‘updated’ without affecting existing linked entities, by an automation action without a script.

Maybe one of you has figured out a way?

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/282f64efdd1cf0c17ecafb2c2763c23c4639cecb.png)

---

<div class="post-metadata">

**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:** [September 24, 2025, 12:22pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/2 "2025-09-24T12:22:59Z")

</div>

What do you mean by ‘targeted by an automation action’?  
Do you have a concrete example of what you want to do?

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [September 24, 2025, 12:33pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/3 "2025-09-24T12:33:25Z")

</div>

> [@Chr1sG](#):
>
> What do you mean by ‘targeted by an automation action’?

I mean ‘updated’ without affecting existing linked Tasks (I updated the post above, thanks)  
E.g. When a task is linked to a team, the “owner” user field is set to the team lead.

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [September 24, 2025, 12:50pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/4 "2025-09-24T12:50:23Z")

</div>

There are two workarounds:

If a Task has only one parent Team, then add an automation to the Task database, not in the Team database. In my case, a task can have multiple parent teams however.

The second workaround I used, requires a ‘target entity’ to-one helper field in the Team database.  
In the exaple above, it would be ‘TargetTask’.

1. The step result variable [Step 1 linked Task] then can be used to set the TargetTask,
2. and a second action then updates that TargetTask.

This complicates the schema however, so I rather find a more efficient solution.

---

<div class="post-metadata">

**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Post date:** [September 24, 2025, 1:39pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/5 "2025-09-24T13:39:49Z")

</div>

> [@Yuri\_BC](#):
>
> If a Task has only one parent Team, then add an automation to the Task database, not in the Team database. In my case, a task can have multiple parent teams however.

Sorry this is actually not true. A task can be updated using the [Step 1 linked Team].

My actual goal in this topics is to simplify automations when a task is linked to a number (30+) parent databases without complicated scripts or multiplication of automations. I guess that without polymorphic relations this cannot be simplified. So I may need to update the title of this topic.

---

<div class="post-metadata">

**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:** [September 24, 2025, 2:52pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/6 "2025-09-24T14:52:11Z")

</div>

> [@Yuri\_BC](#):
>
> My actual goal in this topics is to simplify automations when a task is linked to a number (30+) parent databases without complicated scripts or multiplication of automations.

Indeed, because automations are db-specific, if you need an action to execute for the ‘entity linked to…’ events across multiple relations, then you need multiple automations.

---

<div class="post-metadata">

**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:** [September 26, 2025, 1:53pm UTC](https://community.fibery.io/t/update-step-1-linked-entity-without-a-script/9668/7 "2025-09-26T13:53:19Z")

</div>


