Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/flow-for-admins

flow-for-admins

Verified

Use when designing, reviewing, or debugging Salesforce Flows from an Admin perspective. Triggers: 'flow', 'automation', 'record-triggered flow', 'screen flow', 'scheduled flow', 'flow error', 'flow interview', 'before-save vs after-save', 'flow deployed as draft', 'entry criteria', 'fault connector', 'flow-meta.xml', 'FlowDefinitionView'. NOT for Flow debug mode, Run As user, or Flow test suites — use flow/flow-debugging. NOT for building an OmniStudio OmniScript — use omnistudio/omniscript-design-patterns.

references/examples.md

View on GitHub
# Examples: Flow for Admins

---

## Example: Record-Triggered Flow — Update Parent When Child Changes (Bulkification Pattern)

**Requirement:** When a Case is closed, update the parent Account's Last_Case_Closed_Date__c field.

**Flow type:** Record-Triggered Flow (After Save — needs DML on a different object)

**Entry criteria:** `{!$Record.Status} = "Closed"` AND `{!$Record.Status} <> {!$Record__Prior.Status}` (only when Status changes TO Closed)

**Structure:**

```
[TRIGGER: Case After Save — when Status changes to "Closed"]
          ↓
[GET RECORDS: Account where Id = {!$Record.AccountId}]
  ├── fault → [SEND EMAIL: Fault on Get Account] → [END]
  └── success ↓
[UPDATE RECORDS: Account — set Last_Case_Closed_Date__c = TODAY()]
  ├── fault → [SEND EMAIL: Fault on Update Account] → [END]
  └── success ↓
[END]
```

**Why the entry criteria matters:** Without `{!$Record.Status} <> {!$Record__Prior.Status}`, this flow fires every time ANY field on a Closed Case is edited — adding a comment, changing the owner, anything. The delta check (`<> Prior`) ensures it only fires when Status transitions to Closed.

**Bulkification note:** This flow is already bulk-safe. "Update Records" with a single record variable (not a loop) is one DML statement regardless of how many Cases are in the transaction.

---

## Example: Screen Flow — Multi-Step Data Entry with Validation

**Requirement:** Guided screen for converting a Lead to a Contact with custom qualification questions.

**Flow type:** Screen Flow (user-initiated, guided process)

**Structure:**

```
[SCREEN 1: Qualification Questions]
  - Lead Interest Level (picklist — required)
  - Budget Confirmed (checkbox)
  - Decision Timeline (text — required)
  Next button → validates required fields
          ↓
[DECISION: Is Budget Confirmed?]
  ├── Yes → [SCREEN 2A: Budget Details]
  └── No  → [SCREEN 2B: Budget Discovery]
          ↓
[CREATE RECORDS: Create Qualified_Lead_Response__c]
  ├── fault → [SCREEN: Error — "We couldn't save your response. Contact your admin."]
  └── success ↓
[SCREEN: Confirmation — "Lead qualified. Next steps: [...]"]
          ↓
[END]
```

**Error screen pattern:** The fault path for DML in a Screen Flow should show the user a human-readable screen, not a Salesforce system error. Always capture `{!$Flow.FaultMessage}` in the error screen for admin debugging.

```
Error Screen content:
"We encountered an issue saving this record.
Error details: {!$Flow.FaultMessage}
Please contact [Admin Email] and reference Lead ID: {!$Record.Id}"
```

---

## Example: Scheduled Flow — Weekly Cleanup with Batch-Safe Patterns

**Requirement:** Every Monday at 6am, find all Leads that haven't been contacted in 30+ days and set Status to "Unresponsive".

**Flow type:** Scheduled Flow

**Key consideration:** each record the schedule's query returns starts one interview. The org-wide
ceiling is 250,000 schedule-triggered interviews per rolling 24 hours (or user licences x 200,
whichever is greater) — a *per-day, org-wide* number, not a per-run one, so several scheduled flows
share it. The repo's routing line sits well below that: above roughly 50,000 records per run,
`standards/decision-trees/flow-pattern-selector.md` Q6 sends you to Apex Scheduled + Batchable, and
`automation-selection.md` Q10 agrees. Count the records in a report before you build.

```sql
-- Pre-flight: how many interviews will one run actually start?
SELECT COUNT(Id) FROM Lead
WHERE LastActivityDate < LAST_N_DAYS:30
  AND Status NOT IN ('Converted', 'Unresponsive', 'Closed')
```

The `start` element that produces that schedule — note there is no entry-criteria transition gate
here, because a scheduled flow has no "prior" record to compare against; the query filter *is* the
entry criteria:

```xml
<start>
    <locationX>50</locationX>
    <locationY>0</locationY>
    <connector>
        <targetReference>Loop_Stale_Leads</targetReference>
    </connector>
    <filterLogic>and</filterLogic>
    <filters>
        <field>Status</field>
        <operator>NotEqualTo</operator>
        <value>
            <stringValue>Converted</stringValue>
        </value>
    </filters>
    <object>Lead</object>
    <schedule>
        <frequency>Weekly</frequency>
        <startDate>2026-09-07</startDate>
        <startTime>06:00:00.000Z</startTime>
    </schedule>
    <triggerType>Scheduled</triggerType>
</start>
```

`FlowSchedule` carries `frequency` (`Once` / `Daily` / `Weekly`), `startDate`, and `startTime`, and
"the time of day when the flow runs, based on the org's default time zone" — not the author's
(Metadata API Developer Guide, *FlowSchedule*, api_meta.txt:71335–71382). `schedule` is required when
`triggerType` is `Scheduled` (api_meta.txt:72462–72463).

**Structure:**

```
[SCHEDULE: Monday 6:00 AM]
          ↓
[GET RECORDS: Lead where LastActivityDate < (TODAY - 30)
              AND Status NOT IN ("Converted", "Unresponsive", "Closed")
              LIMIT: 2000]  ← always set a practical limit
  ├── fault → [SEND EMAIL: Fault getting leads] → [END]
  └── success ↓
[LOOP: through Lead collection]
          ↓
  [ASSIGNMENT: set loopLead.Status = "Unresponsive"]
  [ADD to updateLeadCollection]
          ↓
[END LOOP]
          ↓
[UPDATE RECORDS: updateLeadCollection]  ← single DML, not in loop
  ├── fault → [SEND EMAIL: Fault updating leads]
  └── success ↓
[END]
```

**Why the LIMIT:** without one, every matching Lead starts an interview, and the run's cost is
whatever the data happens to be that week. `FlowRecordLookup.limit` accepts values "between 2 and
20,000… supported only when `getFirstRecordOnly` is `false`" and is available from API version 63.0
(Metadata API Developer Guide, *FlowRecordLookup*, api_meta.txt:71177–71183). A bounded run that
processes the backlog over several weeks is more operable than an unbounded one that fails on the
week the data spikes.

---

## Example: Autolaunched Flow — Called from Apex with Input/Output Variables

**Requirement:** Complex pricing logic managed by Admins, called from Apex during Opportunity save.

**Flow type:** Autolaunched Flow (no trigger — called programmatically)

**Flow variables to configure:**
- `inputOpportunityId` (Text, Input) — passed from Apex
- `inputProductFamily` (Text, Input) — passed from Apex
- `outputDiscountPercent` (Number, Output) — returned to Apex

**Apex call pattern:**
```apex
Map<String, Object> inputs = new Map<String, Object>{
    'inputOpportunityId' => opp.Id,
    'inputProductFamily' => opp.Product_Family__c
};

Flow.Interview interview = Flow.Interview.createInterview(
    'Calculate_Opportunity_Discount',  // Flow API name
    inputs
);
interview.start();

Decimal discount = (Decimal) interview.getVariableValue('outputDiscountPercent');
```

**Why use a Flow here instead of Apex:** Business users can modify pricing rules in Flow Builder without a code deployment. The Apex caller doesn't change — only the Flow logic changes. This is the "configurable logic" pattern.

**Governor limit warning:** This Flow runs in the same transaction as the Apex call. Any SOQL in the Flow counts against the transaction's SOQL limit. Design the Flow to be SOQL-minimal.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall