Skip to content

Update chapter-3.md #3109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update chapter-3.md #3109

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eb08f26
Update chapter-3.md
tsell89 Apr 25, 2025
fb4a4b4
Merge branch 'main' into match-new-settings-in-merge-node-for-course-2
tsell89 May 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/courses/level-two/chapter-3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,9 +35,9 @@
- [Combine all possible combinations](/integrations/builtin/core-nodes/n8n-nodes-base.merge.md#combine-by-all-possible-combinations){:target="_blank"}
- [Choose Branch](/integrations/builtin/core-nodes/n8n-nodes-base.merge.md#choose-branch){:target="_blank"}

Notice that Combine > Merge by Fields requires you enter input fields to match on. These fields should contain identical values between the data sources so n8n can properly match data together. In the **Merge node**, they're called `Input 1 Field` and `Input 2 Field`.
Notice that when using the Combine mode and the Matching Fields "Combine By" method and toggling on "Fields to Match" requires you enter input fields to match on. These fields should contain identical values between the data sources so n8n can properly match data together. In the **Merge node**, they're called `Input 1 Field` and `Input 2 Field`.

Check warning on line 38 in docs/courses/level-two/chapter-3.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[from-microsoft.Adverbs] Consider removing 'properly'.

Raw Output:
{"message": "[from-microsoft.Adverbs] Consider removing 'properly'.", "location": {"path": "docs/courses/level-two/chapter-3.md", "range": {"start": {"line": 38, "column": 245}}}, "severity": "WARNING"}

<figure><img src="/_images/courses/level-two/chapter-three/explanation_mergepropertyinput.png" alt="Property Input fields in the Merge node" style="width:100%"><figcaption align = "center"><i>Property Input fields in the Merge node</i></figcaption></figure>
https://share.tsell.link/v3D1876C

/// warning | Property Input in dot notation
If you want to reference nested values in the **Merge node** parameters `Input 1 Field` and `Input 2 Field`, you need to enter the property key in dot-notation format (as text, not as an expression).
Expand Down
Loading