🟢 Make (Integromat) · January–February 2026 · B2B / B2C Lead Automation

📎 Project Link: https://drive.google.com/file/d/14SPL5QYJe5JWVVOFmfQpdk2Ichyu-LiH/view?usp=sharing

CONTEXT

Small and mid-size businesses running email outreach face two operational bottlenecks that grow with scale: manually deciding which leads should receive an email based on their status, and keeping a CRM-style record up to date when new contact data arrives from external sources. Both tasks are repetitive, error-prone when done by hand, and consume admin time that should go elsewhere.

This project delivered a working no-code automation pipeline in Make (Integromat) that solves both problems end-to-end. Google Sheets served as the lead database, Gmail as the email delivery layer, and Postman was used for API validation before connecting external data sources. All scenarios were tested and confirmed with zero errors in Make’s execution History.

PROBLEM STATEMENT

Three concrete operational problems were identified and addressed:

• ❌ Unfiltered email sends: outreach emails were being sent to all rows in the spreadsheet, regardless of lead status — no condition check, no record of what was sent or when
• ❌ No record sync from external sources: when a contact submitted data through an external form or API, there was no automated way to check if they already existed and update their record — new rows were always added, creating duplicates
• ❌ No API pre-validation: external endpoints were connected to automations without prior testing, causing runtime errors when the response format didn’t match expectations

Goal: replace manual lead handling with two automated Make scenarios that filter, dispatch, validate, and sync data — reliably, without human intervention after setup.

SOLUTION

I designed and built two independent Make scenarios that together cover the full lead processing cycle. Each scenario includes a data validation layer so that only clean, complete records trigger downstream actions. The architecture is intentionally modular: each scenario can be extended or reused independently.

Scenario 1—Conditional Email Dispatch with Automatic Status Logging

The scenario monitors a Google Sheet for new rows. A 3-condition filter checks that the email field is filled, the subject exists, and the subject contains a target keyword (“promo”). Only rows that pass all three conditions trigger Gmail to send the message—and immediately after, the same row is updated with a delivery status and timestamp. Rows that don’t pass are logged as “filter not passed” in History with no action taken.

Google Sheets: Watch New Rows → Filter: email exists, AND subject exists, AND subject contains "promo." → Gmail: Send an Email (To: email | Subject: subject | Body: message) → Google Sheets: Update a Row (send_status = "sent" | send_ts = now)

Scenario 2—Webhook-Driven Upsert: Update Existing or Create New Record