FREE COURSE · BEGINNER
Make

Build your first two-step practice scenario

A manually tested scenario that passes a fictional value from one module to another.

About 30 minutes4 practical stepsFree to read
A website displayed on a laptop at a bright wooden desk.

Before you start

A Make Free account, available credits and a browser. A laptop or desktop is easier for the scenario canvas. No other app connection or paid AI service is required.

Stay on the free route

This exercise uses built-in Tools modules and a manual run. Runs consume credits. Leave scheduling off; free-plan frequency and credit limits matter when you later automate a real job.

Original practice lesson · Official references checked 13 October 2026 · Button names may differ between app versions.

Your progress

0 of 4 steps complete.

Start first step ↓
STEP 1 · ABOUT 5 MIN

Map the practice flow

Learn the movement of data before connecting real services. Here, the result remains inside a practice scenario.

  1. Write the flow in your notes: “Set a fictional enquiry → pass it to a second module → inspect the result.”
  2. Use this value: “Practice enquiry: bicycle tyre check.” There are no customer details, messages or emails to send.
  3. Open a new scenario and name it “My first practice flow”. Leave its schedule disabled.
Practice example
Module 1: Tools → Set variable
Variable name: enquiry
Variable value: Practice enquiry: bicycle tyre check
Module 2: Tools → Set variable
Variable name: reviewed_enquiry
Variable value: map Module 1’s value
STEP 2 · ABOUT 8 MIN

Create the first variable

A variable temporarily holds a value during the scenario run. Use a clear name so you can recognise it later.

  1. Add Tools → Set variable as the first module.
  2. Set Variable name to enquiry and Variable value to “Practice enquiry: bicycle tyre check”. Save the module.
  3. Run the scenario once, then inspect the module output. Confirm the text you entered appears as a value. Keep the schedule off.
STEP 3 · ABOUT 9 MIN

Pass the value to a second module

Mapping means using the output from an earlier step instead of typing the same value again.

  1. Add another Tools → Set variable module after the first. Name its variable reviewed_enquiry.
  2. Click its value field and use the mapping panel to insert the value output from the first module. Do not type the sample sentence again.
  3. Save, run once and inspect the second module. Its result should match the first module’s value. If it is blank, reopen the field and check which output you mapped.
STEP 4 · ABOUT 8 MIN

Prove the mapping works

A changed input is a useful test: the output should follow it without editing the second step.

  1. Change only the first module’s value to “Practice enquiry: brake check”. Run once again.
  2. Inspect both modules. The second should now contain the changed value. Check the run history and actual credit usage.
  3. Save the scenario with scheduling off. Write down one real repeat job you might automate later, its trigger, intended action and what should happen if it fails. Choose the supported app connections before turning that idea into a live workflow.
TRY IT YOURSELF · ABOUT 5 MIN

The second module never changes

Your first practice module holds “tyre check”. In the second, you typed “tyre check” into the value field. After changing the first to “brake check”, the second still says “tyre check”.

Original fictional scenario · choose an answer, then read the explanation.

What needs changing?

See a worked example and review checklist

Module 1: enquiry = “Practice enquiry: brake check”. Module 2: reviewed_enquiry = mapped value from Module 1. Run once and inspect both outputs. This tests mapping, not a connection to a real inbox.

  • The second value is mapped, not a typed duplicate.
  • A changed first input reaches the second module.
  • I inspected the run and kept the practice schedule off.

Try it with a new example: Try a third fictional value. Change only the first module and predict the second output before running it.

This checks one practice decision, not your real work. Answers save only in this browser when storage is available.

MAKE THE LESSON YOURS

Keep your practice notes

Record what you made, what you checked and what you want to improve. These notes stay in this browser; they are not sent to us or synced to another device. Clearing browser data removes them.

Optional · up to 2,000 characters.

YOUR NEXT SMALL STEP

Build and test a three-question feedback form

A working practice form with required questions, a thank-you message and one checked test response.

Try the next course →

Part of Plan and test a small workflow.

GO FURTHER WITH THE PROVIDER

Make Academy: Foundation

Official free learning path. An Academy account or enrolment may be required. Access periods and badge requirements are set by Make.

Open official learning ↗

Sources and lesson notes

The practical brief and exercises are ours. Official references support the product guidance; we do not host the providers’ course content.

Checked 13 October 2026. Tool plans can change; consult the provider before choosing an upgrade. These beginner exercises have not been presented as certified or exhaustive product testing.

Progress saves in this browser. No site account needed.

THE OTHER FEW

Find the few things worth knowing.

Explore AI tools, software and technology through official sources, clear trade-offs and practical comparisons, so you can find the few that matter to your task.

Popular searches:

🔥 Fresh Few

Recently added to our catalogue, with a reason to explore each one.

💎 Hidden Gems

Editorial alternatives with a specific reason to consider them.

📊 Popular Categories

More from The Other Few
Personal Few

Build the few tools that work together.

Describe the outcome, not the software. The Other Few turns the job into a practical stack, keeps overlaps visible, and explains the trade-offs.

Stack suggestions are task-fit decisions, not product rankings. Commercial relationships must never change compatibility.
READY

Tell us the outcome.

We'll break it into jobs, choose the fewest sensible tools and show the trade-offs.

Evidence-first: current pricing, feature availability and platform support should be shown only when verified from an appropriate source.
THE OTHER FEW · INTELLIGENCE LAYER

From task to decision.

The shortlist now explains the fit, the trade-offs and what to do next.

PERSONALISED FIT
✦

Task understanding

Translate natural-language goals into task signals before matching products.

GoalUse caseConstraints
◎

Compatibility

Show why a tool fits this search instead of presenting a permanent product score.

PlatformExperiencePriority
↗

Decision path

Move naturally from shortlist to profile, alternatives, compare and saved tools.

ExploreCompareSave
DISCOVERY

Go beyond the shortlist.

Browse editorial collections when you want to explore rather than solve one task.

Fresh FewOnly products with a genuine freshness signal.Explore →
Hidden GemsInteresting products that deserve a closer look.Explore →
Popular CategoriesStart with the job, then narrow to the Few.Browse →
VERIFIED SOURCES · EDITORIAL FIT · NO PAID RANKING
RECOMMENDATION GRAPH

See why the Few connect.

The recommendation layer connects tasks, constraints, products, alternatives, workflows and evidence without turning the catalogue into a popularity ranking.

GRAPH ACTIVE
YOUR TASKgoal + constraintsTASKFITTOOLEVIDENCE intentexperienceplatformpriorityproductalternativesourcefreshness
EXAMPLE DECISION PATH
1 · GoalBuild a website for a small business.
2 · ConstraintsBeginner · web · low-code · ease.
3 · Candidate setReplit · Lovable · Claude — narrowed before presentation.
4 · Trade-offLovable favours simplicity; Replit offers more control; Claude is broader rather than purpose-built for the build.
Compatibility is task-specific. It is not a permanent product rating.

Graph signals

These are the relationships the engine can reason over as the catalogue grows.

Goal / intentConstraintTask fitAlternativeWorkflow overlapEvidenceFreshnessSaved context
Important: the graph does not invent evidence. Unsupported claims remain unsupported until verified.
PERSONAL DECISION LAYER

Make the decision smaller.

Bring your goal, saved tools, workflows and fresh changes together. The Other Few narrows the decision without pretending there is one universal winner.
● Decision context ready
Launch a businessBuild a websiteCreate videosResearch & decide
GoalWaiting
ConstraintsWaiting
Your FewLocal saves
ChangesFreshness ready
Start with the outcome.

We'll turn it into a smaller, clearer decision using the intelligence already built into The Other Few.
Fit is contextual. Editorial judgement, evidence and commercial relationships remain separate.Private on this device.
Intelligence Core
Make the catalogue smarter, not just bigger.
The intelligence layer now treats products, tasks, constraints, alternatives and workflows as connected evidence. Expansion is staged into verification lanes rather than filling the catalogue with unverified entries.
18 core records · verification-first
18Core records
7Categories covered
14Relationship types
0Fabricated records

Connected catalogue

Core products are connected to the tasks and categories they are already structured to serve.

Expansion lanes

These are research lanes, not unpublished product claims. A lane becomes catalogue data only after source verification and taxonomy review.
Editorial rule: catalogue breadth never outranks evidence quality. A product can enter the research queue without entering the public Few.
Intelligence Core

One brain. Every decision.

The catalogue, Finder, Decision Engine, workflows, Your Few and freshness signals now have a shared conceptual layer. The goal is not more results — it is better decisions with fewer tools.
● CORE MODEL READY

Decision graph

The same product can play different roles depending on the user's outcome and constraints.
18core products
7active categories
0saved tools
0watched tools
GoalOutcome
IntentTask
ConstraintsFit limits
ProductsCatalogue
DecisionFew