Seven Summer '26 Flow Updates That Add Up

Summer ’26 does not give Flow one enormous headline feature. It gives builders a collection of smaller improvements that remove familiar workarounds.

That matters because most Flow pain is not dramatic. It is friction repeated across dozens of automations.

Here are the seven updates I would check first.

1. Groups can require unanimous approval

An approval step assigned to a group can now wait for every member to approve.

That finally models real consensus for legal, finance, security, and change boards without building one step per approver.

Use it only when unanimity is the business rule. Group membership must be clean before the approval begins, and Salesforce notes that these work items cannot be reassigned.

2. Scheduled Flows get custom batch sizes

Scheduled Flows can use a batch size from 1 to 200 instead of always processing 200 interviews together.

A smaller batch can reduce transaction pressure when a Flow performs related DML, calls Apex, or touches fragile downstream automation. It can also increase total run time.

Treat the setting as a pressure valve: measure a realistic workload rather than choosing a small number because it feels safer.

3. Decisions understand dates

Date conditions now support operators such as Is Today, Is Anniversary of Today, and Last Number of Days.

That turns a formula resource named IsRenewalToday into a readable Decision condition: Renewal Date Is Today.

The win is not merely fewer resources. The business rule is visible where the branch happens.

4. Data Tables show lookup names

Screen Flow Data Tables in Aura and LWR sites can show a related record name instead of an ID and optionally link to the record.

Edge Communications is useful to a partner or service agent. 0018a00002abcXYZ is not.

This is a small change that makes guided experiences feel finished.

5. More standard components support styling

The Style tab now reaches more components, including Address, Choice Lookup, Dependent Picklists, Lookup, Slider, Toggle, and common contact inputs.

Use overrides to align spacing, emphasis, and portal branding. Do not let every Flow invent colours, tiny text, and inconsistent component treatments.

The goal is consistency, not decoration.

6. Apex-defined inputs need less ceremony

Builders can set fields inside Apex-defined inputs directly in the action property panel.

That removes the old variable-plus-Assignment dance. It also exposes weak DTO design more clearly: labels, descriptions, required fields, and optional fields now form a visible admin-facing API.

A cleaner editor cannot rescue a confusing contract.

7. Custom components can expose style settings

Custom Flow screen components can provide supported presentation controls to Flow Builder.

Expose choices such as Comfortable or Compact, with strong defaults and accessible output. Avoid turning the property panel into raw CSS configuration.

Admins need enough control to fit a component into the screen, not enough to create a new design system in every Flow.

Why the group matters

Together these updates remove manual approval chains, oversized scheduled batches, date formulas, visible record IDs, unnecessary custom components, wrapper-variable assignments, and ad hoc styling properties.

That is the Summer ’26 Flow story: the obvious path is becoming the clean path.

Start with group approvals that genuinely need consensus, scheduled Flows under limit pressure, date formulas used only for Decisions, and Data Tables exposing IDs. Those are immediate wins.

The individual features are small. The reduction in workaround-shaped Flow is not.