From 8fc210a6b5248389c86a3009024a56d299ab38ea Mon Sep 17 00:00:00 2001 From: Ron Widler Date: Mon, 16 Jan 2023 01:37:35 +0800 Subject: [PATCH 1/2] changing some source files to relative paths (for testing) --- docs/courses/index.md | 4 ++-- docs/courses/level-one/chapter-1.md | 8 ++++---- docs/courses/level-one/chapter-2.md | 14 ++++++------- docs/courses/level-one/chapter-4.md | 20 +++++++++---------- .../level-one/chapter-5/chapter-5.1.md | 12 +++++------ .../level-one/chapter-5/chapter-5.3.md | 10 +++++----- .../level-one/chapter-5/chapter-5.4.md | 8 ++++---- docs/courses/level-one/index.md | 4 ++-- docs/workflows/connections.md | 2 +- docs/workflows/executions.md | 2 +- docs/workflows/nodes.md | 14 ++++++------- docs/workflows/sticky-notes.md | 2 +- docs/workflows/workflows.md | 8 ++++---- 13 files changed, 54 insertions(+), 54 deletions(-) diff --git a/docs/courses/index.md b/docs/courses/index.md index 87edc96bd55..19b7fd5ec49 100644 --- a/docs/courses/index.md +++ b/docs/courses/index.md @@ -8,5 +8,5 @@ These tasks can and should be automated! And you don't need advanced technical k ## Available courses -- [Level 1: Beginner course](/courses/level-one/) -- [Level 2: Intermediate course](/courses/level-two/) +- [Level 1: Beginner course](level-one/) +- [Level 2: Intermediate course](level-two/) diff --git a/docs/courses/level-one/chapter-1.md b/docs/courses/level-one/chapter-1.md index 99cf9936611..39e4045937c 100644 --- a/docs/courses/level-one/chapter-1.md +++ b/docs/courses/level-one/chapter-1.md @@ -6,7 +6,7 @@ In this lesson you will learn how to navigate the Editor UI. We will walk throug ## Getting started -First of all, you need to get n8n. There are different [ways to set up n8n](/hosting/options/){:target="_blank" .external}, choose the option that best suits your skills and needs. +First of all, you need to get n8n. There are different [ways to set up n8n](../../hosting/options/){:target="_blank" .external}, choose the option that best suits your skills and needs. !!! warning "n8n version" @@ -20,7 +20,7 @@ Next, you'll learn how to navigate the Editor UI. ## Editor UI settings -The [Editor UI](/editor-ui/){:target="_blank" .external} represents the web interface where you build [workflows](/workflows/workflows/){:target="_blank" .external}. Think of it as a canvas on which the artist in you designs automations. From the Editor UI you can access all your workflows and credentials, as well as support pages. +The [Editor UI](../../editor-ui/){:target="_blank" .external} represents the web interface where you build [workflows](../../workflows/workflows/){:target="_blank" .external}. Think of it as a canvas on which the artist in you designs automations. From the Editor UI you can access all your workflows and credentials, as well as support pages. ### Left-side panel @@ -56,7 +56,7 @@ The *canvas* is the gray grid background in the Editor UI. On the canvas, there - Buttons to zoom the canvas to fit the screen, zoom in or out of the canvas, and reset the canvas to the original resolution. - A button to *Execute Workflow*. When you click on it, all nodes on the canvas are executed. - A button with a *+* sign inside. This button opens the nodes panel. -- A button with a note icon inside. This button adds a [sticky note](/workflows/sticky-notes){:target="_blank" .external} to the canvas. +- A button with a note icon inside. This button adds a [sticky note](../../workflows/sticky-notes){:target="_blank" .external} to the canvas. - A square with a green play icon inside. This is the *Start node*. You will learn more about nodes in the [next section](#nodes).
Workflow canvas
Workflow canvas
@@ -88,7 +88,7 @@ Based on their function, nodes can be classified into two types: ### Start node -The [*Start node*](/integrations/builtin/core-nodes/n8n-nodes-base.start/){:target="_blank" .external} is the default starting point in any workflow. Every time you create a new workflow, a *Start node* will be included by default. +The [*Start node*](../../integrations/builtin/core-nodes/n8n-nodes-base.start/){:target="_blank" .external} is the default starting point in any workflow. Every time you create a new workflow, a *Start node* will be included by default. The **Start** node cannot be deleted or duplicated. If you have a workflow in which you don't use the Start node, you can remove the connection, deactivate it, and move it away from the workflow. If you need more than one Start node, you probably need to use other Trigger nodes or create separate workflows. diff --git a/docs/courses/level-one/chapter-2.md b/docs/courses/level-one/chapter-2.md index f65927c34cb..d4bc796cca2 100644 --- a/docs/courses/level-one/chapter-2.md +++ b/docs/courses/level-one/chapter-2.md @@ -36,7 +36,7 @@ Additional fields are options that you can add to certain nodes to make your req The configuration of the parameters for the *Hacker News node* should now look like this: -
Hacker News node parameters
Hacker News node parameters
+
Hacker News node parameters
Hacker News node parameters
### Settings @@ -51,7 +51,7 @@ This option will display the description note under the node in the Editor UI. The configuration of the settings for the *Hacker News node* looks like this: -
Hacker News node renaming
Hacker News node renaming
+
Hacker News node renaming
Hacker News node renaming
!!! note "Renaming a node" @@ -60,7 +60,7 @@ The configuration of the settings for the *Hacker News node* looks like this: - Select the node you want to rename and at the same time press the F2 key on your keyboard. - Double-click on the node to open the node window. Click on the name of the node in the top left corner of the window, rename it as you like, then click *Rename* to save the node under the new name. -
Renaming a node
Renaming a node from the keyboard
+
Renaming a node
Renaming a node from the keyboard
## 3. Save the workflow @@ -77,7 +77,7 @@ There are two ways in which you can save a workflow: Click on the *Execute Node* button in the top right corner of the node window. You should see 10 results in *Table* view. -
Results in Table view for the Hacker News node
Results in Table view for the Hacker News node
+
Results in Table view for the Hacker News node
Results in Table view for the Hacker News node
## Node executions @@ -87,7 +87,7 @@ Click on the *Execute Node* button in the top right corner of the node window. Y If a node executed successfully a small green circle with a number inside will appear on top of the node. -
Successfully executed workflow
Successfully executed workflow
+
Successfully executed workflow
Successfully executed workflow
If the parameters are configured correctly and everything works fine, the requested data will be displayed in the node window in *Table* and *JSON* format. You can switch between these views by selecting the one you want from the *JSON|Table* button at the top of the node window. @@ -95,7 +95,7 @@ If the parameters are configured correctly and everything works fine, the reques The *Table* view is the default. It displays the requested data in a table, where the rows are the records and the columns are the available attributes of those records. -
Results in JSON view for the Hacker News node
Results in JSON view for the Hacker News node
+
Results in JSON view for the Hacker News node
Results in JSON view for the Hacker News node
The node window displays more information about the node execution: @@ -109,7 +109,7 @@ This field displays the number of items (records) that are returned by the node !!! warning "Error in nodes" A red warning icon on a node means that the node has errors. This might happen if the node credentials are missing or incorrect, or the node parameters are not configured correctly. -
Error in nodes
Error in nodes
+
Error in nodes
Error in nodes
## Summary diff --git a/docs/courses/level-one/chapter-4.md b/docs/courses/level-one/chapter-4.md index e23b660b003..85291a320f6 100644 --- a/docs/courses/level-one/chapter-4.md +++ b/docs/courses/level-one/chapter-4.md @@ -13,21 +13,21 @@ Nathan's workflow involves sending data from the company's data warehouse to two n8n provides integrations for all these steps, so Nathan's workflow in n8n would look like this: -
Finished workflow
Nathan's workflow
+
Finished workflow
Nathan's workflow
You will build this workflow in 8 steps: -1. [Getting data from the data warehouse](/courses/level-one/chapter-5/chapter-5.1/) -2. [Inserting data into Airtable](/courses/level-one/chapter-5/chapter-5.2/) -3. [Filtering orders](/courses/level-one/chapter-5/chapter-5.3/) -4. [Setting values for processing orders](/courses/level-one/chapter-5/chapter-5.4/) -5. [Calculating booked orders](/courses/level-one/chapter-5/chapter-5.5/) -6. [Notifying the team](/courses/level-one/chapter-5/chapter-5.6/) -7. [Scheduling the workflow](/courses/level-one/chapter-5/chapter-5.7/) -8. [Activating and examining the workflow](/courses/level-one/chapter-5/chapter-5.8/) +1. [Getting data from the data warehouse](../chapter-5.1/) +2. [Inserting data into Airtable](../chapter-5.2/) +3. [Filtering orders](../chapter-5.3/) +4. [Setting values for processing orders](../chapter-5.4/) +5. [Calculating booked orders](../chapter-5.5/) +6. [Notifying the team](../chapter-5.6/) +7. [Scheduling the workflow](../chapter-5.7/) +8. [Activating and examining the workflow](../chapter-5.8/) To build this workflow, you will need credentials that are sent in the email from n8n when you sign up for this course. If you haven't signed up already, you can do it [here](https://n8n-community.typeform.com/to/PDEMrevI?typeform-source=127.0.0.1){:target="_blank" .external-link}. If you haven't received a confirmation email after signing up, [contact us](mailto:course@n8n.io).
- +
diff --git a/docs/courses/level-one/chapter-5/chapter-5.1.md b/docs/courses/level-one/chapter-5/chapter-5.1.md index 59603d0bdfd..dff30f3a45b 100644 --- a/docs/courses/level-one/chapter-5/chapter-5.1.md +++ b/docs/courses/level-one/chapter-5/chapter-5.1.md @@ -13,15 +13,15 @@ The first thing you need to do is get data from ABCorp's old data warehouse. In the previous chapter, you used a regular node for a specific app (YCombinator). However, not all apps or services have dedicated nodes – like the legacy data warehouse from Nathan's company. -Though it's not possible to directly export the data, the data warehouse has a couple of API endpoints. That's all we need to access the data via the [***HTTP Request node***](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/){:target="_blank" .external} in n8n. +Though it's not possible to directly export the data, the data warehouse has a couple of API endpoints. That's all we need to access the data via the [***HTTP Request node***](../../../integrations/builtin/core-nodes/n8n-nodes-base.httprequest/){:target="_blank" .external} in n8n. !!! note "No node for that service?" The *HTTP Request node* is one of the most versatile nodes, allowing you to make HTTP requests which can be used to query data from apps and services. You can use it to access data from apps or services that don't have a dedicated node in n8n. -Now, in your Editor UI, add an *HTTP Request node* like you learned in the lesson [Adding nodes](/courses/level-one/chapter-1/#adding-nodes). The node window will open, where you need to configure some parameters. +Now, in your Editor UI, add an *HTTP Request node* like you learned in the lesson [Adding nodes](../../chapter-1/#adding-nodes). The node window will open, where you need to configure some parameters. -
HTTP Request node
HTTP Request node
+
HTTP Request node
HTTP Request node
In the left panel, select: @@ -48,15 +48,15 @@ In the *Connection* tab, fill in the two fields: Click on the *Save* button in the top right corner to save your credentials. Your *Credentials Connection* window should look like this: -
HTTP Request node credentials
HTTP Request node credentials
+
HTTP Request node credentials
HTTP Request node credentials
Now click the *Save* button in the bottom right corner of the window. In the *HTTP Request node* window, click the *Execute Node* button. The result of the HTTP request should look like this: -
HTTP Request node window
HTTP Request node window
+
HTTP Request node window
HTTP Request node window
-This view should be familiar to you from the [Hacker News mini-workflow](/courses/level-one/chapter-2/). This is the data from ABCorp's data warehouse that Nathan needs to work with. This data set includes sales information of 30 customers with 5 features: +This view should be familiar to you from the [Hacker News mini-workflow](../../chapter-2/). This is the data from ABCorp's data warehouse that Nathan needs to work with. This data set includes sales information of 30 customers with 5 features: - *orderID:* The unique id of each order. - *customerID:* The unique id of each customer. diff --git a/docs/courses/level-one/chapter-5/chapter-5.3.md b/docs/courses/level-one/chapter-5/chapter-5.3.md index 3d791c55b39..1c084d64e5d 100644 --- a/docs/courses/level-one/chapter-5/chapter-5.3.md +++ b/docs/courses/level-one/chapter-5/chapter-5.3.md @@ -4,10 +4,10 @@ In this step of the workflow you will learn how to filter data using conditional To insert only processing orders into Airtable we need to filter our data by *orderStatus*. Basically, we want to tell the program that _if_ the *orderStatus* is processing, _then_ insert all records with this status into Airtable; _else_, i.e. if the *orderStatus* is not *processing*, calculate the sum of all orders with the other *orderStatus (booked)*. -This if-then-else command is conditional logic. In n8n workflows, conditional logic can be implemented with the [**IF node**](/integrations/builtin/core-nodes/n8n-nodes-base.if/){:target="_blank" .external}, which splits a workflow conditionally based on comparison operations. +This if-then-else command is conditional logic. In n8n workflows, conditional logic can be implemented with the [**IF node**](../../../integrations/builtin/core-nodes/n8n-nodes-base.if/){:target="_blank" .external}, which splits a workflow conditionally based on comparison operations. !!! note "IF vs Switch" - If you need to filter data on more than two conditional routes that are possible with the *IF* node (true and false), use the [*Switch node*](/integrations/builtin/core-nodes/n8n-nodes-base.switch/){:target="_blank" .external}. The *Switch node* is similar to the *IF* node, but supports up to four conditional routes. + If you need to filter data on more than two conditional routes that are possible with the *IF* node (true and false), use the [*Switch node*](../../../integrations/builtin/core-nodes/n8n-nodes-base.switch/){:target="_blank" .external}. The *Switch node* is similar to the *IF* node, but supports up to four conditional routes. Back to your workflow, remove the connection between the *HTTP Request* node and the *Airtable* node. Add an *IF* node connected to the *HTTP Request* node. @@ -21,7 +21,7 @@ To select this value, click the **Expression** tab on the right side of the Valu An expression is a string of characters and symbols in a programming language that represents a value depending upon its input. In n8n workflows, you can use expressions in a node to refer to another node for input data. In our example, the IF node references the data output by the HTTP Request node. -
Expression Editor in the IF node
Expression Editor in the IF node
+
Expression Editor in the IF node
Expression Editor in the IF node
- *Operation:* equal - *Value 2:* processing @@ -32,13 +32,13 @@ To select this value, click the **Expression** tab on the right side of the Valu Now execute the IF node and have a look at the resulting data, which should look like this: -
IF node
IF node
+
IF node
IF node
Next, we want to insert this data into Airtable. You already know how to do this from the previous chapter where we inserted all data into the *orders* table. At this stage, your workflow should look like this: -
Workflow with the IF node
Workflow with the IF node
+
Workflow with the IF node
Workflow with the IF node
## What's next? diff --git a/docs/courses/level-one/chapter-5/chapter-5.4.md b/docs/courses/level-one/chapter-5/chapter-5.4.md index 69ed17b6810..a534f03bad9 100644 --- a/docs/courses/level-one/chapter-5/chapter-5.4.md +++ b/docs/courses/level-one/chapter-5/chapter-5.4.md @@ -4,7 +4,7 @@ In this step of the workflow you will learn how to select and set data before tr The next step in Nathan's workflow is to insert the *employeeName* and *orderId* of all *processing* orders into Airtable. -For this, you need to use the [**Set node**](/integrations/builtin/core-nodes/n8n-nodes-base.set/){:target="_blank" .external}, which allows you to select and set the data you want to be transferred from one app/service to another. +For this, you need to use the [**Set node**](../../../integrations/builtin/core-nodes/n8n-nodes-base.set/){:target="_blank" .external}, which allows you to select and set the data you want to be transferred from one app/service to another. !!! note "Set node" The *Set* node can set completely new data as well as overwrite data that already exists. This node is crucial in workflows which expect incoming data from previous nodes, such as when inserting values into spreadsheets or databases. @@ -25,9 +25,9 @@ In your workflow, add a new *Set* node between the *IF* node and the *Airtable* After setting the two values click on *Execute Node* and you should see the following results: -
Set node
Set node
+
Set node
Set node
-Next, we need to insert these values into Airtable. Go to your Airtable account and add a new table called *processingOrders* with two columns, *orderId* and *employeeName*, just like you learned in the lesson [Inserting data into Airtable](/courses/level-one/chapter-5/chapter-5.2/). +Next, we need to insert these values into Airtable. Go to your Airtable account and add a new table called *processingOrders* with two columns, *orderId* and *employeeName*, just like you learned in the lesson [Inserting data into Airtable](../chapter-5.2/). Remember to update the Airtable node configuration to point to this new table. @@ -35,7 +35,7 @@ Once that's done, execute the *Airtable* node in the workflow and you should see At this stage, it looks like this: -
Workflow with the Set node
Workflow with the Set node
+
Workflow with the Set node
Workflow with the Set node
## What's next? diff --git a/docs/courses/level-one/index.md b/docs/courses/level-one/index.md index 5c48c5edb34..712772d5dee 100644 --- a/docs/courses/level-one/index.md +++ b/docs/courses/level-one/index.md @@ -44,7 +44,7 @@ Completing the course should take around **two hours**. You do not have to compl There are two milestones in this course that test your knowledge of what you have learned in the lessons: -- [x] Building the [main workflow](/courses/level-one/chapter-5/chapter-5.1/){:target="_blank" .external} +- [x] Building the [main workflow](level-one/chapter-5/chapter-5.1/){:target="_blank" .external} - [x] Passing the [quiz](https://n8n-community.typeform.com/to/JMoBXeGA){:target="_blank" .external-link} at the end of the course You can always **check your progress** throughout the course by entering your unique ID [here](https://internal.users.n8n.cloud/webhook/course-level-1/verify){:target="_blank" .external}. @@ -52,5 +52,5 @@ You can always **check your progress** throughout the course by entering your un If you successfully complete the milestones above, you will get [**a badge and an avatar**](https://community.n8n.io/badges/104/completed-n8n-course-level-1){:target="_blank" .external-link} in your forum profile. You can then share your profile and course verification ID to showcase your n8n skills to others.
- +
diff --git a/docs/workflows/connections.md b/docs/workflows/connections.md index 6f6ce569243..99162f5c31b 100644 --- a/docs/workflows/connections.md +++ b/docs/workflows/connections.md @@ -12,4 +12,4 @@ To create a connection between two nodes, click on the grey dot on the right sid An [IF node](/integrations/builtin/core-nodes/n8n-nodes-base.if/) has two connections to different nodes: one for when the statement is true and one for when the statement is false. -![Connection](/_images/workflows/connections/Connection_ifnode.gif) +![Connection](../../_images/workflows/connections/Connection_ifnode.gif) diff --git a/docs/workflows/executions.md b/docs/workflows/executions.md index ff95ba10853..5495cabe17b 100644 --- a/docs/workflows/executions.md +++ b/docs/workflows/executions.md @@ -8,7 +8,7 @@ An execution is a single run of a workflow. To browse all executions: -Select **Executions** ![Executions menu icon](/_images/common-icons/executions-menu.png) in the left menu to view your executions history. n8n opens the **Workflow Executions** modal. You can then open and view individual executions. +Select **Executions** ![Executions menu icon](../../_images/common-icons/executions-menu.png) in the left menu to view your executions history. n8n opens the **Workflow Executions** modal. You can then open and view individual executions. To view executions for a single workflow: diff --git a/docs/workflows/nodes.md b/docs/workflows/nodes.md index c335b6d27b9..e43b065f046 100644 --- a/docs/workflows/nodes.md +++ b/docs/workflows/nodes.md @@ -27,19 +27,19 @@ If an application you need does not have a dedicated Node yet, you can access th Regular nodes perform an action, like fetching data or creating an entry in a calendar. Regular nodes are named for the application they represent and are listed under Regular Nodes in the Editor UI. -![Regular Nodes](/_images/workflows/nodes/Regular_nodes.png) +![Regular Nodes](../../_images/workflows/nodes/Regular_nodes.png) ### Example A [Google Sheets node](/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/) can be used to retrieve or write data to a Google Sheet. -![Sheets_node](/_images/workflows/nodes/Google_sheets.png) +![Sheets_node](../../_images/workflows/nodes/Google_sheets.png) ## Trigger nodes Trigger nodes start workflows and supply the initial data. -![Trigger_nodes](/_images/workflows/nodes/Trigger_nodes.png) +![Trigger_nodes](../../_images/workflows/nodes/Trigger_nodes.png) Trigger nodes can be app or core nodes. @@ -47,7 +47,7 @@ Trigger nodes can be app or core nodes. * **App Trigger nodes** start the workflow when an event happens in an app. App Trigger nodes are named like the application they represent followed by "Trigger" and are listed under Trigger Nodes in the Editor. For example, a [Telegram trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.telegramtrigger/) can be used to trigger a workflow when a message is sent in a Telegram chat. -![Telegram trigger](/_images/workflows/nodes/telegram_trigger.png) +![Telegram trigger](../../_images/workflows/nodes/telegram_trigger.png) ## Node settings @@ -61,7 +61,7 @@ The node operations are illustrated with icons that appear on top of the node wh * **Copy**: Duplicate the selected node * **Play**: Run the selected node -![Node settings](/_images/workflows/nodes/Node_settings.gif) +![Node settings](../../_images/workflows/nodes/Node_settings.gif) To access the node parameters and settings, double-click on the node. @@ -80,11 +80,11 @@ The node settings allow you to configure the look and execution of the node. The * **Retry On Fail**: If active, the node tries to execute a failed attempt multiple times until it succeeds * **Continue On Fail**: If active, the workflow continues even if the execution of the node fails. When this happens, the node passes along input data from previous nodes, so the workflow should account for unexpected output data. -![Node parameters](/_images/workflows/nodes/Node_parameters.gif) +![Node parameters](../../_images/workflows/nodes/Node_parameters.gif) If a node is not correctly configured or is missing some required information, a **warning sign** is displayed on the top right corner of the node. To see what parameters are incorrect, double-click on the node and have a look at fields marked with red and the error message displayed in the respective warning symbol. -![Node error](/_images/workflows/nodes/Node_error.gif) +![Node error](../../_images/workflows/nodes/Node_error.gif) ## Pausing nodes diff --git a/docs/workflows/sticky-notes.md b/docs/workflows/sticky-notes.md index f6bf50346ac..865b97f7246 100644 --- a/docs/workflows/sticky-notes.md +++ b/docs/workflows/sticky-notes.md @@ -8,7 +8,7 @@ Sticky Notes allow you to annotate and comment on your workflows. n8n recommends using Sticky Notes heavily, especially on template workflows, to help other users understand your workflow. -![Screenshot of a basic workflow with an example sticky note](/_images/workflows/stickies/example-sticky-note.png) +![Screenshot of a basic workflow with an example sticky note](../../_images/workflows/stickies/example-sticky-note.png) ## Create a Sticky Note diff --git a/docs/workflows/workflows.md b/docs/workflows/workflows.md index 9d7c9c4a452..6b618cf4cf4 100644 --- a/docs/workflows/workflows.md +++ b/docs/workflows/workflows.md @@ -8,7 +8,7 @@ A workflow is a collection of nodes connected together to automate a process. A workflow can be started manually (with the Start node) or by Trigger nodes. When a workflow is started, it executes all the active and connected nodes. The workflow execution ends when all the nodes have processed their data. You can view your workflow executions in the **Execution log**, which can be helpful for debugging. -![Workflow](/_images/workflows/workflows/Execute_workflow.gif) +![Workflow](../../_images/workflows/workflows/Execute_workflow.gif) ## Activating a workflow @@ -28,7 +28,7 @@ You can export a workflow as a JSON file in two ways: * **Copy-Paste**: Select all the workflow nodes in the Editor UI, copy them (`Ctrl + c` or `cmd +c`), then paste them (`Ctrl + v` or `cmd + v`) in your desired file. To select all nodes, or a group of nodes, click and drag: - ![Select a group of nodes](/_images/workflows/workflows/selectingnodes.gif) + ![Select a group of nodes](../../_images/workflows/workflows/selectingnodes.gif) You can import JSON files as workflows in two ways: @@ -39,7 +39,7 @@ You can import JSON files as workflows in two ways: On each workflow, it's possible to set some custom settings and overwrite some of the global default settings from the **Workflow** > **Settings** menu. -![The Workflow Setting modal.](/_images/workflows/workflows/workflow_settings.png) +![The Workflow Setting modal.](../../_images/workflows/workflows/workflow_settings.png) The following settings are available: @@ -100,4 +100,4 @@ You can submit your own workflows to n8n's template library. * **Description**: tell users what the workflow does. Include any configuration or setup steps. * **Workflow code**: copy in the workflow JSON that you downloaded. 5. Click **Publish Workflow to Share**. n8n reviews all workflows before publishing them. ---> \ No newline at end of file +--> From 820553b24450eceafc08917a55383113705a809f Mon Sep 17 00:00:00 2001 From: Ron Widler Date: Mon, 16 Jan 2023 02:16:57 +0800 Subject: [PATCH 2/2] fix absolute paths --- docs/workflows/index.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/workflows/index.md b/docs/workflows/index.md index 0f426b3a892..ced144ced36 100644 --- a/docs/workflows/index.md +++ b/docs/workflows/index.md @@ -6,7 +6,7 @@ description: "Learn about the key components of automation in n8n." Learn about the key components of an automation in n8n: -* [Workflows](/workflows/workflows/) -* [Connections](/workflows/connections/) -* [Nodes](/workflows/nodes/) -* [Items](/workflows/items/) +* [Workflows](workflows/) +* [Connections](connections/) +* [Nodes](nodes/) +* [Items](items/)