By default, when the “Manage Database” action fails to find a matching row, the Flowbot stops with an error.

This guide explains how to prevent the Flowbot from stopping and instead branch to a different operation when no matching record is found.

We will create a Flowbot that:

✔️ Updates a record if the form data already exists in the database.

✔️ Adds a new record if no matching record is found.

🎯 The flowbot will NOT stop due to a missing row—it will automatically branch and continue processing!

Since the process starts from a form submission, configure a form trigger.

Make sure the form includes all necessary fields required for both updating and adding records.

✔️ Choose the database (e.g., Google Sheets) in the action selection screen.

✔️ Select the action “Update Record”.

✔️ Define the search conditions and specify the fields to update.

‼️ Important

At the bottom of the setup screen, under Advanced Settings, turn OFF the setting for "Handling of Search Failures".

This ensures that even if no matching records are found, the Flowbot continues running instead of stopping.

✔️ In between actions, add a Branching action.

✔️ Choose the update record action as the branch target.

✔️ Set the branch condition to "Output is empty."

This means that if no matching record is found, the Flowbot will take a different path.

For the "Output is empty" branch:

✔️ Add another “Manage Database” action.

✔️ Choose the same database used for updating.

✔️ Set execute action to “Add Record.”

✔️ Configure the data to be added.

✅ If a matching record exists, it is updated.
✅ If no matching record is found, the flowbot adds a new record instead of stopping.

Your Flowbot Now Handles Missing Records Seamlessly!

No more interruptions—ensure smooth data processing every time.