# 07. Automate one clear decision.

Route a fictional request to review or the normal queue.

## Facilitator preflight

Bring laptops, internet, a projector and these local course files. Check tool access before the meetup. Keep samples free of personal information.

Quick win: Run a Manual Trigger and see one data item.

Prerequisites: A facilitator-prepared n8n instance. No AI model needed.

### Tools and cost notes

- **n8n workflow editor with permission to create test workflows.**: Prepared before the meetup.. Hosting/cloud terms vary. Use a prepared workshop instance; no paid model call.

## Run of show

| Slide | Minutes | Activity |
|---|---:|---|
| 1 | 3 | Automate one clear decision. |
| 2 | 3 | Before you start. |
| 3 | 5 | Your first small win. |
| 4 | 3 | What happens between input and output? |
| 5 | 3 | Step 01. Create a test workflow. |
| 6 | 3 | Step 02. Add a fictional request. |
| 7 | 3 | Step 03. Add the rule. |
| 8 | 3 | Step 04. Name both outputs. |
| 9 | 3 | Step 05. Test both branches. |
| 10 | 3 | Step 06. Save the working version. |
| 11 | 4 | Make the working version. |
| 12 | 4 | Ask for a review. Then check it. |
| 13 | 6 | Prove your result works. |
| 14 | 4 | When it does not work yet. |
| 15 | 5 | Choose your next challenge. |
| 16 | 3 | Keep the result. Keep the evidence. |
| 17 | 2 | Sources you can check. |

Total: 60 minutes.

## 1. Automate one clear decision.

Outcome: Route a fictional request to review or the normal queue. This is a 60-minute in-person laptop session after preflight. No setup-duration guarantee. Core first, extensions second.

## 2. Before you start.

Hosting/cloud terms vary. Use a prepared workshop instance; no paid model call. The facilitator verifies accounts, installed tools and model/host connections before the session. Pair up if setup is incomplete. Do not create accounts or incur costs without understanding the provider terms.

## 3. Your first small win.

Quick win: Run a Manual Trigger and see one data item. Aim for a visible result in the first 15 minutes after preflight. Explain that generated code/output is untested until the learner checks it. If tools are unavailable, inspect the prepared example with a partner.

Copyable prompt: [Open prompt](index.html#07-quick-win)

```text
Sketch a tiny workflow: manually start, create a fictional request with urgent=true, send urgent requests to review and others to the normal queue. Name the inputs and the expected output. Do not add AI or external messages.
```

## 4. What happens between input and output?

Ask a learner to explain each stage in their own words. This is a teaching model, not a promise that all tools behave identically.

## 5. Step 01. Create a test workflow.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 6. Step 02. Add a fictional request.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 7. Step 03. Add the rule.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 8. Step 04. Name both outputs.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 9. Step 05. Test both branches.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 10. Step 06. Save the working version.

Perform these numbered actions on the laptop. Pause after the step and inspect the result. Use fictional or approved material.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## 11. Make the working version.

Use fictional practice inputs. Ask learners to show their work, not just the final answer.

Copyable prompt: [Open prompt](index.html#07-build)

```text
Write a manual test table for my request router. It uses a Boolean urgent field: true means review, false means normal. Include a missing-field case and a wrong-type case. Do not claim the workflow was executed.
```

## 12. Ask for a review. Then check it.

Use fictional practice inputs. Ask learners to show their work, not just the final answer.

Copyable prompt: [Open prompt](index.html#07-review)

```text
Check my workflow design for missing fields, text-versus-Boolean mistakes and dropped request data. Give one correction at a time. Design: Manual Trigger -> Edit Fields -> If -> review or normal Edit Fields.
```

## 13. Prove your result works.

These are manual acceptance tests for the learner to perform. No test is claimed to have run merely because it appears here. Ask pairs to demonstrate one pass and one corrected failure.

## 14. When it does not work yet.

Choose the observed symptom. Change one thing and rerun the smallest test. Avoid restarting the whole project or adding tools before diagnosing the current step.

## 15. Choose your next challenge.

Experienced learners use the extensions while beginners complete the same core outcome. An extension is optional, not a prerequisite for participating.

## 16. Keep the result. Keep the evidence.

Save the working version before leaving. Add a short note: what worked, what needed correction and what you would try next. The next module builds on the saved output.

## 17. Sources you can check.

Primary sources checked during course creation on 2026-10-08. Provider interfaces and availability can change. The examples, prompts and activities are original community teaching designs. Source links explain capabilities; they do not prove these fictional exercises were executed.

Source: [n8n: Edit Fields](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.set/)

Source: [n8n: If node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.if/)

## Extensions

- Add a third priority without using AI.
- Import another request and test the rule on it.

## Delivery notes

Arrow keys, Space, Home and End navigate slides. N opens notes. Read all slides creates a scrolling lesson. Every prompt has a real Copy prompt button with an honest manual fallback if the browser blocks clipboard access. Keep the whole curriculum folder together: PPTX prompt links open the companion index.html at the same prompt anchor. PowerPoint does not copy directly. For sharing online, rebuild with --companion-base-url set to the published curriculum URL.

Motion illustrates input, agent, tool, human review and output. Pause flow stops it; system reduced-motion is respected. PDF contains a static diagram. PPTX uses an animated GIF where available; playback varies by viewer.

Original teaching content, synthesized from learning objectives. Public source decks remain separate in library/. No one-to-one rebranding or permission to republish is implied.
