I would like to be able to sort automations into groups, and move them between groups and alter their position in the list.
+1
We’ve tried to create an internal naming convention for automations but it becomes unwieldy very quickly.
1 Like
I have 0 votes left since 2022 so take my
+1
I’ve never been able to dive deep enough into Coda automation dependency, and for several reasons.
Bound to a Document
This one really troubled me because I tend to see automation as adjacent to workflows, and workflows often traverse multiple documents. This has always been a puzzling disconnect.
Observability
It doesn’t exist. The hidden side of automation is the obscurity that comes from this distributed form of automation entities. It makes it difficult to see what’s happening across all documents and all automated processes.
Orchestration
There’s no central place to view or manage automation. Imagine you have two automation processes - one that performs advanced steps and another that does basic, mission-critical stuff. You may need to assess an issue quickly and switch between these automation processes periodically.
It Gets Worse
Coda is not well-positioned to be an agentic orchestrator either. What if Grammary’s future agent features are doc-based? How will agents and automations co-exist?
Maybe the answer is Grammarly itself. It might be ideal if automatons were defined within the pervasiveness of Grammarly such that they could perform in contextual settings.
1 Like