SharePoint Document Issues

How to Skip Blank Approvers in a SharePoint Approval Flow

Huma Ashraf ChHuma Ashraf Ch Nov 4, 2026 868 views

Question details

The user needs to configure a SharePoint approval workflow to automatically bypass optional approvers if their email fields are left blank.

How to Skip Blank Approvers in a SharePoint Approval Flow
Product
SharePoint / Power Automate
Device & OS
not provided
Scenario
Designing a multi-stage approval workflow in Power Automate where some approvers are optional, requiring the flow to check for blank email addresses to prevent failure.
Observed behavior
The workflow must verify if an email address is present before sending an approval request, proceeding directly to the next step if the current approver field is empty.
Before you start

Ensure you have Edit permissions for the target SharePoint list and the associated Power Automate workflow. Identify which approver fields in your list are optional so you can apply the appropriate conditional logic to them.

Solution 1Recommended

Use a Condition Control to Skip Blank Email Fields

The most straightforward method to handle optional approvers is adding a condition branch that checks if the approver's email field contains data before initiating the approval step.

By verifying the presence of an email address first, you prevent Power Automate from throwing a 'BadRequest' error caused by attempting to send an approval to a null user.

1
Edit your workflow

Open Power Automate, locate your SharePoint approval flow, and click 'Edit' to open the flow designer.

2
Add a Condition action

Click the '+' icon right before your 'Start and wait for an approval' action and select 'Add an action'. Search for and select the 'Condition' control.

3
Configure the condition logic

In the first field of the Condition block, insert the dynamic content for your optional approver's email. Set the operator to 'is not equal to' and leave the right-side field completely blank (or use the expression 'null').

4
Set up the 'If yes' branch

Drag your existing 'Start and wait for an approval' action into the 'If yes' box. This ensures the approval only triggers when an email address is actually present.

5
Configure the 'If no' branch

Leave the 'If no' box empty, or add a simple 'Compose' action to log that the step was skipped. The flow will naturally bypass the approval and continue to the next stage.

Use a Condition Control to Skip Blank Email Fields
Handling Multiple Approvers: If you have multiple sequential optional approvers, you will need to repeat this Condition check for each specific approver step in your chain.
Free Microsoft Office alternative

Collaborate on Documents Easily with WPS Office

While SharePoint and Power Automate handle complex backend workflows, WPS Office provides a free, lightweight, and highly compatible alternative for everyday document creation and team collaboration. Seamlessly transition your work without losing formatting.

  1. 1. Download WPS Office: Visit the official WPS website and click the 'Free Download' button.
  2. 2. Install the application: Run the downloaded installer and follow the simple on-screen instructions to set up the software.
  3. 3. Open and collaborate: Launch WPS Office to seamlessly open, edit, and share your existing Microsoft Office documents.
Highly compatible with Microsoft Office formats (DOCX, XLSX, PPTX)Built-in PDF editor and document sharing features for smooth teamworkLightweight application that runs smoothly on older or slower devicesFree alternative to costly Microsoft 365 subscriptions
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Power Automate flow fail when an approver email is blank?

Power Automate's approval action strictly requires a valid email address. If a blank value is passed to the 'Assigned To' field, the system cannot resolve the recipient, resulting in a 'BadRequest' error that stops the entire flow.

Can I use an expression instead of a condition block to skip blank approvers?

Yes. You can use expressions like `empty(variables('ApproverEmail'))` within an inline 'If' expression. However, using a standard Condition block is generally easier to visualize, troubleshoot, and manage in the flow designer.

How do I handle parallel approvals where one user might be blank?

For parallel approvals, you can wrap each parallel branch in its own condition check. Alternatively, you can use a 'Filter array' step to compile all valid emails into a single semicolon-separated string, then pass that string to a single approval action set to wait for all responses.