Workflow Task
A Workflow Task in Salesforce is one of the four automated actions a Workflow Rule can fire when its trigger criteria are met.
Definition
A Workflow Task in Salesforce is one of the four automated actions a Workflow Rule can fire when its trigger criteria are met. The action creates a Task record (a Salesforce activity) and assigns it to a specified user, role, or record owner, with a configurable subject, status, priority, and due date. Workflow Tasks were the standard way to drive follow-up reminders, action items, and ownership handoffs from rule-based automation for over a decade.
In 2026, Workflow Tasks are part of a deprecated automation toolkit. Salesforce announced the retirement of Workflow Rules and Process Builder in favor of Flow as the single declarative automation platform. New automation should use Flow with a Create Records element to write a Task record. Existing Workflow Tasks continue to fire, but Salesforce has published a migration timeline and a Migrate to Flow tool to help orgs convert them before the end-of-support date.
Workflow Tasks in a Flow-first world: how they work, what replaces them
How a Workflow Task fires from a Workflow Rule
Workflow Rules sit on a single object and define trigger criteria (Field Updated, Record Created, Record Created or Edited, formula evaluates to true). When the trigger fires, the rule executes its associated workflow actions, which can include up to ten actions of any combination: Field Update, Email Alert, Outbound Message, and Workflow Task. The Workflow Task action references a Task template that defines the assigned user (or role or record owner), the Subject, Status, Priority, and Due Date offset (a number of days relative to a chosen date field). When the rule fires, the platform creates a new Task record with values from the template and links it to the source record through the WhatId field.
Configuration: assignee, due date, and template fields
Each Workflow Task template carries five required fields. Assigned To is either a specific User, a Role, the Record Owner, the Manager of the Record Owner, or a User defined by formula. Subject is the visible Task name on the activity timeline (often a short instruction like Follow up with customer). Status is the initial Task status, typically Not Started. Priority is High, Normal, or Low. Due Date is calculated from a chosen date field on the source record plus or minus a number of days. The template can also pre-populate the Comments field with longer instruction text. Once saved, the template is available to any Workflow Rule on the same object that wants to fire it.
Workflow Tasks versus Flow-created Tasks
Flow can create a Task record through a Create Records element, and the resulting Task is identical to one created by a Workflow Task action; the platform stores both in the same Task object. The differences are in the authoring tool and the routing flexibility. Workflow Tasks are limited to the five assignee options listed above and a single Task per rule action. Flow can assign Tasks to any User reference (a lookup on the source record, a query result, a complex calculation), can create multiple Tasks in one transaction, and can route Tasks through downstream branches based on record state. For any new requirement, Flow is the right tool. Workflow Tasks remain only for legacy rules that have not been migrated yet.
The Workflow Rules retirement and migration timeline
Salesforce announced in 2023 that Workflow Rules and Process Builder are scheduled for retirement. Existing Workflow Rules continue to fire, and Salesforce has not set a hard end-of-support date that removes them from the platform, but no new investment goes into either tool. The recommended path is to migrate every Workflow Rule (and every Process Builder) to Flow using the Migrate to Flow tool in Setup. The tool reads a Workflow Rule, generates an equivalent Flow, and lets the admin review and activate the Flow. Workflow Tasks specifically are converted to Create Records elements that build a Task with the same template values. After validation, the original Workflow Rule can be deactivated. Plan a migration project for any org with significant Workflow Rule volume.
Common patterns Workflow Tasks served and where they go in Flow
Three patterns dominated Workflow Task usage. First, follow-up reminders: when a record reaches a stage, create a Task for the owner to follow up in N days. In Flow, this is a Create Records element with a Due Date calculated as today plus N days. Second, escalation handoffs: when a Case sits unassigned for too long, create a Task for the manager. In Flow, this is a Scheduled Path on a record-triggered Flow with a Create Records element. Third, batch action items from a rule criterion: when a record matches a condition, create a Task for the assigned team. In Flow, this is a Create Records element with a Get Records lookup to find the right assignee. Each pattern translates cleanly; the Flow version is more flexible than the Workflow Task version.
Debugging Workflow Tasks and what breaks at migration time
Workflow Tasks have a small surface, but they break in predictable ways. The assignee can become inactive (a user leaves the company), and the Task creation either fails or assigns to a fallback. The Due Date can land on a weekend, which means the assignee may not see it on Monday morning. The Task comment can exceed the field length and silently truncate. The source record may have been deleted between the rule firing and the Task creation, which kills the link to the parent record. At migration time, these edge cases show up in the converted Flow because Flow makes them explicit decisions rather than implicit defaults. This is a good thing: the Flow forces the admin to design the behavior rather than inherit the Workflow Rule defaults.
Migrating Workflow Tasks to Flow
In 2026, the operational task around Workflow Tasks is migration, not creation. New automation should use Flow from the start; existing Workflow Tasks should be migrated to Flow on a schedule. The Migrate to Flow tool in Setup automates most of the work, but the converted Flows still need review, testing, and activation before the original Workflow Rule can be deactivated. This guide covers the migration routine end to end, since that is what every Salesforce admin running an established org needs to know.
- Inventory existing Workflow Tasks
From Setup, open Workflow Rules and list every active rule. For each rule, note the object, the trigger criteria, the actions (including any Workflow Tasks), and the assignee, subject, and due-date logic on each Task. Export the inventory to a spreadsheet for the migration tracker. Group rules by object and by complexity; simple single-task rules can be migrated in bulk, while multi-action rules with field updates and tasks need individual review. The inventory is the source of truth for the migration scope; do not start until it is complete.
- Run the Migrate to Flow tool for each rule
From Setup, search Migrate to Flow. Select a Workflow Rule from the list and click Migrate. The tool generates an equivalent record-triggered Flow with one Decision element per rule criterion and one Create Records (or other action) element per Workflow action. Review the generated Flow carefully. The tool is conservative and may not pick the optimal Flow design; rename elements for clarity, consolidate redundant Decision branches, and confirm the Task template fields map to the right Flow variables. Save the Flow as a draft until testing is complete.
- Test the converted Flow in a sandbox
Refresh a sandbox with the production configuration, deploy the draft Flow, and trigger it manually with representative source records. Confirm Tasks are created with the right assignee, subject, status, priority, and due date. Compare the output to what the original Workflow Rule produces in the same scenario; the two should be functionally identical. Add unit tests if the Flow has Apex action calls. Capture any divergence in a defect tracker and fix the Flow before activating in production. Skipping this step is the most common cause of post-migration support tickets.
- Activate the Flow, deactivate the Workflow Rule, and monitor
In production, activate the new Flow. Watch for the first few Tasks it creates and confirm they look right. Once you are confident (typically after a few days of clean operation), deactivate the original Workflow Rule. Do not delete the Workflow Rule immediately; keep it inactive for 30 days as a rollback option. After 30 days of clean Flow operation, delete the Workflow Rule and remove it from your migration tracker. Document the migration in the org automation registry so future admins know which Flow replaced which legacy rule.
- Workflow Tasks fire even when the original assignee is inactive. The Task creation may fall back to a default user or fail silently. Audit your active assignees on Workflow Tasks before migration.
- The Migrate to Flow tool is conservative. It generates a functionally correct Flow but not always an optimal one. Review the generated Flow and refactor for clarity before promoting to production.
- Workflow Rules will be retired. Salesforce has not given a hard date, but new investment is on Flow only. Treat any new automation requirement as Flow work; do not add new Workflow Tasks.
- Activating the Flow without deactivating the Workflow Rule creates duplicate Tasks. The conversion period needs careful sequencing: activate Flow, validate, then deactivate the Workflow Rule, never both active at once.
- Workflow Task templates do not version. Editing the template in production changes behavior for every rule that uses it. Migrate to Flow per rule, not per template, to maintain isolation.
Trust & references
Straight from the source - Salesforce's reference material on Workflow Task.
- Workflow Rules OverviewSalesforce Help
- Migrate to FlowSalesforce Help
- Flow OverviewSalesforce Help
Hands-on resources to go deeper on Workflow Task.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Workflow Task?
Q2. What replaces them?
Q3. Who can tasks be assigned to?
Discussion
Loading discussion…