BiTree
  • Search For Lessons
  • Curriculum
  • Pricing
  • For Educators
  • Become a Tutor
  • About
  • Contact
Log InGet Started

Questions, concerns, bug reports, or suggestions? We read every message, write to us at [email protected].

More ways to reach us →
BiTree

Live coding lessons for aspiring developers and security professionals.

[email protected]

(201) 785-7951

Mon–Fri, 9 AM–5 PM EST

Learn

  • Search For Lessons
  • Curriculum
  • Pricing

Company

  • About
  • For Educators & Schools
  • Become a Tutor
  • Contact Us

Legal

  • Terms of Service
  • Privacy Policy
© 2026 BiTree. All rights reserved.
Curriculum/AI Agents/No-Code Agents/Make.com: Scenario-Based Agent Flows
50 minBeginner

Make.com: Scenario-Based Agent Flows

After this lesson, you will be able to: Build multi-step Make.com scenarios that use AI modules to extract, classify, and route data through complex conditional logic.

Make.com (formerly Integromat) is Zapier's most direct competitor, but with a far better visual canvas for branching, looping, and aggregation. This lesson uses Make to build a content moderation pipeline: incoming submission → classify → branch on result → store + notify.

Prerequisites:Zapier: Automation + AI Steps

Why Make over Zapier

Visual scenario canvas (you see the flow, not a vertical list). Built-in routers, iterators, aggregators. Cheaper at scale. The downside: smaller integration library and a steeper learning curve. Worth it for branching-heavy work.

Build the moderation scenario

  1. 1

    1. Sign up at make.com (free tier).

  2. 2

    2. Create a scenario. Trigger: 'Webhook' → 'Custom webhook'. Copy the URL.

  3. 3

    3. Add module: 'OpenAI / Claude' → 'Create a Completion'. Prompt: 'Classify this submission as SAFE, FLAG, or BLOCK and explain in one sentence: {{1.text}}'.

  4. 4

    4. Add module: 'Router' (the diamond icon, splits flow).

  5. 5

    5. Branch 1, filter: result contains 'SAFE'. Connect to Google Sheets 'Add Row' (approved log).

  6. 6

    6. Branch 2, filter: result contains 'FLAG'. Connect to Slack post + Sheets review queue.

  7. 7

    7. Branch 3, filter: result contains 'BLOCK'. Connect to Sheets blocked log + email admin.

  8. 8

    8. Run once. POST sample text to the webhook URL. Watch the canvas highlight the path it took.

💡 Routers vs. filters

A Router fans data out into parallel paths (each path can have its own filter). A Filter on a single edge only continues if the condition is true. Use Routers for multi-class branching, Filters for single yes/no gates.

Iterators and aggregators

Iterator splits an array into multiple bundles, one per item, so downstream modules run once per item. Aggregator collects multiple bundles back into one. Pair them when you need 'for each item, do X' loops in a no-code flow.

Test and turn on

  1. 1

    1. After each module run, click the bubble to inspect input/output JSON.

  2. 2

    2. Once the scenario works end-to-end, click the toggle to enable it.

  3. 3

    3. Set a schedule (or leave it as on-demand for webhook triggers).

Sign in and purchase access to unlock this lesson.

Sign in to purchase
←Zapier: Automation + AI Steps
Back to No-Code Agents
Voiceflow: Chat and Voice Agent Design→