👂 Feedback needed: scripts in automations that shouldn't be scripts

[mdubakov]

Try new Script AI Assistant in the latest release

October 3, 2024 / Quick filters on relation and embedded views, Clean email body, Automations Script AI Assistant, and more

In today’s release we added several improvements to recently released features and made a first step to AI Automations assistant. This is the recent feedback we’ve got from one our customer and it generated a lot of dopamine for our team, just want to share it with you as well. I’m deeply impressed by the technical design of Fibery — you guys seem to make excellent trade-offs and design decisions, preferring to add more powerful & simple higher-level abstractions, rather than special-case feat…

[Renato_Carvalho]

+1 here:

Webhook Action in Automations

I hope this becomes an automation/button action. It would increase the usability/flexibility of Fibery for low-code users if there was a UI that builds an API call similar to Zapier and Make.

[gb_carbone]

When a new Time Log is created:

• Set the state of the currently opened time logs to closed
• Set the end date/time of those time logs to now
• Only do that for the time logs owned by the person who triggered the workflow (who created the new time log)

[RonMakesSystems]

@interr0bangr

• There’s no way to loop through multiple matching entities in automation without a script. Any attempt to do so with formula fields gets flagged as an infinite loop, even with very clear and restrictive filters in place.

+1

When templating, it would be great to have the ability to create a new entity for each relation the other entity has. And bind fields based on each of the other relation.

Updating is already possible in bulk, but creating is not yet.

[gb_carbone]

IIRC, I would have to create a script here just to access step 2 results - or are step 2 results accessible at all otherwise?

If we do need to create a script here to access those results, well this is a good case for this thread. Otherwise, would love to know how! And if step 2 results are not accessible even in a script, well that is a bigger issue.

[helloitse]

TIL that there is no way to add a value to a multi-select field of a linked entity - only to clear the old values entirely and set a new one.
To add a value without losing the existing ones, I’ll need to use a script - not cool.

[gomocoop]

Same for collections!

I wish I was able to add entities to a relation field without erasing the ones that are already there.

[Chr1sG]

@gomocoop

I wish I was able to add entities to a relation field without erasing the ones that are already there.

You can. The Link action will link an existing entity. The Add action will add a new entity.
Neither will affect existing linked entities.

[RonMakesSystems]

Only (structured) related entities can be created in automations. This reduces flexibility. I want to create a tasks on trigger, and simply mention the triggering entity in the description. This may be fixed with the new “Global database” coming soon, but either way, it’s something that is possible via script but not via no-code automations.

I’ll add one more I just found out. If there IS a structured relation, but it is autolinked, it is not possible to create a new entity of that type. Yes, it won’t be linked directly, but the names that are set to it will make it auto-linked. Unfortunate.

[Eren_Turgut]

Agree, here is an example:
I have DBs [Outgoing Invoice] and [Invoice Line Items].
I wanted to create a button to create a new invoice based on the chosen one, so it should also create line items (duplicating loses the line items).

That requires looping through the line items and create a new one for each existing one.
It’s possible without scripting too but with unnecessarily complicated workarounds, unless I’m missing something.