+ Start a Discussion

Workflow , Flow & Process Builder


I am new to Salesforce and often get confused between: Worflow , Flow and Process builder? The line seems blurry when trying to differentiate between them.

Would anyone be able to describe the difference? 

Thank you.
ajay rawat 14ajay rawat 14
Hi Gabz
         Basically process builder is advance version of workflow.
1)  Process builder is mainly used to avoid use of multiple workflow because one workflow can have only one condition and criteria action but one   process builder can have multiple if/else condition.
2) Process builder allow you to update child record where as worflow doesnot.
3) Process builder can call your apex code so it can send email alerts, submit records for approvals using apex code whereas workflow cannot call apex but  can send email/ outbound alert only  without code.

There are much more difference Kindly refer below links

Ajay Rawat
Rupali PophaliyaRupali Pophaliya

Workflow enables you to set up workflow rules. A workflow rule identifies what kinds of record changes or additions trigger specified workflow actions, such as sending email alerts and updating record fields.

Workflow rules and actions are associated with a specific object (and can cross objects only to update fields on a related master record).

Visual Workflow:

Visual Workflow enables you to create flows, which are triggered by users rather than events. Unlike Workflow, which always executes rules and actions behind the scenes, Visual Workflow offers screens for displaying and collecting information from the user running the flow.

Flows aren’t tied to any one object. They can look up, create, update, and delete records for multiple objects.

Process Builder:

The Process Builder’s simple and powerful design allows you to:Create your processes using a convenient layout with point-and-click efficiency.
  • Create your whole process in one place rather than using multiple workflow rules.
  • Create processes by collaborating with different teams in your business.
  • Stop using Apex code to automate simple tasks.


Rupal KumarRupal Kumar
Hi Gabz,

Workflow- are fast, easy, and button-click friendly. The Workflow rule will “trigger” based on a set of criteria at which point the actions will either be immediate or based on a time-based schedule. Workflow rules can do a lot. They can update fields for the object it’s being “triggered” on and in certain circumstances update records for their parent record. Workflow rules can send out emails and create tasks. There’s also the rarely used Outbound message for integration.

One downside to the Workflow Rule is organization. Each set of criteria requires a new workflow rule. This means you’ll have many workflow rules for the same workflow process. For example, you want to have similar but different actions fire based on the stage of the Opportunity. This will require 1 Workflow rule per stage. The only way to organize this is by the naming convention of the rule – which can get messy.

A second downside to workflow rules are from the management perspective. You have no way of knowing what the actions are without “drilling” into each Workflow rule. That can be quickly annoying.

The final downside is the limitation. You are limited in what records you create and update, and you don’t have access to many of new features (chatter) available.

Process Builder- is the new version of Workflow Rules. You can do a lot more different types of actions – including having a Flow from Visual Workflow get called. This gives you a lot of different powers. It’s built on top of Visual Workflow so you have almost all the same power of that tool. A Process can have multiple criteria diamonds – basically the equivalent of nesting multiple Workflow Rules together on one page. You can also see all the actions for each set of criteria that will be called.

One downside of the Process Builder is you currently only have access to the records and fields the running user has. Workflow rules would let you update an “invisible” field to the user. This was great for lots of data validation and controls. With Process Builder (and Visual Workflow) the field must be visible and editable by the user in order for the tool to update the field.

There are some other downsides with the current version. The tool isn’t truly “bulkified” so managing many many records will be problematic. There are also some limits on the number of “criteria diamonds” you can have and the number of active processes per object.

Rupal kumar

Vijay NagarathinamVijay Nagarathinam
Hi Gabz,

The main difference between workflow, process builder and visual workflow is follows
  1. The workflow supports the outbound message but it not support in process builder.
  2. The process builder and visual workflow supports to call the apex  methods.
  3. The process builder and visual workflow support to update parent to child and child to parent, but worklfow supports only the master detail relationship objects.
  4. Process builder support to check more than one conditons in a single builder, but in workflow you need to create more than one for checking different condtions.

Goldy Raj 4Goldy Raj 4
Which statement is true regarding both flow and process builder?

1)are able to be embedded directly on vf page
2)are both server side consideration in order of execution
3)can use apex that implments the process.plugin interface
4) can use apex methods with @invocablemethod annotation

any answer and why?

thanks in advance
Hi please refer below link to get clear idea about workflow Rule with example
Workflow Rule in Salesforce with real time example (http://salessforcehacks.blogspot.com/2019/12/what-is-workflow-rule-in-salesforce.html)