How to connect if/else branches with people lists in Play Builder

When working with if/else branches in Play Builder that need to process a list of people, you may encounter connection issues or confusing error messages about input type requirements. This article explains how to properly connect these components.

The Issue

Users often see error messages indicating that a "single record" is required when trying to connect if/else branches, even when working with a list of people from a trigger node. This can make it seem like you need to add intermediate processing nodes like loops to convert the data format.

The Solution

To properly connect an if/else branch when working with a list of people:

1. In your trigger node, click directly on "people" in the output

2. Connect this directly to your if/else branch node

3. Do not add intermediate nodes like loops between the trigger and the if/else branch

This direct connection method allows the if/else branch to properly process the people list input, even though the error messages may suggest otherwise.

Why This Works

The Play Builder can handle list inputs for if/else branches when connected directly from the trigger's "people" output. The confusing error messages about input types are often misleading in this context, and adding intermediate processing nodes can actually cause connection problems rather than solve them.

By connecting directly from the trigger's people output to your if/else branch, you ensure the proper data flow and avoid unnecessary complexity in your Play structure.