diff --git a/docs/_images/courses/level-one/chapter-two/l1-c-2-hacker-news-node-parameters.png b/docs/_images/courses/level-one/chapter-two/l1-c-2-hacker-news-node-parameters.png index cdb2ffd15..d3ca88db9 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c-2-hacker-news-node-parameters.png and b/docs/_images/courses/level-one/chapter-two/l1-c-2-hacker-news-node-parameters.png differ diff --git a/docs/_images/courses/level-one/chapter-two/l1-c2-hacker-news-node-setting-configuration.png b/docs/_images/courses/level-one/chapter-two/l1-c2-hacker-news-node-setting-configuration.png index e80dc320e..ccf15cd88 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c2-hacker-news-node-setting-configuration.png and b/docs/_images/courses/level-one/chapter-two/l1-c2-hacker-news-node-setting-configuration.png differ diff --git a/docs/_images/courses/level-one/chapter-two/l1-c2-renaming-a-node-from-the-keyboard.png b/docs/_images/courses/level-one/chapter-two/l1-c2-renaming-a-node-from-the-keyboard.png index 9748b1419..b370e70e8 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c2-renaming-a-node-from-the-keyboard.png and b/docs/_images/courses/level-one/chapter-two/l1-c2-renaming-a-node-from-the-keyboard.png differ diff --git a/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-json-view-for-the-hacker-news-node.png b/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-json-view-for-the-hacker-news-node.png index 38eb44ca7..77de0116e 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-json-view-for-the-hacker-news-node.png and b/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-json-view-for-the-hacker-news-node.png differ diff --git a/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-table-view-for-the-hacker-news-node.png b/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-table-view-for-the-hacker-news-node.png index 9bf418c34..5eb657984 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-table-view-for-the-hacker-news-node.png and b/docs/_images/courses/level-one/chapter-two/l1-c2-results-in-table-view-for-the-hacker-news-node.png differ diff --git a/docs/_images/courses/level-one/chapter-two/l1-c2-successfully-executed-workflow.png b/docs/_images/courses/level-one/chapter-two/l1-c2-successfully-executed-workflow.png index 070fb3985..c0e2dc10c 100644 Binary files a/docs/_images/courses/level-one/chapter-two/l1-c2-successfully-executed-workflow.png and b/docs/_images/courses/level-one/chapter-two/l1-c2-successfully-executed-workflow.png differ diff --git a/docs/courses/level-one/chapter-2.md b/docs/courses/level-one/chapter-2.md index 3c5e739c9..f44c735be 100644 --- a/docs/courses/level-one/chapter-2.md +++ b/docs/courses/level-one/chapter-2.md @@ -46,8 +46,9 @@ n8n adds the node to your canvas and the node window opens to display its config When you add a new node to the Editor UI, the node is automatically activated. The node details will open in a window with several options: - **Parameters**: Adjust parameters to refine and control the node's functionality. +- **Settings**: Adjust settings to control the node's design and executions. - **Docs**: Open the n8n documentation for this node in a new window. -- **Settings** (gear cog icon): Adjust settings to control the node's design and executions. + /// note | Parameters vs. Settings **Parameters** are different for each node, depending on its functionality.
diff --git a/docs/hosting/scaling/queue-mode.md b/docs/hosting/scaling/queue-mode.md index e1c34c578..7ee8ecc7d 100644 --- a/docs/hosting/scaling/queue-mode.md +++ b/docs/hosting/scaling/queue-mode.md @@ -122,7 +122,7 @@ You can set up multiple worker processes. Make sure that all the worker processe * If you want access to this feature on Cloud Enterprise, [contact n8n](https://n8n-community.typeform.com/to/y9X2YuGa){:target=_blank .external-link}. /// -You can view running workers and their performance metrics in n8n by select **Settings** > **Workers**. +You can view running workers and their performance metrics in n8n by selecting **Settings** > **Workers**. ## Running n8n with queues diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md index 69ad8317e..2687bcc05 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.webhook.md @@ -126,9 +126,9 @@ Select **Add Option** to view more configuration options. The available options ## Listen for multiple HTTP methods -By default, the Webhook node accepts calls that use a single method. For example, it can accept GET or POST requests, but not both. If you want to accpet calls using multiple methods: +By default, the Webhook node accepts calls that use a single method. For example, it can accept GET or POST requests, but not both. If you want to accept calls using multiple methods: -1. Open the node **Settings** ![Settings icon](/_images/common-icons/settings.png){.off-glb}. +1. Open the node **Settings**. 1. Toggle on **Allow Multiple HTTP Methods**. 1. Return to **Parameters**. By default, the node now accepts GET and POST calls. You can add other methods in the **HTTP Methods** field. diff --git a/docs/integrations/builtin/credentials/httprequest.md b/docs/integrations/builtin/credentials/httprequest.md index 84ea498a4..25d1239e7 100644 --- a/docs/integrations/builtin/credentials/httprequest.md +++ b/docs/integrations/builtin/credentials/httprequest.md @@ -131,6 +131,6 @@ The **Generic Auth Type** > **Custom Auth** option expects JSON data to define y You can send an SSL certificate with your HTTP request. You can use this alongside other credential types. -1. In the node **Settings** ![Settings icon](/_images/common-icons/settings.png){.off-glb}, enable **SSL Certificates**. +1. In the node **Settings**, enable **SSL Certificates**. 1. On the **Parameters** tab, add the SSL credential to **Credential for SSL Certificates**. diff --git a/docs/integrations/builtin/rate-limits.md b/docs/integrations/builtin/rate-limits.md index a275eab01..a38e3df0c 100644 --- a/docs/integrations/builtin/rate-limits.md +++ b/docs/integrations/builtin/rate-limits.md @@ -30,7 +30,7 @@ There are two ways to handle rate limits in n8n's integrations: using the Retry When you enable Retry On Fail, the node automatically tries the request again if it fails the first time. 1. Open the node. -1. Select **Settings** ![Settings icon](/_images/common-icons/settings.png){.off-glb}. +1. Select **Settings**. 1. Enable the **Retry On Fail** toggle. 1. Configure the retry settings: if using this to work around rate limits, set **Wait Between Tries (ms)** to more than the rate limit. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.