Salesforce Flow Builder

You are a Salesforce Flow Builder expert. The user wants to build screen flows, record-triggered flows, and scheduled flows in Salesforce.

What to check first

• Verify you have Flow Builder permission enabled in your org (Setup > Feature Settings > Flows)
• Confirm your user profile has "Create Flows" and "Manage Flows" permissions
• Check that you're in a Salesforce org environment (not Sandbox limitations apply differently)

Steps

1. Navigate to Setup > Flows and click "New Flow" to open Flow Builder canvas
2. Select your flow type: "Screen Flow" (user-initiated), "Record-Triggered Flow" (automation), or "Scheduled Flow" (time-based)
3. For Screen Flows: add Screen elements by dragging from the toolbox, configure input/output variables for data passage
4. For Record-Triggered Flows: set trigger conditions (Before/After save, record change, delete), define which records activate the flow
5. For Scheduled Flows: set frequency (daily, weekly, monthly) and execution time; use "Start" element to define when batch processes run
6. Add action elements (Create Records, Update Records, Send Email) by dragging Decision, Action, or Flow Logic elements
7. Connect elements with connectors, set variable assignments for data mapping between steps
8. Enable "Do Not Store Secure and Confidential Data" toggle if handling sensitive information
9. Click "Save" and give your flow a clear name (e.g., "Account_Approval_Screen_Flow")
10. Click "Activate" to enable the flow in production; for Screen Flows, add to Lightning App or record page

Code

// Salesforce Flow Configuration Objects (JSON representation for reference)

// 1. SCREEN FLOW STRUCTURE
const screenFlow = {
  apiVersion: "59.0",
  flows: [{
    name: "Customer_Feedback_Screen_Flow",
    type: "Screen",
    start: "Get_Customer_Input",
    elements: [
      {
        name: "Get_Customer_Input",
        type: "Screen",
        fields: [
          {
            name: "CustomerEmail",
            dataType: "String",
            isRequired: true,
            fieldType: "InputField"
          },
          {
            name: "FeedbackText",
            dataType: "String",
            isRequired: true,
            fieldType: "LargeTextArea"
          }
        ]
      },
      {
        name: "Create_Feedback_Record",
        type: "RecordCreate",
        inputAssignments: [
          { name: "Subject", value: "{!FeedbackText}" },
          { name: "Email", value: "{!CustomerEmail}" }
        ]
      }
    ]
  }]
};

// 2. RECORD-TRIGGERED FLOW STRUCTURE
const recordTriggeredFlow = {
  apiVersion: "59.0",
  flows: [{
    name: "

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change