Skip to content
SalesforceSkills

Flow Builder

Build record-triggered and screen flows. Describe your business logic and AI generates the flow structure with best practices built in.

Skill Details

Install this skill

Versionv2.1.0AuthorJag ValaiyapathyLicenseMITSections9

Works with

Claude CodeCursorWindsurf

Use this skill when the user needs Flow design or Flow XML work: record-triggered, screen, autolaunched, scheduled, or platform-event Flows, including validation, architecture choices, and safe deployment sequencing.

When This Skill Owns the TaskWorkflow

Use sf-flow when the work involves:

  • .flow-meta.xml files
  • Flow Builder architecture and XML generation
  • record-triggered, screen, scheduled, autolaunched, or platform-event flows
  • Flow-specific bulk safety, fault paths, and subflow orchestration

Delegate elsewhere when the user is:

Required Context to Gather FirstWorkflow

Ask for or infer:

  • flow type
  • trigger object / entry conditions
  • core business goal
  • whether this is new, refactor, or repair
  • target org alias if deployment or validation is needed
  • whether related objects / fields already exist

Recommended Workflow

1. Choose the right automation tool

Before building, confirm Flow is the right answer rather than:

  • formula field
  • validation rule
  • roll-up summary
  • Apex

2. Choose the right Flow type

3. Start from a template

Prefer the provided assets:

  • assets/record-triggered-before-save.xml
  • assets/record-triggered-after-save.xml
  • assets/screen-flow-template.xml
  • assets/autolaunched-flow-template.xml
  • assets/scheduled-flow-template.xml
  • assets/platform-event-flow-template.xml
  • assets/ai-decision-template.xml
  • assets/subflows/

4. Validate against Flow guardrails

Focus on:

  • no DML in loops
  • no Get Records inside loops
  • proper fault paths
  • correct trigger conditions
  • safe subflow composition
  • AI Decision elements not placed inside loops (credit cost per iteration)
  • AI Decision prompts include merge field references for data context

5. Hand off deployment and testing

Use:

High-Signal Rules

Flow architecture

  • before-save for same-record field updates
  • after-save for related records, emails, and callouts
  • do not loop over $Record
  • use subflows when logic becomes wide or repetitive

Bulk safety

  • no DML in loops
  • no Get Records in loops
  • test with 251+ records when bulk behavior matters
  • prefer Transform when the job is shaping data, not per-record branching

Error handling

  • every data-changing path should have fault handling
  • avoid self-referencing fault connectors
  • deploy Flows as Draft first when activation risk is non-trivial

Output FormatTemplate

When finishing, report in this order:

1
Flow type and goal
2
Files created or updated
3
Architecture choices
4
Bulk/error-handling notes
5
Deploy/testing next steps

Suggested shape:

TEXT
Flow: <name>
Type: <flow type>
Files: <paths>
Design: <trigger choice, subflows, key decisions>
Risks: <bulk safety, fault paths, dependencies>
Next step: <dry-run deploy, activate, or test>

Flow Testing (CLI)

Run Flow tests from the command line without VS Code:

Terminal
# Create a flow test definition
sf flow test create --flow-api-name MyFlow --target-org <alias> --json

# Run flow tests
sf flow test run --test-id <id> --target-org <alias> --json

# Run all flow tests
sf flow test run --target-org <alias> --json

Flow tests execute in the org and can take 1-5 minutes. Always run with --json and use background execution for longer runs.

Cross-Skill IntegrationReference

Reference Map

Start here

Design / orchestration

AI Decision

Screen / integration / troubleshooting

Score Guide

NeedDefault flow type
same-record update before savebefore-save record-triggered
related-record work / emails / calloutsafter-save record-triggered
guided UIscreen flow
reusable background logicautolaunched / subflow
scheduled processingscheduled flow
event-driven declarative responseplatform-event flow
AI-evaluated routing (sentiment, intent, tone)autolaunched with AI Decision element
NeedDelegate toReason
create objects / fields firstsf-metadataschema readiness
deploy / activate flowsf-deploysafe deployment sequence
create realistic bulk test datasf-datapost-deploy verification
create Apex actions / invocablessf-apeximperative logic
embed LWC in a screen flowsf-lwccustom UI components
expose Flow to Agentforcesf-ai-agentscriptagent action orchestration
ScoreMeaning
88+production-ready Flow
75–87good Flow with some review items
60–74functional but needs stronger guardrails
< 60unsafe / incomplete for deployment

More in Apex & Flow

Apex Code

Apex & Flow

Write custom Apex classes, triggers, and batch jobs. Describe what you need in plain English and AI builds production-ready Salesforce code.

Debug Logs

Apex & Flow

Read and analyze Salesforce debug logs. Paste the error, AI finds the root cause and tells you exactly what to fix.

Deployments

Apex & Flow

Deploy metadata between Salesforce orgs. AI handles the CLI commands, validation, and flags the things that could go wrong.

Navigate Apex & Flow

Previous
Deployments
Next
SOQL Queries