01. n8n workflow architecture
Practical objective
Non-production flow diagram.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Separate trigger, transform, decision and output. define minimal ticket data.
Guided workshop
- Separate trigger, transform, decision and output
- define minimal ticket data
- keep external systems outside the lab
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Non-production flow diagram. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
02. Installation and environments
Practical objective
Readiness checklist, no server installed.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Compare hosted and self-hosted options using security needs. separate test, staging and production.
Guided workshop
- Compare hosted and self-hosted options using security needs
- separate test, staging and production
- document backup and updates without deployment
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Readiness checklist, no server installed. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
03. Manual and scheduled triggers
Practical objective
Trigger spec and edge case.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Plan a manual run over five tickets. compare a scheduled trigger.
Guided workshop
- Plan a manual run over five tickets
- compare a scheduled trigger
- define time window and reprocessing risk
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Trigger spec and edge case. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
04. Expressions and JSON transformations
Practical objective
Validated JSON input/output.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Read an object with ID, category and severity. normalise without losing ID.
Guided workshop
- Read an object with ID, category and severity
- normalise without losing ID
- handle missing values explicitly
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Validated JSON input/output. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
05. Conditions and branches
Practical objective
Three-row routing matrix.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Route critical tickets to human review and others to a standard queue. define unknown-category fallback.
Guided workshop
- Route critical tickets to human review and others to a standard queue
- define unknown-category fallback
- test three tickets
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Three-row routing matrix. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
06. Loops, batches and volumes
Practical objective
Verified batches 2 + 2 + 1.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Split five tickets into batches of two. handle final partial batch.
Guided workshop
- Split five tickets into batches of two
- handle final partial batch
- define upper limit and stop condition
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Verified batches 2 + 2 + 1. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
07. Webhooks and input protection
Practical objective
Data contract and rejection rule.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Specify an endpoint without activating it. validate schema, event key and size.
Guided workshop
- Specify an endpoint without activating it
- validate schema, event key and size
- reject empty body and retain only trace ID
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Data contract and rejection rule. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
08. Errors, logs and recovery
Practical objective
Recovery plan for permanent and transient faults.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Simulate malformed ticket and temporary failure. decide abort versus retry.
Guided workshop
- Simulate malformed ticket and temporary failure
- decide abort versus retry
- add logs without sensitive fields
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Recovery plan for permanent and transient faults. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
09. Credentials, rights and audit
Practical objective
Risk register with mitigations.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
List minimum permissions per connection. review security-audit findings.
Guided workshop
- List minimum permissions per connection
- review security-audit findings
- exclude secrets, risky nodes and exposed webhooks from the lab
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Risk register with mitigations. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
10. Versioning and controlled deployment
Practical objective
Release checklist with rollback.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Version the ticket schema. plan four-eyes approval and rollback.
Guided workshop
- Version the ticket schema
- plan four-eyes approval and rollback
- forbid automatic deployment of exercise workflows
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Release checklist with rollback. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
11. Reliability measurements
Practical objective
Execution table with computed indicators.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Define success, rejected and retried tickets. count unique processed IDs.
Guided workshop
- Define success, rejected and retried tickets
- count unique processed IDs
- compare simulated log to expected outputs
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Execution table with computed indicators. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
12. Final project: ticket processing
Practical objective
Technical dossier, local log and tests.
Scenario
Fictional offline lab: processing sample tickets locally, with no public webhook and no real credentials.
Key concept
Build a workflow plan for five JSON tickets, validate IDs, deduplicate and route critical ones. generate an offline log.
Guided workshop
- Build a workflow plan for five JSON tickets, validate IDs, deduplicate and route critical ones
- generate an offline log
- mark all n8n steps not actually run
Independent exercise
Using the supplied dataset, repeat with one additional record and log what changes. The deliverable must not trigger any external action.
Solution and evidence
Expected output : Technical dossier, local log and tests. Acceptance check: two people should be able to locate the deliverable and understand the decision without an oral explanation.
Caution : Simulated workshop, not tested in a live software account. Recheck available commands and plan restrictions in your environment.
