Hi Marco,

Thank you for taking the time to raise this great question.

To answer this we need to start mentioning that Action Engine / Process Automation and Actions flows are independent products. The former are our "old" automation products and Action Flows are our "new" automation product which has been integrated into the EMS as part of the Integromat acquisition. In the future, Action Flows will replace Action Engine and Process Automation.

To the differences, Any unattended automation use case (= fully automated use case without human intervention) can and should already be implemented on Action Flows. Please note, unattended means no manual intervention by users.

Please note some other noteworthy capabilities of Action Flows below:

• Customers can implement nearly any automation use case with Action Flows using 10,000+ out-of-the-box actions across 900+ system connectors (cloud, on-prem, and custom)
• Using generic system connectors (e.g. HTTP or SOAP), Action Flows can trigger API-based actions in any (custom) system that provides APIs and for the remainder of legacy systems that do not offer API-based actions, Action Flows support the triggering of RPA bots (Automation Anywhere, Blueprism, UI Path).
• Action Flows can replace nearly all RPA use cases.

Attended automation use cases (= users trigger actions manually) still have to be implemented using Action Engine and Process Automation until further notice as Action Flows currently not supporting that.

I hope this answers your question and clarifies on the surface the difference between the products.

Kind Regards

Levente,

thank you so much for clarifying in this extend. That really helped me to understand how to provide a viable solution to our customers.

Hi! Are there any updates regarding when to use Skills or Action Flows? Can you redirect me on where to find the use cases where Skills are better than AF and visceversa?

Thank you!