Salesforce Flow

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.

Compare Salesforce Flow with Microsoft Power Automate, Workato, MuleSoft Composer. Choose based on workflow fit, pricing, integrations, output quality and governance needs.