FREE COURSE · BEGINNER
Workflow planning

Plan a simple automation before building it

A small workflow brief with an input, a rule, an output and three test cases.

About 15 minutes4 practical stepsFree to read
A developer workspace with a laptop displaying code.

Before you start

Paper or a notes app. No app connections, customer records or paid automation service are needed.

Stay on the free route

This lesson creates a plan only. Sending messages, changing real records and enabling a schedule are later steps that require appropriate access and testing.

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

Your progress

0 of 4 steps complete.

Start first step ↓
STEP 1 · ABOUT 3 MIN

Pick one repeatable job

Start with a small task you can describe precisely. A workflow needs a clear input and an observable result.

  1. Use this fictional job: sort a practice enquiry into Repairs or Other.
  2. Write what happens now: someone reads the subject and adds a category to a practice list.
  3. Keep the first version inside your notes. It does not contact anyone or make a booking.
Practice example
Input: a fictional enquiry subject
Rule: if the subject contains “repair”, category = Repairs; otherwise category = Other
Output: the subject and category in a practice list
STEP 2 · ABOUT 4 MIN

Define missing and repeated inputs

The normal case is only part of the job. Decide what should happen when an input is blank or repeated.

  1. Give each practice enquiry an ID so you can recognise a duplicate.
  2. For an empty subject, choose Needs review rather than guessing the category.
  3. For a repeated ID, keep one result rather than adding a second row. Record the decision in the brief.
Practice example
Empty subject → Needs review
Repeated enquiry ID → do not add a second result
Unexpected error → keep the original input and mark the run for review
STEP 3 · ABOUT 4 MIN

Run three cases by hand

Test the rule manually before choosing software. This helps distinguish a bad rule from a tool setup problem.

  1. Try E01 with subject “Bicycle repair question”: expect Repairs.
  2. Try E02 with a blank subject: expect Needs review.
  3. Try E01 again with the same subject: expect no new row. Note what you would check if an output differs.
Practice example
E01 | Bicycle repair question | Repairs | one result
E02 | [blank] | Needs review | one result
E01 | Bicycle repair question | duplicate | no extra result
STEP 4 · ABOUT 4 MIN

Make the build small enough to test

Use the plan to choose the smallest useful practice build. You can learn data mapping before connecting a live inbox or form.

  1. Save the input fields, category rule, expected output and test cases together.
  2. Decide who should review an error before any real records are changed.
  3. Continue with the Make practice scenario to learn how a value moves between two modules. That course teaches mapping; it does not implement this entire enquiry sorter.
TRY IT YOURSELF · ABOUT 5 MIN

The same enquiry arrives twice

Your practice sorter receives enquiry E01, then receives E01 again. The brief says there should be one result per enquiry ID.

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

What should the plan do with the repeated ID?

See a worked example and review checklist

Input E01 → create one practice result. Repeated E01 → keep the existing result, record or skip the repeat according to the brief. Blank subject → Needs review.

  • The duplicate test does not create an extra result.
  • A blank input has its own review route.
  • I have separated planning from enabling a live workflow.

Try it with a new example: Choose what a later changed enquiry should do: update the existing result or send it for review. Write that rule before building 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 your first two-step practice scenario

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

Try the next course →

Part of Plan and test a small workflow.

READ THE BACKGROUND GUIDANCE

Make: module types

Official background on triggers, actions and other module types. The provider-neutral planning exercise below is ours.

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 17 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