diff --git a/docs/courses/level-one/chapter-5/chapter-5.5.md b/docs/courses/level-one/chapter-5/chapter-5.5.md index a99b7066b..c21edeb2d 100644 --- a/docs/courses/level-one/chapter-5/chapter-5.5.md +++ b/docs/courses/level-one/chapter-5/chapter-5.5.md @@ -29,15 +29,15 @@ In n8n, the data that is passed between nodes is an array of objects with the fo // Any kind of JSON data is allowed. So arrays and the data being deeply nested is fine. json: { // The actual data n8n operates on (required) // This data is only an example it could be any kind of JSON data - alfa: 'bravo', - charlie: { - delta: 1 + apple: 'beets', + carrot: { + dill: 1 } }, // Binary data of item. The most items in n8n do not contain any (optional) binary: { - // The key-name "alfa" is only an example. Any kind of key-name is possible. - alfa: { + // The key-name "apple" is only an example. Any kind of key-name is possible. + apple: { data: '....', // Base64 encoded binary data (required) mimeType: 'image/png', // Optional but should be set if possible (optional) fileExtension: 'png', // Optional but should be set if possible (optional) diff --git a/docs/data/data-structure.md b/docs/data/data-structure.md index a212c49d8..b06ff73a5 100644 --- a/docs/data/data-structure.md +++ b/docs/data/data-structure.md @@ -9,16 +9,16 @@ In n8n, all data passed between nodes is an array of objects. It has the followi // Wrap each item in another object, with the key 'json' "json": { // Example data - "alfa": "bravo", - "charlie": { - "delta": 1 + "apple": "beets", + "carrot": { + "dill": 1 } }, // For binary data: // Wrap each item in another object, with the key 'binary' "binary": { // Example data - "alfa": { + "apple": { "data": "....", // Base64 encoded binary data (required) "mimeType": "image/png", // Best practice to set if possible (optional) "fileExtension": "png", // Best practice to set if possible (optional)