🧐 Your opinion needed. Automations in Fibery (limitations and opportunities)

[mkervo]

Hello,
The use case I can think of is “improved workflows” as discussed in this thread:

Invitation to users wanting improved workflows

We know that the current workflow implementation is simplistic, and given that there are quite a few topics here that relate to workflows, e.g. …it seems like there are plenty users who would like more sophistication. Without making any promises, I would like to invite users to get in touch if they have specific use cases in mind that cannot currently be achieved in Fibery. This may allow us to develop templates that might be useful, as well as helping us understand what functions/features…

I think a lot of companies have complex workflows which mix automations, processes and manual procedures (tasks). It’s difficult to document the processes well and to mix both worlds (automation with human in the loop).

The most difficult thing is to follow each ongoing process execution. (e.g. a specific customer onboarding, a project lifecycle, a marketing campaign).

The alternatives are:

• Domain locked workflow solutions. A lot of Saas products propose workflow solutions
  • CRMs -e.g. Projects by Pipedrive - Knowledge Base | Pipedrive).
  • Project Managment - Introduction to Jira Workflows | Atlassian
• Powerful workflow engines which lack end-user friendly interfaces
  • (e.g. https://www.windmill.dev/, https://temporal.io/)
• And well.. N8N which is great. But it is not really ‘human in the loop’ friendly

In the end, it’s important for a company to track and improve the efficiency of its processes. It’s also important to quickly onboard on those.

EDIT:
Maybe materializing Workflows, allowing to manage a set of rules and their correlations. Properly handling the “time / transition / contract” aspect of automation.

For an example. A task status can switch to ‘Done’ or ‘Canceled’ only when it is not ‘Draft’. And depending of the “completion” or “cancellation” event. It would trigger other rules, like Creating a ‘Report’ or a ‘Test’. To ‘cancel’ a task, maybe it should be mandatory to fill a ‘form’ with a proper reason.
And you could see all this logic on a proper Workflow page.