Hi everyone,
I’m Dheeraj Sudan from the UK. I’m a software developer and also run a business with my wife Meenu Hinduja. I’m trying to Automating status updates across multiple connected databases in Fibery has become challenging. How can I trigger automatic status changes in related entities when one record is updated, without creating circular automations or performance issues? Are there best practices for structuring these workflows?
Thanks
Meenu Hinduja Dheeraj Sudan
If you can provide more concrete details of what you’re trying to achieve, we can probably come up with some ideas.
What are the relevant dbs/fields/relations and what do you want to happen?
Hey Dheeraj, You can’t do that to multiple records with built-in automation rules but you can use scripting for that. You can also use n8n or make instead.
Well, it depends.
For example, if you have a Project linked to several Tasks, you could add a lookup to get the Project status in the Task db, and then use an automation (in the Task db) which triggers when this lookup field value changes, and updates the Task status as an action.
I did mean in one go so you don’t get lost 6 months after about what’s actually happening here 
The method I mentioned first has the benefit of allowing you to fine- tune which Tasks get updated e.g. using filters to take into account other Task field values and/or previous state value.
But if you want it really simple, just use an automation in the Project db which triggers when its status changes and updates all linked Tasks, no matter what.