← AIAP Topic CoursesAll programsHomeSearch
AIAP Topic Courses·Make·09:50

Your First Real Scenario: Router, Search Rows, Filters (the Upsert Pattern), Functions, and History

Samruti Make trainer - builds a Google Forms to Google Sheets scenario live on a free Make plan

The short version

  1. Goal: if the person already submitted, update their row; else add one. Router with two paths; Update a Row was hard-coded to row 2, so add Google Sheets > Search Rows filtered by email before the router and use its row number dynamically; filters on each route - 'row number does not exist' for Add, 'exists' for Update. Without filters both paths run (0:00-0:07).
  2. Functions: math, text, date/time, arrays, custom - an if/else for 'budget over a thousand'. History tab: timestamps, status, operations, duration, data, per-step advanced log, errors (0:07-0:09).

At a glance, three clicks deep

Skim here first: the closed row is the glance, open is the study card with the key points and timestamps, and the ↓ link drops to that concept's full write-up below.

01The upsert pattern: search, router, filtersSearch -> router -> filtered paths;›

Search -> router -> filtered paths; read History.

Router and search (0:00-0:05)

Filters and test (0:05-0:07)

Functions and History (0:07-0:09)

↓ Full write-up of this concept

The concepts in full

01

The upsert pattern: search, router, filters

Search for the email first. If a row comes back, update it; if nothing comes back, add one. Two filters make the router choose.

PROCEDURE: add a Router after the trigger with two paths (Add a Row, Update a Row). Insert Google Sheets > Search Rows before the router with filter email = mapped email. In Update a Row, replace the hard-coded row number with the search output's row number. Filters: Add path - 'row number does not exist'; Update path - 'row number exists'. Routes evaluate top to bottom; without filters both run. Test: a new email routes to Add. Functions (math, text, date, arrays, if/else) handle rules like budget thresholds. History shows each run's status, operations, duration and a per-step advanced log for debugging.

Why it matters

The first pattern that makes an automation safe to leave running.

Tools referenced

ToolCoverageMomentContext
Make.comdemonstratedRouter, filters, Search Rows, History
Google Sheetsdemonstrated

Action items

    Resources mentioned

    Resources
    • docLesson page on the platform

    Extraction notes

    This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

    Transcript corrections applied

    The transcript saysThe trainer actually means
    Charge GPT / Chart GPT / ChargeGPDChatGPT
    cloud / Cloud AIClaude
    Mishou / Misho / MISOMeesho
    main dot com / mail dot comMake.com

    True on recording day — verify before relying