Automate processes and orchestrate work with enterprise workflow automation
Salesforce Flow is Salesforce’s low-code automation and orchestration engine that builds record-triggered, scheduled, screen, and platform event flows across the Salesforce Platform; it’s ideal for admins and business analysts automating CRM processes at scale and is included with most Salesforce editions so organizations usually pay via their existing Salesforce license rather than a separate per-user Flow fee.
Salesforce Flow is a low-code Automation & Workflow tool that automates business processes inside the Salesforce Platform. It lets admins and developers create record-triggered flows, screens for guided user interactions, scheduled flows, and platform-event-driven automations without Apex code. The key differentiator is deep native access to Salesforce data, security model, and thousands of prebuilt connectors across the Salesforce ecosystem, making it ideal for sales, service, and operations teams. Flow is bundled into Salesforce editions (Sales Cloud, Service Cloud, Platform) so pricing accessibility depends on your Salesforce license rather than a standalone Flow price.
Salesforce Flow is the declarative automation engine embedded in the Salesforce Platform, first introduced as Flow Builder and evolved from earlier workflow rules and Process Builder. Its origin is within Salesforce’s product suite as the primary automation tool for CRM workflows and enterprise process orchestration. Flow replaces and extends the capabilities of Workflow Rules and Process Builder, positioning itself as the central low-code tool for building record-triggered automations, multi-step business logic, and user-facing screens. The core value proposition is enabling admins and citizen developers to implement complex business logic, approvals, and integrations without writing Apex code while respecting Salesforce security, sharing, and data model natively.
Salesforce Flow offers several concrete features. Record-triggered flows execute when a record is created or updated and can run before-save (fast field updates) or after-save (complex logic), allowing bulk-safe operations across up to platform governor limits such as DML and SOQL per transaction. Screen Flows provide guided UI pages for data collection in Lightning Experience and mobile, supporting components, conditional visibility, and input validation. Scheduled (time-based) flows let you run batch operations on a saved schedule to update or notify large sets of records. Integration capabilities include invoking Apex actions, calling external REST APIs via Named Credentials and external services, and using Platform Events for asynchronous orchestration across systems. Flow also supports subflows, loops, collections, and fault paths for production-ready error handling.
Pricing for Flow is not sold as a separate product; instead Flow is included with Salesforce editions. There is no standalone “Flow” monthly price on Salesforce’s site. The practical cost depends on which Salesforce license you purchase: Sales Cloud, Service Cloud, or Platform licenses start at paid per-user seat pricing that varies by edition (Essentials, Professional, Enterprise, Unlimited). Free use is available within Developer Editions and sandbox orgs for testing, while production orgs require paid Salesforce licenses; certain higher-volume or API-heavy use cases may require Enterprise/Unlimited editions to access advanced features like more flexible integration capabilities and larger limits. For accurate per-user seat pricing you must consult Salesforce’s edition pricing or your Salesforce account rep, as published prices vary by region and contract.
Typical users include Salesforce admins and automation engineers building lead routing, opportunity stage automation, and case assignment flows. A Customer Success Manager might use Flow to automate renewal reminders and update contract records automatically; a Sales Operations Manager could build a record-triggered flow to auto-assign high-value leads and create follow-up tasks, reducing lead response time by measurable minutes. Larger orgs use Flows for quote and order processes, entitlement checks, and multi-step approvals. Compared to competing automation tools like Microsoft Power Automate, Flow’s primary advantage is deeper native access to Salesforce objects, security, and ecosystem-integrated components rather than standalone connectors to external productivity apps.
Three capabilities that set Salesforce Flow apart from its nearest competitors.
Current tiers and what you get at each price point. Verified against the vendor's pricing page.
| Plan | Price | What you get | Best for |
|---|---|---|---|
| Developer Edition | Free | Single developer org, limited data and API calls for testing flows | Developers and admins testing Flows |
| Essentials / Professional (entry) | Starts at region-dependent per-user fees | Basic Flow features included; fewer advanced integration limits | Small teams using CRM automation |
| Enterprise | Starts at region-dependent per-user fees (commonly quoted for Enterprise edition) | Full Flow features, higher API/automation limits, sandbox access | Mid-size orgs needing advanced automation |
| Unlimited / Performance | Custom | Highest limits, priority support, expanded sandbox and integrations | Large enterprises with complex automation needs |
Copy these into Salesforce Flow as-is. Each targets a different high-value workflow.
Role: You are a Salesforce Flow expert designing a Record-Triggered Flow to auto-assign new Lead records. Constraints: use a before-save Record-Triggered Flow only; no Apex; assignment must respect Lead.OwnerId and Queue fallback; include criteria for Industry and LeadSource. Output format: provide a numbered, step-by-step list of Flow elements (Trigger, Get Records if needed, Decision conditions, Assignment element, Update record), with API names, exact field names, sample decision expressions, and sample OwnerId/QueueId placeholder values. Example decision: "If Industry = 'Technology' AND LeadSource = 'Web' then assign to Queue 'Tech-Web-Queue'".
Role: You are a Salesforce Flow consultant building a Scheduled Flow to auto-create renewal tasks for Contracts or Opportunities approaching renewal. Constraints: use a Scheduled-Triggered Flow running daily; only create one task per contract within 90 days of EndDate; set Priority and Reminder; avoid duplicate tasks by checking existing Tasks with Subject 'Renewal Reminder'. Output format: return a concise step list with schedule details, Get Records queries (with filter logic and API field names), Decision criteria, Task Create element fields (Subject, DueDate, Priority, WhoId/WhatId), and sample SOQL-style filters. Example filter: "Contract.EndDate >= TODAY() AND Contract.EndDate <= NEXT_N_DAYS:90".
Role: You are a Salesforce Flow architect designing a Record-Triggered Flow to escalate Cases automatically when SLAs are missed. Constraints: use After-Save Record-Triggered Flow; create an Escalation Task, post to Case Chatter, and send an email alert; use one input variable named 'escalation_level' to map to queue/manager; include idempotency so escalation only happens once. Output format: produce a structured JSON object listing: Trigger conditions, Flow variables, Get Records queries, Decision matrix (conditions -> actions), each Action element (Create Task, Post to Chatter, Send Email Template) with API names and example payloads. Example decision row: "If Case.SLA_Status = 'Breached' AND Case.Priority = 'High' then escalation_level = 2".
Role: You are a Salesforce Flow engineer creating a Scheduled-Triggered Flow that detects likely duplicate Leads and flags them nightly. Constraints: run once daily, limit processing to 200 leads per run, never merge or delete; create a Duplicate_Flag__c checkbox and a Merge_Suggestion__c text note. Output format: provide a clear JSON array of Flow steps including Schedule, Get Records query with dedupe match logic (Email exact match, Company fuzzy match), Loop and Assignment logic with variables (maxRecordsPerRun), Update Records payload, and an example Merge_Suggestion__c text value. Example match logic: "Lead.Email = other.Email OR (LevenshteinScore(Company, other.Company) >= 85)" — describe alternative practical implementation without custom functions.
Role: You are a senior Flow developer designing an end-to-end Quote-to-Cash Flow with conditional approvals, contract creation, and accounting handoff. Multi-step instructions: 1) Define trigger (Quote Accepted status change) and required Get Records (Quote, Opportunity, Product Schedules). 2) Create Decision logic for approval path (value thresholds, discount %, product types). 3) Build Approval Actions (submit for approval, auto-approve for threshold, escalate to manager) and post-approval automation to create Contract, set Contract fields, and notify Finance. Constraints: include audit fields, versioning, and rollback steps if Contract creation fails. Output format: deliver a detailed flow blueprint listing elements (API names), decision rules, sample Approval Process entries, sample email templates, and rollback sequence. Few-shot examples: provide 2 approval rule examples (e.g., Discount > 25% -> Manager+VP approval).
Role: You are an integration-focused Salesforce Flow architect building a Platform-Event-Triggered Flow to forward events to an external system with robust error handling and retry. Multi-step requirements: subscribe to a specific Platform Event, map event fields to outbound payload, call an external named action or Outbound Message, implement exponential backoff retry using a holding custom object and Scheduled Flow reprocessing, and create Error_Log__c records for failures. Constraints: include unique event deduplication, idempotent processing, and SLA for max 3 retries. Output format: provide a step-by-step implementation plan with Flow element names, sample JSON payloads for the outbound call, sample Error_Log__c schema, retry schedule (e.g., 5m/30m/2h), and two few-shot error payload examples showing transient vs permanent errors.
Choose Salesforce Flow over Microsoft Power Automate if you primarily need native Salesforce data access and automation that respects org security and object model.
Head-to-head comparisons between Salesforce Flow and top alternatives: