Flow Designer vs WorkflowSummaryFlow Designer was introduced in Kingston Release and is active by default. It is a simple way to create automated workflows using natural language - no code! Flow Designer and Workflow can be used at the same time in an instance. Benefits of Flow Designer: Combines multiple platform automation capabilities, configuration, and runtime information so process owners and developers can create, operate, and troubleshoot flows from a single interface.You do not have to script. Natural language descriptions are used to help non-technical users to understand triggers, actions, inputs and outputs.Provides a list of reusable flow components in the base system and helps reduce development cost. Reduces upgrade costs, with upgrade-safe platform logic, replacing complex custom scripts.Develop, share, and reuse your custom flow components with other flow designers.Integrate with external instances and third-party applications with the use of IntegrationHub. Flow Designer vs Workflow: If you are creating something new, start with flow designer. However, there are a few cases you will need to use Workflow, as follows: Instance is running on a release earlier than Kingston.If the process requires complicated or scripted logic, it can be written in a Workflow and called from a flow.Changing logic already developed using Workflows.SLA timer is required.Steps required do not exist yet in Flow Designer and require unsupported protocols. Use Flow Designer when: Instance is running Kingston release or later.Process owners need to use natural language and low code way to automate approvals, task, notifications and record operations.New logic needs to be developed and it has not been created in workflow.Business logic needs to use the library of reusable actions across multiple flows. Related LinksFlow Designer Kingston Release notes Flow Designer Workflow Flow Designer Architecture Flow Designer