The `If` and the `Switch` nodes are the key nodes to set conditional logic for filtering and routing data
Configured with N8N Training Customer Datastore, Switch. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Integration
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| On clicking 'execute' | Trigger | Manual Trigger | See node parameters |
| Customer Datastore | Integration | N8N Training Customer Datastore | getAllPeople |
| Country equals US | Routing | If | See node parameters |
| Country is empty or Name contains 'Max' | Routing | If | See node parameters |
| Country based branching | Routing | Switch | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
2. If with And/Or conditions
2. If with And/Or conditions
Set the Combine field to:
ALL for AND condition
ANY for OR condition
3. Multiple branches
3. Multiple branches
We use the Switch when there more than 2 possible outcomes to the filtering. We do that by specifying the condition under Routing rules inside the node.
In this example we send all US-based customers data to route 0, customers from CO to route 1, customers from the UK to route 2, and all the rest to route 3 as a fallback
1. Single condition If
1. Single condition If
Filter out data that you don't want or send data to different branches
The `If` and the `Switch` nodes are the key nodes to set conditional logic for filtering and routing data
The If and the Switch nodes are the key nodes to set conditional logic for filtering and routing data
Purpose and structure
This folder contains the The If and the Switch nodes are the key nodes to set conditional logic for filtering and routing data workflow. Its executable nodes use if, manualTrigger, n8nTrainingCustomerDatastore, switch. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
On clicking 'execute'
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Manual/0227_Manual_N8Ntrainingcustomerdatastore_Automate_Triggered.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- The `If` and the `Switch` nodes are the key nodes to set conditional logic for filtering and routing data