diff --git a/.vale.ini b/.vale.ini index a2ffb82d7..13e60b00e 100644 --- a/.vale.ini +++ b/.vale.ini @@ -4,4 +4,5 @@ Vocab = default [*.md] BasedOnStyles = alex, write-good, Microsoft, n8n-styles, Vale alex.Profanity = NO +BlockIgnores = (\**Release date:\**.*), (\### Contributors.*#) TokenIgnores = (\-\-8\<\-\- \".*\") diff --git a/docs/_extra/publicapi.yml b/docs/_extra/publicapi.yml index 1a82ca72c..e624e28c6 100644 --- a/docs/_extra/publicapi.yml +++ b/docs/_extra/publicapi.yml @@ -823,7 +823,7 @@ components: risk: credentials sections: - title: Credentials not used in any workflow - description: These credentials are not used in any workflow. Keeping unused credentials in your instance is an unneeded security risk. + description: These credentials aren't used in any workflow. Keeping unused credentials in your instance is an unneeded security risk. recommendation: Consider deleting these credentials if you no longer need them. location: - kind: credential @@ -853,7 +853,7 @@ components: - title: Nodes that interact with the filesystem description: This node reads from and writes to any accessible file in the host filesystem. Sensitive file content may be manipulated through a node operation. recommendation: Consider protecting any sensitive files in the host filesystem - or refactoring the workflow so that it does not require host filesystem interaction.: null + or refactoring the workflow so that it doesn'trequire host filesystem interaction.: null location: - kind: node workflowId: '1' @@ -867,7 +867,7 @@ components: risk: nodes sections: - title: Community nodes - description: This node is sourced from the community. Community nodes are not vetted by the n8n team and have full access to the host system. + description: This node is sourced from the community. Community nodes aren't vetted by the n8n team and have full access to the host system. recommendation: Consider reviewing the source code in any community nodes installed in this n8n instance and uninstalling any community nodes no longer used.: null location: @@ -880,7 +880,7 @@ components: risk: execution sections: - title: Unprotected webhooks in instance - description: These webhook nodes have the "Authentication" field set to "None" and are not directly connected to a node to validate the payload. Every unprotected webhook allows your workflow to be called by any third party who knows the webhook URL. + description: These webhook nodes have the "Authentication" field set to "None" and aren't directly connected to a node to validate the payload. Every unprotected webhook allows your workflow to be called by any third party who knows the webhook URL. recommendation: Consider setting the "Authentication" field to an option other than "None" or validating the payload with one of the following nodes.: null location: diff --git a/docs/api/v1/openapi.yml b/docs/api/v1/openapi.yml index fd5180c66..a45478b45 100644 --- a/docs/api/v1/openapi.yml +++ b/docs/api/v1/openapi.yml @@ -823,7 +823,7 @@ components: risk: credentials sections: - title: Credentials not used in any workflow - description: These credentials are not used in any workflow. Keeping unused credentials in your instance is an unneeded security risk. + description: These credentials aren't used in any workflow. Keeping unused credentials in your instance is an unneeded security risk. recommendation: Consider deleting these credentials if you no longer need them. location: - kind: credential @@ -853,7 +853,7 @@ components: - title: Nodes that interact with the filesystem description: This node reads from and writes to any accessible file in the host filesystem. Sensitive file content may be manipulated through a node operation. recommendation: Consider protecting any sensitive files in the host filesystem - or refactoring the workflow so that it does not require host filesystem interaction.: null + or refactoring the workflow so that it doesn'trequire host filesystem interaction.: null location: - kind: node workflowId: '1' @@ -867,7 +867,7 @@ components: risk: nodes sections: - title: Community nodes - description: This node is sourced from the community. Community nodes are not vetted by the n8n team and have full access to the host system. + description: This node is sourced from the community. Community nodes aren't vetted by the n8n team and have full access to the host system. recommendation: Consider reviewing the source code in any community nodes installed in this n8n instance and uninstalling any community nodes no longer used.: null location: @@ -880,7 +880,7 @@ components: risk: execution sections: - title: Unprotected webhooks in instance - description: These webhook nodes have the "Authentication" field set to "None" and are not directly connected to a node to validate the payload. Every unprotected webhook allows your workflow to be called by any third party who knows the webhook URL. + description: These webhook nodes have the "Authentication" field set to "None" and aren't directly connected to a node to validate the payload. Every unprotected webhook allows your workflow to be called by any third party who knows the webhook URL. recommendation: Consider setting the "Authentication" field to an option other than "None" or validating the payload with one of the following nodes.: null location: diff --git a/docs/choose-n8n/faircode-license.md b/docs/choose-n8n/faircode-license.md index 27eabacf9..eab88ea1e 100644 --- a/docs/choose-n8n/faircode-license.md +++ b/docs/choose-n8n/faircode-license.md @@ -78,7 +78,7 @@ Provided you are using n8n for internal business purposes, and not making n8n av Any code you contribute on GitHub is subject to GitHub's [terms of use](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#d-user-generated-content). In simple terms, this means you own, and are responsible for, anything you contribute, but that you grant other GitHub users certain rights to use this code. When you contribute code to a repository containing notice of a license, you license the code under the same terms. -n8n asks every contributor to sign our [Contributor License Agreement](https://github.com/n8n-io/n8n/blob/master/CONTRIBUTOR_LICENSE_AGREEMENT.md). In addition to the above, this gives n8n the ability to change its license without seeking additional permission. It also means you are not liable for your contributions (e.g. in case they cause damage to someone else's business). +n8n asks every contributor to sign our [Contributor License Agreement](https://github.com/n8n-io/n8n/blob/master/CONTRIBUTOR_LICENSE_AGREEMENT.md). In addition to the above, this gives n8n the ability to change its license without seeking additional permission. It also means you aren't liable for your contributions (e.g. in case they cause damage to someone else's business). It's easy to get started contributing code to n8n [here](https://github.com/n8n-io), and we've listed broader ways of participating in our community [here](https://docs.n8n.io/reference/contributing.html). @@ -99,7 +99,7 @@ That means you are now free to offer commercial consulting or support services ( ### Is n8n open source? -Although n8n's source code is available under the Sustainable Use License, according to the [Open Source Initiative](https://opensource.org/) (OSI), open source licenses cannot include limitations on use, so we do not call ourselves open source. In practice, n8n offers most users many of the same benefits as OSI-approved open source. +Although n8n's source code is available under the Sustainable Use License, according to the [Open Source Initiative](https://opensource.org/) (OSI), open source licenses can't include limitations on use, so we do not call ourselves open source. In practice, n8n offers most users many of the same benefits as OSI-approved open source. We coined the term ['fair-code'](https://faircode.io/) as a way of describing our licensing model, and the model of other companies who are source-available, but restrict commercial use of their source code. diff --git a/docs/code/builtin/index.md b/docs/code/builtin/index.md index 20a906028..616d0643c 100644 --- a/docs/code/builtin/index.md +++ b/docs/code/builtin/index.md @@ -8,7 +8,7 @@ contentType: overview n8n provides built-in methods and variables for working with data and accessing n8n data. This section provides a reference of available methods and variables for use in expressions, with a short description. /// note | Availability in the expressions editor and the Code node -Some methods and variables aren't available in the Code node. These are noted in the documentation. +Some methods and variables aren't available in the Code node. These aren'ted in the documentation. All data transformation functions are only available in the expressions editor. /// diff --git a/docs/code/cookbook/expressions/check-incoming-data.md b/docs/code/cookbook/expressions/check-incoming-data.md index 9972bf4d6..c337d5993 100644 --- a/docs/code/cookbook/expressions/check-incoming-data.md +++ b/docs/code/cookbook/expressions/check-incoming-data.md @@ -4,7 +4,7 @@ contentType: howto # Check incoming data -At times, you may want to check the incoming data. If the incoming data doesn't satisfy a condition, you may want to return a different value. For example, you want to check if a variable from the previous node is empty and return a string if it is empty. Use the following code snippet to return `not found` if the variable is empty. +At times, you may want to check the incoming data. If the incoming data doesn't satisfy a condition, you may want to return a different value. For example, you want to check if a variable from the previous node is empty and return a string if it's empty. Use the following code snippet to return `not found` if the variable is empty. ```js {{$json["variable_name"]? $json["variable_name"] :"not found"}} diff --git a/docs/code/expressions.md b/docs/code/expressions.md index dd4343852..7f939a8aa 100644 --- a/docs/code/expressions.md +++ b/docs/code/expressions.md @@ -87,7 +87,7 @@ However, the first example isn't a valid n8n expression: ```js // This example is split over multiple lines for readability -// It is still invalid when formatted as a single line +// It's still invalid when formatted as a single line {{ function example() { let end = DateTime.fromISO('2017-03-13'); diff --git a/docs/courses/level-one/chapter-1.md b/docs/courses/level-one/chapter-1.md index 151a246a3..7f167c4c1 100644 --- a/docs/courses/level-one/chapter-1.md +++ b/docs/courses/level-one/chapter-1.md @@ -16,7 +16,7 @@ The first step is setting up n8n. There are two ways you can do this: For more details on the different ways to set up n8n, see our [platforms documentation](/choose-n8n/#platforms){:target="_blank" .external} /// warning | n8n version -This course was developed on n8n version 1.15.0. In other versions, some of the user interface might look different, but the core functionality should not be impacted. +This course was developed on n8n version 1.15.0. In other versions, some of the user interface might look different, but the core functionality shouldn't be impacted. /// Once you have n8n running, open the Editor UI in a browser window. It should look like this: diff --git a/docs/courses/level-one/chapter-2.md b/docs/courses/level-one/chapter-2.md index 38dd1fa41..9802e09d2 100644 --- a/docs/courses/level-one/chapter-2.md +++ b/docs/courses/level-one/chapter-2.md @@ -48,7 +48,7 @@ The *Settings* section includes several options for node design and executions. - *Notes:* Get the 10 latest articles /// note | Node notes -It is often helpful, especially for complex or shared workflows, to add a short description in the node about what it does. +It's often helpful, especially for complex or shared workflows, to add a short description in the node about what it does. /// - *Display note in flow?:* toggle to true
This option will display the description note under the node in the Editor UI. @@ -108,11 +108,11 @@ The node window displays more information about the node execution: This field displays the number of items (records) that are returned by the node request. In our case, it's expected to be 10, since this is the limit we set in the node. But if you don't set a limit, it's useful to see how many records are actually returned. - Next to the *Items* information, notice a small grey *i* icon. If you hover on it, you'll get two more pieces of information: ***Start Time*** (when the node execution started) and ***Execution Time*** (how long it took for the node to return the results from the moment it started executing). *Start Time* and *Execution Time* can provide insights into the performance of each individual node. -- Under the node name beside the **Parameters** tab, there is a link to the node's **Docs**. Check it out if you run into trouble or are not sure how to configure the node's parameters. +- Under the node name beside the **Parameters** tab, there is a link to the node's **Docs**. Check it out if you run into trouble or aren't sure how to configure the node's parameters. /// 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. +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 aren't configured correctly. ///
Error in nodes
Error in nodes
diff --git a/docs/courses/level-one/chapter-5/chapter-5.2.md b/docs/courses/level-one/chapter-5/chapter-5.2.md index 8fd01d15f..f2ccd14ee 100644 --- a/docs/courses/level-one/chapter-5/chapter-5.2.md +++ b/docs/courses/level-one/chapter-5/chapter-5.2.md @@ -18,7 +18,7 @@ If we are going to insert data into Airtable, we first need to set up a table th
Create an Airtable base
Create an Airtable base
3. In the beginner course base you have by default a *Table 1* with four fields: *Name, Notes, Assignee, and Status*. -These fields are not relevant for us since they are not in our orders data set. This brings us to the next point: the names of the fields in Airtable have to match the names of the columns in the node result. +These fields aren't relevant for us since they aren't in our orders data set. This brings us to the next point: the names of the fields in Airtable have to match the names of the columns in the node result. - Replace the four default table fields with the five column names from the data set, selecting `Number` field type for orderID, customerID, and orderPrice, and `Single line text` for employeeName and orderStatus. - Delete the 3 blank rows created by default. - Also, rename the table from *Table 1* to *orders* to make it easier to identify. diff --git a/docs/courses/level-two/chapter-2.md b/docs/courses/level-two/chapter-2.md index 5af124415..ca90fe96f 100644 --- a/docs/courses/level-two/chapter-2.md +++ b/docs/courses/level-two/chapter-2.md @@ -89,7 +89,7 @@ If you need to convert date and time data to different formats, and calculate da You can also schedule workflows to run at a specific time, interval, or duration, using the [Schedule Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.scheduletrigger/) node. -In some cases, you might need to pause the workflow execution. This might be necessary, for example, if you know that a service doesn't process the data instantly or it is generally slower, so you don't want the incomplete data to be passed to the next node. In this case, you can use the [Wait node](/integrations/builtin/core-nodes/n8n-nodes-base.wait/) after the node that you want to delay. The Wait node pauses the workflow execution and resumes it at a specific time, after a time interval, or on a webhook call. +In some cases, you might need to pause the workflow execution. This might be necessary, for example, if you know that a service doesn't process the data instantly or it's generally slower, so you don't want the incomplete data to be passed to the next node. In this case, you can use the [Wait node](/integrations/builtin/core-nodes/n8n-nodes-base.wait/) after the node that you want to delay. The Wait node pauses the workflow execution and resumes it at a specific time, after a time interval, or on a webhook call. ### Exercise @@ -268,7 +268,7 @@ Build a workflow that adds five days to an input date. Then, if the calculated d ## Binary data -So far, you have mainly worked with text data. But what if you want to process data that is not text? For example, images or PDF files. This is binary data, as it is represented in the binary numeral system. In this form, binary data doesn't offer you useful information, so it needs to be converted into a readable form. +So far, you have mainly worked with text data. But what if you want to process data that is not text? For example, images or PDF files. This is binary data, as it's represented in the binary numeral system. In this form, binary data doesn't offer you useful information, so it needs to be converted into a readable form. In n8n, you can process binary data with the following nodes: diff --git a/docs/courses/level-two/chapter-3.md b/docs/courses/level-two/chapter-3.md index 7ba7d7242..1bc9a806d 100644 --- a/docs/courses/level-two/chapter-3.md +++ b/docs/courses/level-two/chapter-3.md @@ -17,7 +17,7 @@ Merging data can involve: - Synchronizing data between multiple systems. For example, removing duplicate data, or updating data in one system when it changes in another. /// note | One-way vs. two-way sync -In a one-way sync, data is synchronized in one direction. One system serves as the single source of truth. When information changes in that main system, it automatically changes in the secondary system; but if information changes in the secondary system, the changes are not reflected in the main system. +In a one-way sync, data is synchronized in one direction. One system serves as the single source of truth. When information changes in that main system, it automatically changes in the secondary system; but if information changes in the secondary system, the changes aren't reflected in the main system. In a two-way sync, data is synchronized in both directions (between both systems). When information changes in either of the two systems, it automatically changes in the other one as well. @@ -83,7 +83,7 @@ To [create a loop in an n8n workflow](/flow-logic/looping/#using-loops-in-n8n){: If you need to process large incoming data, execute the Code node multiple times, or avoid API rate limits, it's best to split the data into batches (groups) and process these batches. You can do this with the [Loop Over Items node](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/){:target="_blank" .external}. This node splits input data into a specified batch size and, with each iteration, returns a predefined amount of data. /// warning | Execution of Loop Over Items node -The Loop Over Items node stops executing after all the incoming items get divided into batches and passed on to the next node in the workflow, so it is not necessary to add an IF node to stop the loop. +The Loop Over Items node stops executing after all the incoming items get divided into batches and passed on to the next node in the workflow, so it's not necessary to add an IF node to stop the loop. /// ### Exercise diff --git a/docs/courses/level-two/chapter-4.md b/docs/courses/level-two/chapter-4.md index df74c50ef..eb777630d 100644 --- a/docs/courses/level-two/chapter-4.md +++ b/docs/courses/level-two/chapter-4.md @@ -113,7 +113,7 @@ Throwing exceptions with the Stop and Error node is useful for verifying the dat If you are working with data from a third-party service, you may come across problems such as: wrongly formatted JSON output, data with the wrong type (for example, numeric data that has a non-numeric value), missing values, or errors from remote servers. -Though this kind of invalid data might not cause the workflow to fail right away, it could cause problems later on, and then it can become difficult to track the source error. This is why it is better to throw an error at the time you know there might be a problem. +Though this kind of invalid data might not cause the workflow to fail right away, it could cause problems later on, and then it can become difficult to track the source error. This is why it's better to throw an error at the time you know there might be a problem.
Stop and Error node with error message
/// diff --git a/docs/hosting/logging-monitoring/logging.md b/docs/hosting/logging-monitoring/logging.md index 26b7138da..ef6ed769b 100644 --- a/docs/hosting/logging-monitoring/logging.md +++ b/docs/hosting/logging-monitoring/logging.md @@ -91,11 +91,11 @@ Logger.verbose(`Executing hook (workflowExecuteBefore, hookFunctionsPush)`, {exe When creating new loggers, some useful standards to keep in mind are: -- Craft log messages to be as easily human-readable as possible. For example, always wrap names in quotes. +- Craft log messages to be as human-readable as possible. For example, always wrap names in quotes. - Duplicating information in the log message and metadata, like workflow name in the above example, can be useful as messages are easier to search and metadata enables easier filtering. - Include multiple IDs (e.g. executionId, workflowId, and sessionId) throughout all logs. - Use node types instead of node names (or both) as this is more consistent, and so easier to search. ## Front-end logs -As of now, front-end logs are not available. Using `Logger` or `LoggerProxy` would yield errors in the `editor-ui` package. This functionality will get implemented in the future versions. +As of now, front-end logs aren't available. Using `Logger` or `LoggerProxy` would yield errors in the `editor-ui` package. This functionality will get implemented in the future versions. diff --git a/docs/hosting/logging-monitoring/monitoring.md b/docs/hosting/logging-monitoring/monitoring.md index f2df40b6c..48a5f3566 100644 --- a/docs/hosting/logging-monitoring/monitoring.md +++ b/docs/hosting/logging-monitoring/monitoring.md @@ -9,7 +9,7 @@ There are two API endpoints you can call to check the status of your instance: ` ## healthz -The `/healthz` endpoint returns a standard HTTP status code. 200 indicates the instance is reachable. It is available for both self-hosted and Cloud users. +The `/healthz` endpoint returns a standard HTTP status code. 200 indicates the instance is reachable. It's available for both self-hosted and Cloud users. Access the endpoint: diff --git a/docs/hosting/scaling/memory-errors.md b/docs/hosting/scaling/memory-errors.md index 515e9d3b4..3b0162c94 100644 --- a/docs/hosting/scaling/memory-errors.md +++ b/docs/hosting/scaling/memory-errors.md @@ -52,4 +52,4 @@ However, as long as your sub-workflow does the heavy lifting for each batch and ### Increase old memory -This applies to self-hosting n8n. When encountering **JavaScript heap out of memory** errors, it is often useful to allocate additional memory to the old memory section of the V8 JavaScript engine. To do this, set the appropriate [V8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes){:target=_blank .external-link} `--max-old-space-size=SIZE` either through the CLI or through the `NODE_OPTIONS` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions){:target=_blank .external-link}. +This applies to self-hosting n8n. When encountering **JavaScript heap out of memory** errors, it's often useful to allocate additional memory to the old memory section of the V8 JavaScript engine. To do this, set the appropriate [V8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes){:target=_blank .external-link} `--max-old-space-size=SIZE` either through the CLI or through the `NODE_OPTIONS` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions){:target=_blank .external-link}. diff --git a/docs/index.md b/docs/index.md index 59d7e3608..9fe746108 100644 --- a/docs/index.md +++ b/docs/index.md @@ -8,7 +8,7 @@ hide: This is the documentation for [n8n](https://n8n.io/), a [fair-code](http://faircode.io) licensed node-based workflow automation tool. -It covers everything from setup to usage and development. It is a work in progress and all [contributions](/contributing/) are welcome. +It covers everything from setup to usage and development. It's a work in progress and all [contributions](/contributing/) are welcome. ## Where to start diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md index 761881b2e..c8d0e9f50 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.getresponse.md @@ -58,7 +58,7 @@ In the screenshot below, you will notice that the node retrieves all the contact ### 3. IF node -This node will check if a contact belongs to the `n8n` campaign or not. If a contact does not belong to the `n8n` campaign, it will return true otherwise false. Create a campaign in GetResponse if you don't already have one. +This node will check if a contact belongs to the `n8n` campaign or not. If a contact doesn'tbelong to the `n8n` campaign, it will return true otherwise false. Create a campaign in GetResponse if you don't already have one. 1. Click on ***Add Condition*** and select 'String'. 2. Click on the gears icon next to the ***Value 1*** field and click on ***Add Expression***. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin.md index 7b5219376..d19280093 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.gsuiteadmin.md @@ -103,7 +103,7 @@ In the screenshot below, you will notice that the node returns the information o There are three different ways to project a user's information: -- ***Basic:*** Does not include any custom fields. +- ***Basic:*** Doesn'tinclude any custom fields. - ***Custom:*** Includes the custom fields from schemas in customField. - ***Full:*** Include all the fields associated with the user. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticai.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticai.md index ab03cb0bb..4d56b0595 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticai.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.humanticai.md @@ -91,7 +91,7 @@ This node will return the `Hiring` persona for the candidate that we created usi 5. Select 'Hiring' from the ***Persona*** dropdown list. 6. Click on ***Execute Node*** to run the node. -In the screenshot below, you will notice that the node returns the `Hiring` persona for the candidate that we created using the Humantic AI node (column headers are not visible in the screenshot since we've scrolled down to show the data). +In the screenshot below, you will notice that the node returns the `Hiring` persona for the candidate that we created using the Humantic AI node (column headers aren't visible in the screenshot since we've scrolled down to show the data). ![Using the Humantic AI node to get the information of the candidate](/_images/integrations/builtin/app-nodes/humanticai/humanticai2_node.png) diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md index 536f084ae..634341079 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.jenkins.md @@ -24,8 +24,8 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Instance * Cancel quiet down state * Put Jenkins in quiet mode, no builds can be started, Jenkins is ready for shutdown - * Restart Jenkins immediately on environments where it is possible - * Restart Jenkins once no jobs are running on environments where it is possible + * Restart Jenkins immediately on environments where it's possible + * Restart Jenkins once no jobs are running on environments where it's possible * Shutdown once no jobs are running * Shutdown Jenkins immediately * Job diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox.md index e5ab97c1c..dbc4bc553 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.kobotoolbox.md @@ -65,7 +65,7 @@ All operations that return form submission data offer options to tweak the respo #### About reformatting -The default JSON format for KoBoToolbox submission data is sometimes hard to deal with, because it is not schema-aware, and all fields are therefore returned as strings. +The default JSON format for KoBoToolbox submission data is sometimes hard to deal with, because it's not schema-aware, and all fields are therefore returned as strings. This node provides a lightweight opinionated reformatting logic, enabled with the **Reformat?** parameter, available on all operations that return form submissions: the submission query, get, and the attachment download operations. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md index 24a6820ec..b3af6ad0e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.matrix.md @@ -99,7 +99,7 @@ In the screenshot below, you will notice that the node returns the information o ### 4. IF node -This node will compare your user ID with the user ID of other members. If the user IDs are not equal, the output will be true. +This node will compare your user ID with the user ID of other members. If the user IDs aren't equal, the output will be true. 1. Click on ***Add Condition*** and select 'String'. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextcloud.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextcloud.md index 9f2792e4c..d888b79d6 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextcloud.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.nextcloud.md @@ -34,7 +34,7 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Move a folder * Share a folder * User - * Invite a user to a NextCloud organization + * Invite a user to a Nextcloud organization * Delete a user. * Retrieve information about a single user. * Retrieve a list of users. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus.md index 40baa41d5..fa884352e 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.openthesaurus.md @@ -11,7 +11,7 @@ Use the OpenThesaurus node to automate work in OpenThesaurus, and integrate Open On this page, you'll find a list of operations the OpenThesaurus node supports and links to more resources. /// note | Credentials -OpenThesaurus node does not require authentication. +OpenThesaurus node doesn'trequire authentication. /// /// note | Examples and templates For usage examples and templates to help you get started, take a look at n8n's [OpenThesaurus integrations](https://n8n.io/integrations/openthesaurus/){:target="_blank" .external-link} list. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md index 12786b224..82903dd93 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster.md @@ -1,20 +1,20 @@ --- -title: Phantombuster -description: Documentation for the Phantombuster node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. +title: PhantomBuster +description: Documentation for the PhantomBuster node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- -# Phantombuster +# PhantomBuster -Use the Phantombuster node to automate work in Phantombuster, and integrate Phantombuster with other applications. n8n has built-in support for a wide range of Phantombuster features, including adding, deleting, and getting agents. +Use the PhantomBuster node to automate work in PhantomBuster, and integrate PhantomBuster with other applications. n8n has built-in support for a wide range of PhantomBuster features, including adding, deleting, and getting agents. -On this page, you'll find a list of operations the Phantombuster node supports and links to more resources. +On this page, you'll find a list of operations the PhantomBuster node supports and links to more resources. /// note | Credentials -Refer to [Phantombuster credentials](/integrations/builtin/credentials/phantombuster/) for guidance on setting up authentication. +Refer to [PhantomBuster credentials](/integrations/builtin/credentials/phantombuster/) for guidance on setting up authentication. /// /// note | Examples and templates -For usage examples and templates to help you get started, take a look at n8n's [Phantombuster integrations](https://n8n.io/integrations/phantombuster/){:target="_blank" .external-link} list. +For usage examples and templates to help you get started, take a look at n8n's [PhantomBuster integrations](https://n8n.io/integrations/phantombuster/){:target="_blank" .external-link} list. /// ## Operations diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md index 84c60686c..fdfced6b0 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.redis.md @@ -22,7 +22,7 @@ For usage examples and templates to help you get started, take a look at n8n's [ * Delete a key from Redis. * Get the value of a key from Redis. * Returns generic information about the Redis instance. -* Atomically increments a key by 1. Creates the key if it does not exist. +* Atomically increments a key by 1. Creates the key if it doesn'texist. * Returns all the keys matching a pattern. * Set the value of a key in redis. * Publish message to redis channel. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md index 2ec4097ea..a44526e90 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wekan.md @@ -1,20 +1,20 @@ --- -title: Wekan -description: Documentation for the Wekan node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. +title: WeKan +description: Documentation for the WeKan node in n8n, a workflow automation platform. Includes details of operations and configuration, and links to examples and credentials information. contentType: integration --- -# Wekan +# WeKan -Use the Wekan node to automate work in Wekan, and integrate Wekan with other applications. n8n has built-in support for a wide range of Wekan features, including creating, updating, deleting, and getting boards and cards. +Use the WeKan node to automate work in WeKan, and integrate WeKan with other applications. n8n has built-in support for a wide range of WeKan features, including creating, updating, deleting, and getting boards and cards. -On this page, you'll find a list of operations the Wekan node supports and links to more resources. +On this page, you'll find a list of operations the WeKan node supports and links to more resources. /// note | Credentials -Refer to [Wekan credentials](/integrations/builtin/credentials/wekan/) for guidance on setting up authentication. +Refer to [WeKan credentials](/integrations/builtin/credentials/wekan/) for guidance on setting up authentication. /// /// note | Examples and templates -For usage examples and templates to help you get started, take a look at n8n's [Wekan integrations](https://n8n.io/integrations/wekan/){:target="_blank" .external-link} list. +For usage examples and templates to help you get started, take a look at n8n's [WeKan integrations](https://n8n.io/integrations/wekan/){:target="_blank" .external-link} list. /// ## Basic Operations @@ -52,13 +52,13 @@ For usage examples and templates to help you get started, take a look at n8n's [ ## Example Usage -This workflow allows you to create a board and two lists called `To Do` and `Done` using the Wekan node. It also allows you to create a card and update the list ID of the card, enabling you to move it from the `To Do` list to the `Done` list. You can also find the [workflow](https://n8n.io/workflows/728) on n8n.io. This example usage workflow uses the following nodes. +This workflow allows you to create a board and two lists called `To Do` and `Done` using the WeKan node. It also allows you to create a card and update the list ID of the card, enabling you to move it from the `To Do` list to the `Done` list. You can also find the [workflow](https://n8n.io/workflows/728) on n8n.io. This example usage workflow uses the following nodes. - [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/) -- [Wekan]() +- [WeKan]() The final workflow should look like the following image. -![A workflow with the Wekan node](/_images/integrations/builtin/app-nodes/wekan/workflow.png) +![A workflow with the WeKan node](/_images/integrations/builtin/app-nodes/wekan/workflow.png) ### 1. Start node @@ -66,11 +66,11 @@ The final workflow should look like the following image. The start node exists by default when you create a new workflow. -### 2. Wekan node (create: board) +### 2. WeKan node (create: board) -This node will create a board called `Documentation` in Wekan. To create a board with a different name, you can enter the name of your board instead. +This node will create a board called `Documentation` in WeKan. To create a board with a different name, you can enter the name of your board instead. -1. First of all, you'll have to enter credentials for the Wekan node. You can find out how to do that [here](/integrations/builtin/credentials/wekan/). +1. First of all, you'll have to enter credentials for the WeKan node. You can find out how to do that [here](/integrations/builtin/credentials/wekan/). 2. Select 'Board' from the ***Resource*** dropdown list. 3. Enter `Documentation` in the ***Title*** field. @@ -80,29 +80,29 @@ This node will create a board called `Documentation` in Wekan. To create a board In the screenshot below, you will notice that the node creates a new board with the title `Documentation`. -![Using the Wekan node to create a board](/_images/integrations/builtin/app-nodes/wekan/wekan_node.png) +![Using the WeKan node to create a board](/_images/integrations/builtin/app-nodes/wekan/wekan_node.png) -### 3. Wekan1 node (create: list) +### 3. WeKan1 node (create: list) This node will create a list with the title `To Do` in the `Documentation` board, which was created using the previous node. 1. Select the credentials that you entered in the previous node. 2. Select 'List' from the ***Resource*** dropdown list. 3. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. +4. Select the following in the ***Variable Selector*** section: Nodes > WeKan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. 5. Enter `To Do` in the ***Title*** field. 6. Click on ***Execute Node*** to run the node. In the screenshot below, you will notice that the node creates a new list called `To Do` in the `Documentation` board. -![Using the Wekan node to create a list with the title To Do](/_images/integrations/builtin/app-nodes/wekan/wekan1_node.png) +![Using the WeKan node to create a list with the title To Do](/_images/integrations/builtin/app-nodes/wekan/wekan1_node.png) -### 4. Wekan2 node (create: list) +### 4. WeKan2 node (create: list) -This node will create a list with the title `Done` in the `Documentation` board, which was created using the Wekan node. +This node will create a list with the title `Done` in the `Documentation` board, which was created using the WeKan node. 1. Select the credentials that you entered in the previous node. 2. Select 'List' from the ***Resource*** dropdown list. @@ -114,55 +114,55 @@ This node will create a list with the title `Done` in the `Documentation` board, In the screenshot below, you will notice that the node creates a new list called `Done` in the `Documentation` board. -![Using the Wekan node to create a list with the title Done](/_images/integrations/builtin/app-nodes/wekan/wekan2_node.png) +![Using the WeKan node to create a list with the title Done](/_images/integrations/builtin/app-nodes/wekan/wekan2_node.png) -### 5. Wekan3 node (create: card) +### 5. WeKan3 node (create: card) -This node will create a card in the `Documentation` board under the list titled `To Do`, which was created using the Wekan1 node. +This node will create a card in the `Documentation` board under the list titled `To Do`, which was created using the WeKan1 node. 1. Select the credentials that you entered in the previous node. 2. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. 3. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. 4. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. 5. Select the following in the ***Variable Selector*** section: Nodes > Wekan1 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan1"].json["_id"]}}`. -6. Enter `Document Wekan node` in the ***Title*** field. +6. Enter `Document WeKan node` in the ***Title*** field. 7. Select 'Default' from the ***Swimlane ID*** dropdown list. 8. Select an author from the ***Author ID*** dropdown list. 9. Click on ***Execute Node*** to run the node. -In the screenshot below, you will notice that the node creates a new card with the title `Document Wekan node` in the `To Do` list of the `Documentation` board. +In the screenshot below, you will notice that the node creates a new card with the title `Document WeKan node` in the `To Do` list of the `Documentation` board. -![Using the Wekan node to create a card in the To Do list](/_images/integrations/builtin/app-nodes/wekan/wekan3_node.png) +![Using the WeKan node to create a card in the To Do list](/_images/integrations/builtin/app-nodes/wekan/wekan3_node.png) -### 6. Wekan4 node (update: card) +### 6. WeKan4 node (update: card) This node will update the list ID of the card created by the previous node and move it from the `To Do` list to the `Done` list. 1. Select the credentials that you entered in the previous node. 2. Select 'Update' from the ***Operation*** dropdown list. 3. Click on the gears icon next to the ***Board ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wekan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. +4. Select the following in the ***Variable Selector*** section: Nodes > WeKan > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan"].json["_id"]}}`. 5. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -6. Select the following in the ***Variable Selector*** section: Nodes > Wekan1 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan1"].json["_id"]}}`. +6. Select the following in the ***Variable Selector*** section: Nodes > WeKan1 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan1"].json["_id"]}}`. 7. Click on the gears icon next to the ***Card ID*** field and click on ***Add Expression***. -8. Select the following in the ***Variable Selector*** section: Nodes > Wekan3 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan3"].json["_id"]}}`. +8. Select the following in the ***Variable Selector*** section: Nodes > WeKan3 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan3"].json["_id"]}}`. 9. Click on the ***Add Field*** button and select 'List ID'. 10. Click on the gears icon next to the ***List ID*** field and click on ***Add Expression***. -11. Select the following in the ***Variable Selector*** section: Nodes > Wekan2 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan2"].json["_id"]}}`. +11. Select the following in the ***Variable Selector*** section: Nodes > WeKan2 > Output Data > JSON > _id. You can also add the following expression: `{{$node["Wekan2"].json["_id"]}}`. 12. Click on ***Execute Node*** to run the node. In the screenshot below, you will notice that the node updates the list id of the card that we created in the previous node and moves it from the `To Do` list to the `Done` list. -![Using the Wekan node to update the card](/_images/integrations/builtin/app-nodes/wekan/wekan4_node.png) +![Using the WeKan node to update the card](/_images/integrations/builtin/app-nodes/wekan/wekan4_node.png) ## FAQs ### How to load all the parameters for the node? -To load all the parameters, for example, Author ID, you need to give admin permissions to the user. Refer to the [Wekan documentation](https://github.com/wekan/wekan/wiki/Features#members-click-member-initials-or-avatar--permissions-adminnormalcomment-only) to learn how to change permissions. +To load all the parameters, for example, Author ID, you need to give admin permissions to the user. Refer to the [WeKan documentation](https://github.com/wekan/wekan/wiki/Features#members-click-member-initials-or-avatar--permissions-adminnormalcomment-only) to learn how to change permissions. diff --git a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md index a92efe405..dddbadab2 100644 --- a/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md +++ b/docs/integrations/builtin/app-nodes/n8n-nodes-base.wordpress.md @@ -44,7 +44,7 @@ The final workflow should look like the following image. The start node exists by default when you create a new workflow. -### 2. Wordpress node (create: post) +### 2. WordPress node (create: post) 1. First of all, you'll have to enter credentials for the WordPress node. You can find out how to do that [here](/integrations/builtin/credentials/wordpress/). 2. Enter the title in the ***Title*** field. @@ -53,12 +53,12 @@ The start node exists by default when you create a new workflow. ![Using the WordPress node to create a new post](/_images/integrations/builtin/app-nodes/wordpress/wordpress_node.png) -### 3. Wordpress1 node (update: post) +### 3. WordPress1 node (update: post) 1. Select the credentials that you entered in the previous node. 2. Select 'Update' from the ***Operation*** dropdown list. 3. Click on the gears icon next to the ***Post ID*** field and click on ***Add Expression***. -4. Select the following in the ***Variable Selector*** section: Nodes > Wordpress > Output Data > JSON > id. You can also add the following expression: `{{$node["Wordpress"].json["id"]}}`. +4. Select the following in the ***Variable Selector*** section: Nodes > WordPress > Output Data > JSON > id. You can also add the following expression: `{{$node["Wordpress"].json["id"]}}`. 5. Click on the ***Add Field*** button and select 'Content' from the dropdown list. 6. Enter the content in the ***Content*** filed. 7. Click on ***Execute Node*** to run the workflow. diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger.md index 7486cc74b..6da46bb5f 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.activationtrigger.md @@ -24,7 +24,7 @@ The Activation trigger node gets triggered for the workflow that it gets added t - Events - ***Activation:*** Run when the workflow gets activated - ***Start:*** Run when n8n starts or restarts - - ***Update:*** Run when the workflow gets saved while it is active + - ***Update:*** Run when the workflow gets saved while it's active ## Example Usage diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md index 1523b8d46..45030e0cd 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.if.md @@ -25,22 +25,22 @@ Add comparison conditions using the **Add Condition** filter. The available comp **String**: - exists -- does not exist +- doesn'texist - is equal to - is not equal to - contains -- does not contain +- doesn'tcontain - starts with -- does not start with +- doesn'tstart with - ends with -- does not end with +- doesn'tend with - matches regex -- does not match regex +- doesn'tmatch regex **Number**: - exists -- does not exist +- doesn'texist - is equal to - is not equal to - is greater than @@ -51,7 +51,7 @@ Add comparison conditions using the **Add Condition** filter. The available comp **Date & Time**: - exists -- does not exist +- doesn'texist - is equal to - is not equal to - is after @@ -62,7 +62,7 @@ Add comparison conditions using the **Add Condition** filter. The available comp **Boolean**: - exists -- does not exist +- doesn'texist - is true - is false - is equal to @@ -71,11 +71,11 @@ Add comparison conditions using the **Add Condition** filter. The available comp **Array**: - exists -- does not exist +- doesn'texist - is equal to - is not equal to - contains -- does not contain +- doesn'tcontain - length equal to - length not equal to - length greater than @@ -86,7 +86,7 @@ Add comparison conditions using the **Add Condition** filter. The available comp **Object**: - exists -- does not exist +- doesn'texist - is empty - is not empty diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md index eae4d4311..e546dacf6 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.markdown.md @@ -33,7 +33,7 @@ Some of the options depend on each other, or can interact. We recommend testing | **GitHub Mentions** | Whether to support tagging GitHub users with `@` (enabled) or not (disabled). When enabled, n8n replaces `@name` with `https://github.com/name`. | Disabled | | **GitHub Task Lists** | Whether to support GitHub Flavored Markdown task lists (enabled) or not (disabled). | Disabled | | **Header Level Start** | Number. Set the start level for headers. For example, changing this field to `2` causes n8n to treat `#` as `

`, `##` as `

`, and so on. | 1 | -| **Mandatory Space Before Header** | Whether to make a space between `#` and heading text required (enabled) or not (disabled). When enabled, n8n renders a heading written as `##Some header text` literally (it does not turn it into a heading element) | Disabled | +| **Mandatory Space Before Header** | Whether to make a space between `#` and heading text required (enabled) or not (disabled). When enabled, n8n renders a heading written as `##Some header text` literally (it doesn'tturn it into a heading element) | Disabled | | **Middle Word Asterisks** | Whether n8n should treat asterisks in words as Markdown (disabled) or render them as literal asterisks (enabled). | Disabled | | **Middle Word Underscores** | Whether n8n should treat underscores in words as Markdown (disabled) or render them as literal underscores (enabled). | Disabled | | **No Header ID** | Disable automatic generation of header IDs (enabled). | Disabled | diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md index 10748c24c..a272aa481 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.ssh.md @@ -29,7 +29,7 @@ You can find authentication information for this node [here](/integrations/built - ***Working Directory:*** Only visible for **Command** resources. The directory where the command should be executed. - ***Path:*** Only visible for **Download** operation on file resources. The path where the desired file is found. - ***Binary Property:*** Only visible for file resources. The name of the binary property which contains the data for the file to be uploaded. -- ***Target Directory:*** Only visible for **Upload** operations on file resources. The directory to upload the file to. The name of the file does not need to be specified, it's taken from the binary data file name. To override this behavior, set the parameter **File Name** under options. +- ***Target Directory:*** Only visible for **Upload** operations on file resources. The directory to upload the file to. The name of the file doesn'tneed to be specified, it's taken from the binary data file name. To override this behavior, set the parameter **File Name** under options. ## Example Usage diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md index 0242d1f85..922964635 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.start.md @@ -7,13 +7,13 @@ contentType: integration # Start /// warning | Deprecated -The Start node was removed from n8n in 0.199.0. It is still available in legacy workflows. +The Start node was removed from n8n in 0.199.0. It's still available in legacy workflows. /// The start node is the first node in a workflow. It exists by default when you create a new workflow and looks like the following image. ![A new workflow with the Start node](/_images/integrations/builtin/core-nodes/start/workflow.png) -In case there is no trigger node in the workflow, the workflow always starts from the Start node. The Start node cannot be deleted. Even if a workflow contains a trigger node, there would still be a Start node. +In case there is no trigger node in the workflow, the workflow always starts from the Start node. The Start node can't be deleted. Even if a workflow contains a trigger node, there would still be a Start node. ## FAQs diff --git a/docs/integrations/builtin/credentials/google/service-account.md b/docs/integrations/builtin/credentials/google/service-account.md index 26fd03cca..a60e3600b 100644 --- a/docs/integrations/builtin/credentials/google/service-account.md +++ b/docs/integrations/builtin/credentials/google/service-account.md @@ -80,7 +80,7 @@ The following video demonstrates the steps described above. ## Troubleshooting -### Service Account cannot access Google Drive files +### Service Account can't access Google Drive files A Service Account can't access Google Drive files and folders that weren't shared with its associated user email. diff --git a/docs/integrations/builtin/credentials/phantombuster.md b/docs/integrations/builtin/credentials/phantombuster.md index 8f18b5425..4e8bfa480 100644 --- a/docs/integrations/builtin/credentials/phantombuster.md +++ b/docs/integrations/builtin/credentials/phantombuster.md @@ -1,26 +1,26 @@ --- -title: Phantombuster credentials -description: Documentation for Phantombuster credentials. Use these credentials to authenticate Phantombuster in n8n, a workflow automation platform. +title: PhantomBuster credentials +description: Documentation for PhantomBuster credentials. Use these credentials to authenticate PhantomBuster in n8n, a workflow automation platform. contentType: integration --- -# Phantombuster credentials +# PhantomBuster credentials -You can use these credentials to authenticate the following nodes with Phantombuster. +You can use these credentials to authenticate the following nodes with PhantomBuster. -- [Phantombuster](/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster/) +- [PhantomBuster](/integrations/builtin/app-nodes/n8n-nodes-base.phantombuster/) ## Prerequisites -Create a [Phantombuster](https://www.phantombuster.com/) account. +Create a [PhantomBuster](https://www.phantombuster.com/) account. ## Using API -1. Access your [Phantombuster](https://phantombuster.com/) dashboard. +1. Access your [PhantomBuster](https://phantombuster.com/) dashboard. 2. Click on your name on the top right and select 'Org settings'. 3. Scroll down to the ***Third party API keys*** section. 4. Click on the ***+ Add third party API key*** button. -5. Use this ***API Key*** with your Phantombuster node credentials in n8n. +5. Use this ***API Key*** with your PhantomBuster node credentials in n8n. -![Getting Phantombuster credentials](/_images/integrations/builtin/credentials/phantombuster/using-api.gif) +![Getting PhantomBuster credentials](/_images/integrations/builtin/credentials/phantombuster/using-api.gif) diff --git a/docs/integrations/builtin/credentials/wekan.md b/docs/integrations/builtin/credentials/wekan.md index c4fe893b0..c7b177520 100644 --- a/docs/integrations/builtin/credentials/wekan.md +++ b/docs/integrations/builtin/credentials/wekan.md @@ -1,20 +1,20 @@ --- -title: Wekan credentials -description: Documentation for Wekan credentials. Use these credentials to authenticate Wekan in n8n, a workflow automation platform. +title: WeKan credentials +description: Documentation for WeKan credentials. Use these credentials to authenticate WeKan in n8n, a workflow automation platform. contentType: integration --- -# Wekan credentials +# WeKan credentials -You can use these credentials to authenticate the following nodes with Wekan. +You can use these credentials to authenticate the following nodes with WeKan. -- [Wekan](/integrations/builtin/app-nodes/n8n-nodes-base.wekan/) +- [WeKan](/integrations/builtin/app-nodes/n8n-nodes-base.wekan/) ## Prerequisites -Install [Wekan](https://github.com/wekan/wekan/wiki) on your server. +Install [WeKan](https://github.com/wekan/wekan/wiki) on your server. ## Using API Key -1. Use the Wekan username, password, and URL with your Wekan node credentials in n8n. +1. Use the WeKan username, password, and URL with your WeKan node credentials in n8n. diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger.md index 1050e52cc..01f6207bc 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.coppertrigger.md @@ -6,7 +6,7 @@ contentType: integration # Copper trigger -[Copper](https://www.copper.com/) is a CRM that focuses on strong integration with Google's G Suite. It is mainly targeted towards small and medium-sized businesses. +[Copper](https://www.copper.com/) is a CRM that focuses on strong integration with Google's G Suite. It's mainly targeted towards small and medium-sized businesses. /// note | Credentials You can find authentication information for this node [here](/integrations/builtin/credentials/copper/). diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger.md index 380806047..b3dbedd44 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.figmatrigger.md @@ -13,7 +13,7 @@ You can find authentication information for this node [here](/integrations/built /// /// warning | Supported Figma Plans -Figma does not support webhooks on the free "Starter" plan. Your team would need to be on the "Professional" plan to use this node. +Figma doesn'tsupport webhooks on the free "Starter" plan. Your team would need to be on the "Professional" plan to use this node. /// ## Trigger Events diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger.md index e0b12ad2b..95fc00fdd 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.kobotoolboxtrigger.md @@ -6,7 +6,7 @@ contentType: integration # KoBo Toolbox trigger -[KoBo toolbox](https://www.kobotoolbox.org/) is a field survey and data collection tool that makes it easy to design interactive forms to be completed offline from mobile devices. It is available both as a free cloud solution or as a self-hosted version. +[KoBo toolbox](https://www.kobotoolbox.org/) is a field survey and data collection tool that makes it easy to design interactive forms to be completed offline from mobile devices. It's available both as a free cloud solution or as a self-hosted version. /// note | Credentials You can find authentication information for this node [here](/integrations/builtin/credentials/kobotoolbox/). diff --git a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger.md b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger.md index a14e289c6..e4db7a376 100644 --- a/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger.md +++ b/docs/integrations/builtin/trigger-nodes/n8n-nodes-base.trellotrigger.md @@ -50,5 +50,5 @@ For this specific example, the List ID would be the Model ID. ### What is the Model ID? -It is the ID of any model in Trello. Depending on the use-case, it could be the User ID, List ID, and so on. +It's the ID of any model in Trello. Depending on the use-case, it could be the User ID, List ID, and so on. diff --git a/docs/integrations/community-nodes/index.md b/docs/integrations/community-nodes/index.md index e0ee1d908..e17b3739a 100644 --- a/docs/integrations/community-nodes/index.md +++ b/docs/integrations/community-nodes/index.md @@ -9,5 +9,5 @@ n8n provides hundreds of built-in nodes. It also supports users [creating their The community nodes repository allows users who create nodes to publish them to npm. These nodes are then available to install and use in your n8n instance. /// note | Only available on self-hosted instances -Community nodes are not available on n8n cloud and require [self-hosting](/hosting/) n8n. -/// \ No newline at end of file +Community nodes aren't available on n8n cloud and require [self-hosting](/hosting/) n8n. +/// diff --git a/docs/integrations/creating-nodes/build/create-trigger-node.md b/docs/integrations/creating-nodes/build/create-trigger-node.md index 1dd7e2731..7df01cf13 100644 --- a/docs/integrations/creating-nodes/build/create-trigger-node.md +++ b/docs/integrations/creating-nodes/build/create-trigger-node.md @@ -41,7 +41,7 @@ Since n8n's repository already has a Autopilot Trigger node, we will name this n 3. Within the Autofriend folder, create a file called `AutofriendTrigger.node.ts` (YourNodeNameTrigger.node.ts). 4. Download and add the Autofriend [icon](https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/Autopilot/autopilot.svg) to the folder. Name it `autopilot.svg`. - The icon property has to be either a 60x60 pixels PNG or an SVG and must exist in the node's folder. - - An SVG is preferable. In case you have to use a PNG, make sure that it is compressed. A good tool for that is [tinypng](https://tinypng.com). + - An SVG is preferable. In case you have to use a PNG, make sure that it's compressed. A good tool for that is [tinypng](https://tinypng.com). - A good place to find company icons is [gilbarbara/logos](https://github.com/gilbarbara/logos/tree/master/logos). 5. Paste the following code in the `AutofriendTrigger.node.ts` file. @@ -140,7 +140,7 @@ npm run dev - On startup, n8n will load all the nodes and credentials (more about credentials later) that are registered in `/packages/nodes-base/package.json`. - The property `description.name` uses camelCase. -- The property `description.color` is the company's branding color in hexadecimal. In case the website does not include this information, there are other websites that help you get a company's branding colors. For example, [brandpalettes.com](https://brandpalettes.com/). +- The property `description.color` is the company's branding color in hexadecimal. In case the website doesn'tinclude this information, there are other websites that help you get a company's branding colors. For example, [brandpalettes.com](https://brandpalettes.com/). ## Creating the UI for the node @@ -320,7 +320,7 @@ The life cycle methods allow us to create, delete, and check if the webhook exis **Methods** - `checkExist`: This is the first method that gets called. It checks if the webhook with the current path is already registered in the external system or not. If the webhook is already registered, n8n persists the webhook ID. If the webhook is not registered with the external system, the `create` method gets executed. -- `create`: This method gets called if the `checkExist` method returns false (if the webhook with the current path does not exist in the external system). This method registers the webhook in the external system and stores the webhook ID in n8n. +- `create`: This method gets called if the `checkExist` method returns false (if the webhook with the current path doesn'texist in the external system). This method registers the webhook in the external system and stores the webhook ID in n8n. - `delete`: This method gets called when the trigger is either stopped manually or when the workflow is deactivated. It uses the ID previously persisted by either the create or the checkExist method to delete the webhook from the external system. ![Lifecycle flowchart](/_images/integrations/creating-nodes/lifecycle.png) @@ -459,7 +459,7 @@ The trigger node is now receiving events. Sometimes it might take a bit longer f You probably noticed that this time we did not run the project using `npm run dev`, but instead using `./packages/cli/bin/n8n start --tunnel`. -Since our server is running locally, we need a tool that lets us proxy all requests to our local machine so that n8n receives and handles the events from the external service (Autopilot). This gets achieved using a tunnel. The details on how a tunnel works are out of the scope of this tutorial. If you want to know about it, you can check this [link](http://localtunnel.github.io/www/). Keep in mind that the tunnel is meant for development purposes only and should not be used in production. +Since our server is running locally, we need a tool that lets us proxy all requests to our local machine so that n8n receives and handles the events from the external service (Autopilot). This gets achieved using a tunnel. The details on how a tunnel works are out of the scope of this tutorial. If you want to know about it, you can check this [link](http://localtunnel.github.io/www/). Keep in mind that the tunnel is meant for development purposes only and shouldn't be used in production. ## Test your node diff --git a/docs/integrations/creating-nodes/build/reference/http-helpers.md b/docs/integrations/creating-nodes/build/reference/http-helpers.md index d0575088b..a19729a54 100644 --- a/docs/integrations/creating-nodes/build/reference/http-helpers.md +++ b/docs/integrations/creating-nodes/build/reference/http-helpers.md @@ -85,7 +85,7 @@ For an example, refer to the [Mattermost node](https://github.com/n8n-io/n8n/blo The previous helper implementation using `this.helpers.request(options)` used and exposed the `request-promise` library. This was removed in version 1. -To minimize incompatibility, n8n made a transparent conversion to another library called `axios`. +To minimize incompatibility, n8n made a transparent conversion to another library called `Axios`. If you are having issues, please report them in the [Community Forums](https://community.n8n.io/){:target=_blank .external-link} or on [GitHub](https://github.com/n8n-io/n8n/issues){:target=_blank .external-link}. diff --git a/docs/integrations/creating-nodes/test/troubleshooting-node-development.md b/docs/integrations/creating-nodes/test/troubleshooting-node-development.md index acfd9062e..495aa207d 100644 --- a/docs/integrations/creating-nodes/test/troubleshooting-node-development.md +++ b/docs/integrations/creating-nodes/test/troubleshooting-node-development.md @@ -7,7 +7,7 @@ contentType: howto ## Credentials -### Error message: 'Credentials of type "*" are not known' +### Error message: 'Credentials of type "*" aren't known' Check that the name in the credentials array matches the name used in the property name of the credentials' class. @@ -19,7 +19,7 @@ Check that the name in the credentials array matches the name used in the proper -### Error message: 'There was a problem loading init data: API-Server can not be reached. It is probably down' +### Error message: 'There was a problem loading init data: API-Server can not be reached. It's probably down' - Check that the names of the node file, node folder, and class match the path added to `packages/nodes-base/package.json`. diff --git a/docs/release-notes.md b/docs/release-notes.md index e34365e28..7355773c9 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1678,7 +1678,7 @@ This release introduces the [TOTP](/integrations/builtin/core-nodes/n8n-nodes-ba ### Bug fixes * Code Node: Update vm2 to address CVE-2023-29017. -* Core: App should not crash with a custom REST endpoint. +* Core: App shouldn't crash with a custom REST endpoint. * Core: Do not execute workflowExecuteBefore hook when resuming executions from a waiting state. * Core: Fix issue where sub workflows would display as running forever after failure to start. * Core: Update xml2js to address CVE-2023-0842. @@ -1722,7 +1722,7 @@ Please note that this version contains a breaking change. The minimum Node.js ve ### Bug fixes * Add droppable state for booleans when mapping. -* Compare Datasets Node: Fuzzy compare not comparing keys missing in one of the inputs. +* Compare Datasets Node: Fuzzy comparen't comparing keys missing in one of the inputs. * Compare Datasets Node: Fix support for dot notation in skip fields. * Core: Deactivate active workflows during import. * Core: Stop marking duplicates as circular references in `jsonStringify`. @@ -2631,7 +2631,7 @@ Editor: suppress validation errors for freshly added nodes. * Build CLI to fix Postgres and MySQL test runs. * Extend date functions clobbering plus/minus. -* Extension deep compare not quite working for some primitives. +* Extension deep comparen't quite working for some primitives. * Upgrade jsonwebtoken to address CVE-2022-23540. @@ -3083,7 +3083,7 @@ KoBo Toolbox node: add support for the media file API. * Core: fix partial execution with pinned data on child node run. * Core: OAuth2 scopes now save. * Enable source-maps on WorkflowRunnerProcess in own mode. -* Handle error when workflow does not exist or is inaccessible. +* Handle error when workflow doesn'texist or is inaccessible. * Make nodes.exclude and nodes.include work with lazy-loaded nodes. * Code Node: restore `pairedItem` to required n8n item keys. * Execute Workflow Node: update Execute Workflow node info notice text. @@ -3415,7 +3415,7 @@ This release introduces the Schedule Trigger node, replacing the Cron node. You ### Node enhancements -* Hubspot node: you can now use your Hubspot credentials in the HTTP Request node to make a [custom API call](/integrations/custom-operations/). +* HubSpot node: you can now use your HubSpot credentials in the HTTP Request node to make a [custom API call](/integrations/custom-operations/). * Rundeck node: you can now use your Rundeck credentials in the HTTP Request node to make a [custom API call](/integrations/custom-operations/). ### Bug fixes @@ -3694,7 +3694,7 @@ The [WhatsApp Business Platform](/integrations/builtin/app-nodes/n8n-nodes-base. * Editor: resolve slow loading times for node types, node creators, and push connections in the settings view. * Nodes: update descriptions in the Merge node * Nodes: ensure the card ID property displays for completed checklists in the Trello node. -* Nodes: fix authentication for the new verions of Wekan. +* Nodes: fix authentication for the new verions of WeKan. * Nodes: ensure form names list correctly in the Wufoo trigger node. ### Contributors @@ -3748,7 +3748,7 @@ This is a bug fix release. It resolves an issue with Postgres migrations. View the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.194.0...n8n@0.195.0){:target=_blank .external-link} for this version.
**Release date:** 2022-09-21 -This release introduces user management and credential sharing for our Cloud platform. It also contains other enhancements and bug fixes. +This release introduces user management and credential sharing for n8n's Cloud platform. It also contains other enhancements and bug fixes. ### New features @@ -3756,13 +3756,13 @@ This release introduces user management and credential sharing for our Cloud pla #### User management and credential sharing for Cloud -This release adds support for our existing [user management](/user-management/) functionality to Cloud, and introduces a new feature: [credential sharing](/credentials/credential-sharing/). Credential sharing is currently only available on Cloud. +This release adds support for n8n's existing [user management](/user-management/) functionality to Cloud, and introduces a new feature: [credential sharing](/credentials/credential-sharing/). Credential sharing is currently only available on Cloud. Also in this release: -* Added a `resourceLocator` parameter type for nodes, and started upgrading our built-in nodes to use it. This new option helps users who need to specify the ID of a record or item in an external service. For example, when using the Trello node, you can now search for a specific card by ID, URL, or do a free text search for card titles. Node builders can learn more about working with this new UI element in our [UI elements](/integrations/creating-nodes/build/reference/ui-elements/) documentation. +* Added a `resourceLocator` parameter type for nodes, and started upgrading n8n's built-in nodes to use it. This new option helps users who need to specify the ID of a record or item in an external service. For example, when using the Trello node, you can now search for a specific card by ID, URL, or do a free text search for card titles. Node builders can learn more about working with this new UI element in n8n's [UI elements](/integrations/creating-nodes/build/reference/ui-elements/) documentation. * Cache npm dependencies to improve performance on self-hosted n8n ### Bug fixes @@ -3800,7 +3800,7 @@ This release includes new nodes: a Gmail trigger, Google Cloud Storage, and Adal #### Adalo -Adalo is a low code app builder. Refer to our [Adalo node documentation](/integrations/builtin/app-nodes/n8n-nodes-base.adalo/) for more information. +Adalo is a low code app builder. Refer to n8n's [Adalo node documentation](/integrations/builtin/app-nodes/n8n-nodes-base.adalo/) for more information. @@ -3841,7 +3841,7 @@ n8n now has a [Gmail trigger node](/integrations/builtin/trigger-nodes/n8n-nodes * Public API: better error handling for bad requests. * AWS nodes: fixed an issue with credentials testing. * GoogleBigQuery node: fix for empty responses when creating records. -* Hubspot node: correct the node name on the canvas. +* HubSpot node: correct the node name on the canvas. ### Contributors @@ -4012,7 +4012,7 @@ n8n@0.187.0 saw the first release of [data mapping](/data/data-mapping/), allowi * CLI: fix the excessive instantiation type error for flattened executions. * CLI: initiate the nodes directory to ensure `npm install` succeeds. * CLI: ensure tsc build errors also cause Turbeorepo builds to fail. -* NextCloud node: fix an issue with credential verification. +* Nextcloud node: fix an issue with credential verification. * Freshdesk node: fix an issue where the getAll operation required non-existant options. ## n8n@0.191.1 @@ -4081,7 +4081,7 @@ This release includes a new node, Sendinblue, as well as bug fixes. ### New nodes -[Sendinblue node](/integrations/builtin/app-nodes/n8n-nodes-base.sendinblue/) and Sendinblue trigger node: introducing our [Sendinblue](https://www.sendinblue.com/){:target=_blank .external-link} integration. +[Sendinblue node](/integrations/builtin/app-nodes/n8n-nodes-base.sendinblue/) and Sendinblue trigger node: introducing n8n's [Sendinblue](https://www.sendinblue.com/){:target=_blank .external-link} integration. ### Node enhancements @@ -4554,7 +4554,7 @@ This release adds a new trigger node for Cal.com. Refer to the [Cal trigger docu * Correct delete button hover spacing. * Resolve a bug causing stuck loading states. * [EmailReadImap node](/integrations/builtin/core-nodes/n8n-nodes-base.emailimap/){:target=_blank}: improve error handling. -* [Hubspot node](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/){:target=_blank}: fix contact loading. +* [HubSpot node](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/){:target=_blank}: fix contact loading. ### Contributors @@ -5002,7 +5002,7 @@ This release includes: This release changes n8n's license, from [Apache 2.0 with Commons Clause](https://github.com/n8n-io/n8n/blob/181ba3c4e236279b65d102a8a33ae6896f160487/LICENSE.md) to [Sustainable Use License](https://github.com/n8n-io/n8n/blob/master/LICENSE.md). -This change aims to clarify our license terms, and our position as a fair-code project. +This change aims to clarify n8n's license terms, and n8n's position as a fair-code project. Read more about the new license in [License](/reference/license/). @@ -5119,7 +5119,7 @@ Added a Redis Trigger node, so you can now start workflows based on a Redis even * [Facebook Graph API:](/integrations/builtin/app-nodes/n8n-nodes-base.facebookgraphapi/) Added suport for Facebook Graph API 13. -* [Hubspot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Added suport for private app token authentication. +* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Added suport for private app token authentication. * [MongoDB:](/integrations/builtin/app-nodes/n8n-nodes-base.mongodb/) Added the aggregate operation. * [Redis Trigger:](/integrations/builtin/trigger-nodes/n8n-nodes-base.redistrigger/) Added a Redis Trigger node. * [Redis:](/integrations/builtin/app-nodes/n8n-nodes-base.redis/) Added support for publish operations. @@ -5404,7 +5404,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ ### Core Functionality -- Temporarily removed debug logging for axios requests. +- Temporarily removed debug logging for Axios requests. ## n8n@0.159.0 @@ -5613,8 +5613,8 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ * [APITemplate.io:](/integrations/builtin/app-nodes/n8n-nodes-base.apitemplateio/) Fixed a bug where the Create operation on the Image resource would fail when the Download option is not enabled. -* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed authentication for new Hubspot applications by using granular scopes when authenticating against the Hubspot OAuth2 API. -* [HubSpot Trigger:](/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/) Fixed authentication for new Hubspot applications by using granular scopes when authenticating against the Hubspot Developer API. +* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed authentication for new HubSpot applications by using granular scopes when authenticating against the HubSpot OAuth2 API. +* [HubSpot Trigger:](/integrations/builtin/trigger-nodes/n8n-nodes-base.hubspottrigger/) Fixed authentication for new HubSpot applications by using granular scopes when authenticating against the HubSpot Developer API. * [Jira Software:](/integrations/builtin/app-nodes/n8n-nodes-base.jira/) Fixed an issue where the Reporter field would not work as expected on Jira Server instances. * [Salesforce:](/integrations/builtin/app-nodes/n8n-nodes-base.salesforce/) Fixed a typo preventing the value in the amount field of from being saved. @@ -5704,7 +5704,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Fixed an issue preventing the `n8n import:workflow --separate` CLI command from finding workflows on Windows. - Further improved the expression security. - Moved all nodes into separate directories in preparation for internationalization. -- Removing default headers for PUT and PATCH operations when using axios. +- Removing default headers for PUT and PATCH operations when using Axios. - Revamped the workflow canvas. ### Bug fixes @@ -5776,7 +5776,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Added a hook after workflow creation. - Fixed a build issue with npm v7 by overriding unwanted behaviour through the .npmrc file. - Fixed an issue preventing unknown node types from being imported. -- Fixed an issue with the UI falsely indicating a credential cannot be selected when using SQLite and multiple credentials with the same name exist. +- Fixed an issue with the UI falsely indicating a credential can't be selected when using SQLite and multiple credentials with the same name exist. ### Bug fixes @@ -5833,7 +5833,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Added name and ID of a workflow to its settings. - Added parameter inputs to be multi-line. -- Fixed an issue with declaring proxies when axios is used. +- Fixed an issue with declaring proxies when Axios is used. - Fixed an issue with serializing arrays and special characters. - Fixed an issue with updating expressions after renaming a node. @@ -6047,7 +6047,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ * [Baserow:](/integrations/builtin/app-nodes/n8n-nodes-base.baserow/) Added the following filter options: Contains, Contains Not, Date Before Date, Date After Date, Filename Contains, Is Empty, Is Not Empty, Link Row Has, Link Row Does Not Have, Single Select Equal, and Single Select Not Equal. * [Pipedrive:](/integrations/builtin/app-nodes/n8n-nodes-base.pipedrive/) Added support for Notes on Leads. -* [Wekan:](/integrations/builtin/app-nodes/n8n-nodes-base.wekan/) Added Sort field to the Card resource. +* [WeKan:](/integrations/builtin/app-nodes/n8n-nodes-base.wekan/) Added Sort field to the Card resource. ### Core Functionality @@ -6074,7 +6074,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ ### Enhanced nodes * [Clockify:](/integrations/builtin/app-nodes/n8n-nodes-base.clockify/) Added Task resource. -* [Hubspot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Added dropdown selection for Properties and Properties with History filters for Get All Deals operations. +* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Added dropdown selection for Properties and Properties with History filters for Get All Deals operations. * [Mautic:](/integrations/builtin/app-nodes/n8n-nodes-base.mautic/) Added Campaign Contact resource. * [MongoDB:](/integrations/builtin/app-nodes/n8n-nodes-base.mongodb/) Added ability to query documents by '_id'. * [MQTT:](/integrations/builtin/app-nodes/n8n-nodes-base.mqtt/) Added SSL/TLS support to authentication. @@ -6091,8 +6091,8 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ ### Bug fixes -* [Hubspot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed issue with 'RequestAllItems' API. -* [Wordpress:](/integrations/builtin/app-nodes/n8n-nodes-base.wordpress/) Fixed issue with 'RequestAllItems' API only returning the first 10 items. +* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed issue with 'RequestAllItems' API. +* [WordPress:](/integrations/builtin/app-nodes/n8n-nodes-base.wordpress/) Fixed issue with 'RequestAllItems' API only returning the first 10 items. ### Contributors [André Matthies](https://github.com/matthiez), [DeskYT](https://github.com/DeskYT), [Frederic Alix](https://github.com/fredericalix), [Jonathan Bennetts](https://github.com/Joffcom), [Ketan Somvanshi](https://github.com/KetanSomvanshi), [Luiz Eduardo de Oliveira Fonseca](https://github.com/luizeof), [TheFSilver](https://github.com/TheFSilver) @@ -6198,7 +6198,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ * [AWS SES:](/integrations/builtin/app-nodes/n8n-nodes-base.awsses/) Fixed issue where special characters in the message were not encoded. * [Baserow:](/integrations/builtin/app-nodes/n8n-nodes-base.baserow/) Fixed issue where Create operation inserted null values. -* [Hubspot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed issue when sending context parameter. +* [HubSpot:](/integrations/builtin/app-nodes/n8n-nodes-base.hubspot/) Fixed issue when sending context parameter. ### Contributors [calvintwr](https://github.com/calvintwr), [CFarcy](https://github.com/CFarcy), [Jeremie Dokime](https://github.com/dokime7), [Michael Hirschler](https://github.com/mvhirsch), [Rodrigo Correia](https://github.com/rodrigoscdc), [sol](https://github.com/5pecia1) @@ -6930,7 +6930,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - SendGrid: Added Mail resource - Spotify: Added Library resource - Telegram: Added Answer Inline Query operation to the Callback resource -- uProc: Added Get ASIN code by EAN code, Get EAN code by ASIN code, Get Email by Social Profile, Get Email by Fullname and Company's domain, and Get Email by Fullname and Company's name operations +- uProc: Added Get ASIN code by EAN code, Get EAN code by ASIN code, Get Email by Social Profile, Get Email by Full name and Company's domain, and Get Email by Full name and Company's name operations - Bug fixes - Clearbit: Fixed an issue with the autocomplete URI - Dropbox: Fixed an issue with the Dropbox credentials by adding the APP Access Type parameter in the credentials. For more details, check out the entry in the [breaking changes](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01130) page @@ -6982,7 +6982,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Added the functionality to expose metrics to Prometheus. Read more about that [here](/hosting/configuration/#prometheus) - Updated fallback values to match the value type - Added the functionality to display debugging information for pending workflows on exit -- Fixed an issue with queue mode for the executions that should not be saved +- Fixed an issue with queue mode for the executions that shouldn't be saved - Fixed an issue with workflows crashing and displaying `Unknown` status in the execution list - Fixed an issue to prevent crashing while saving execution data when the `data` field has over 64KB in MySQL - Updated `jws-rsa` to version `1.12.1` @@ -7029,7 +7029,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - GoToWebinar - Raindrop - Enhanced nodes -- AWS Rekognition: Added the Detect Text type to the Ananlyze operation for the Image resource +- AWS Rekognition: Added the Detect Text type to the Analyze operation for the Image resource - Google Calendar: Added RRULE parameter to the Get All operation for the Event resource - Jira: Added User resource and operations - Reddit: Added the Search operation for the Post resource @@ -7077,7 +7077,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Twitter: Added Delete operation to the Tweet resource - Bug fixes - Google Drive: Fixed an issue with the Delete and Share operations -- Filemaker: Fixed an issue with the script list parsing +- FileMaker: Fixed an issue with the script list parsing - Updated Node.js version of Docker images to `14.15` - Added a shortcut `CTRL + scroll` to zoom @@ -7108,7 +7108,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Enhanced nodes - Affinity: Added List and List Entry resource - Asana: Added Project IDs option to the Create operation of the Task resource -- Hubspot Trigger: Added support for multiple subscriptions +- HubSpot Trigger: Added support for multiple subscriptions - Jira: Added Issue Attachment resource and added custom fields to Create and Update operations of the Issue resource - Todoist: Added Section option - Bug fixes @@ -7169,7 +7169,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - AWS Lambda: Fixed an issue with signature - AWS SNS: Fixed an issue with signature - Fixed an issue with nodes not executing if two input gets passed and one of them didn't return any data -- The code editor does not get closed when clicked anywhere outside the editor +- The code editor doesn'tget closed when clicked anywhere outside the editor - Added CLI commands to [export](/hosting/cli-commands/#export-workflows-and-credentials) and [import](/hosting/cli-commands/#import-workflows-and-credentials) credentials and workflows - The title in the browser tab now resets for new workflows @@ -7182,10 +7182,10 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Beeminder - Enhanced nodes - Crypto: Added hash type `SHA384` -- Google Books: Added support for user impersonification -- Google Drive: Added support for user impersonification -- Google Sheets: Added support for user impersonification -- Gmail: Added support for user impersonification +- Google Books: Added support for user impersonation +- Google Drive: Added support for user impersonation +- Google Sheets: Added support for user impersonation +- Gmail: Added support for user impersonation - Microsoft Outlook: Added support for a shared mailbox - RabbitMQ: Added Exchange mode - Salesforce: Added filters to all Get All operations @@ -7201,7 +7201,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - New nodes - Google Analytics -- Phantombuster +- PhantomBuster - Enhanced nodes - AWS: Added support for custom endpoints - Gmail: Added an option to send messages formatted as HTML @@ -7216,7 +7216,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Split In Batches: Fixed a typo in the description - Telegram: Fixed an issue with the Send Audio operation - Based on your settings, vacuum runs on SQLite on startup -- Updated axios to version `0.21.1` +- Updated Axios to version `0.21.1` ## n8n@0.100.0 For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.99.1...n8n@0.100.0) for this version.
@@ -7267,7 +7267,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Bug fixes - Dropbox: Fixed an issue with the OAuth credentials - Google Sheets: Fixed an issue with the parameters getting hidden for other operations -- Added functionality to easily copy the data and the path from the output +- Added functionality to copy the data and the path from the output - Fixed an issue with the node getting selected after it was duplicated ## n8n@0.98.0 @@ -7295,7 +7295,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - New nodes - Ghost -- Nasa +- NASA - Snowflake - Twist - Enhanced nodes @@ -7317,7 +7317,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - TheHive Trigger - Yourls - Enhanced nodes -- Hubspot: Added Contact List resource and Search operation for the Deal resource +- HubSpot: Added Contact List resource and Search operation for the Deal resource - Google Calendar: You can now add multiple attendees in the Attendees field - Slack: The node now loads both private and public channels - Bug Fixes @@ -7344,7 +7344,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Quick Base - Spontit - Enhanced nodes -- Airable: The Application ID field has been renamed to Base ID, and the Table ID field has been renamed to Table. The List operation now downloads attachments automatically +- Airtable: The Application ID field has been renamed to Base ID, and the Table ID field has been renamed to Table. The List operation now downloads attachments automatically - Harvest: Moved the account field from the credentials to the node parameters. For more details, check out the entry in the [breaking changes](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#0950) page - Bug Fixes - Slack: Fixed an issue with creating channels and inviting users to a channel @@ -7391,7 +7391,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Enhanced nodes - AMQP: Connection is now closed after a message is sent - AMQP Trigger: Added Message per Cycle option to retrieve the specified number of messages from the bus for every cycle -- Hubspot: Added Custom Properties for the Deal resource as Additional Fields +- HubSpot: Added Custom Properties for the Deal resource as Additional Fields - Jira: The node retrieves all the projects for the Project field instead of just 50 - Mattermost: Improved the channel selection - Microsoft SQL: Added TLS parameter for the credentials @@ -7487,7 +7487,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ **Release date:** 2020-10-16 - Bug Fixes -- HTTP Request: Fixed an issue with the Form-Data Mutipart and the RAW/Custom Body Content Types +- HTTP Request: Fixed an issue with the Form-Data Multipart and the RAW/Custom Body Content Types ## n8n@0.88.0 For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.87.2...n8n@0.88.0) for this version.
@@ -7527,7 +7527,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Matrix - Sendy - Vonage -- Wekan +- WeKan - Enhanced nodes - AWS SES: Added Send Template operation for the Email resource and added the Template resource - ClickUp: Added Time Entry and Time Entry Tag resources @@ -7719,8 +7719,8 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Postgres - Webhook - Removed Test-Webhook also in case checkExists fails -- HTTP Request node does not overwrite accept header if it's already set -- Add rawBody to every request so that n8n does not give an error if body is missing +- HTTP Request node doesn'toverwrite accept header if it's already set +- Add rawBody to every request so that n8n doesn'tgive an error if body is missing ## n8n@0.79.0 For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.79.2...n8n@0.79.3) for this version.
@@ -7728,8 +7728,8 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - New nodes - Contentful -- Convertkit -- Convertkit Trigger +- ConvertKit +- ConvertKit Trigger - Paddle - Enhanced nodes - Airtable @@ -7794,7 +7794,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Jira Trigger - Enhanced nodes - GitLab -- NextCloud +- Nextcloud - Pipedrive - QuestDB - Webhooks now support OPTIONS request @@ -7814,7 +7814,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - MongoDB - Pipedrive - Postgres -- Uplead +- UpLead - Webhook - Webhook URLs are now handled independently of the workflow ID by `https://{hostname}/webhook/{path}` instead of the older `https://{hostname}/webhook/{workflow_id}/{node_name}/{path}`. @@ -7838,7 +7838,7 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - Enhanced nodes - Postmark Trigger - Salesforce -- It is now possible to set default values for credentials that get prefilled, and the user cannot change. +- It's now possible to set default values for credentials that get prefilled, and the user can't change. ## n8n@0.72.0 @@ -7862,13 +7862,13 @@ For a comprehensive list of changes, check out the [commits](https://github.com/ - SIGNL4 - Spotify - Enhanced nodes -- Hubspot +- HubSpot - Mailchimp - Typeform - Webflow - Zendesk - Added Postgres SSL support -- It is now possible to deploy n8n under a subfolder +- It's now possible to deploy n8n under a subfolder ## n8n@0.70.0 diff --git a/docs/source-control-environments/understand/git.md b/docs/source-control-environments/understand/git.md index b71fbfea5..4c8fb637a 100644 --- a/docs/source-control-environments/understand/git.md +++ b/docs/source-control-environments/understand/git.md @@ -19,7 +19,7 @@ If you're familiar with Git, don't rely on behaviors matching exactly. In partic This page introduces the Git concepts and terminology used in n8n. It doesn't cover everything you need to set up and manage a repository. The person doing the [Setup](/source-control-environments/setup/) should have some familiarity with Git and with their Git hosting provider. /// note | This is a very brief introduction -Git is a complex topic. This section provides a very brief introduction to the key terms you need when using environments in n8n. If you want to learn about Git in depth, refer to [GitHub | Git and GitHub learning resources](https://docs.github.com/en/get-started/quickstart/git-and-github-learning-resources){:target=_blank .external-link}. +Git's a complex topic. This section provides a very brief introduction to the key terms you need when using environments in n8n. If you want to learn about Git in depth, refer to [GitHub | Git and GitHub learning resources](https://docs.github.com/en/get-started/quickstart/git-and-github-learning-resources){:target=_blank .external-link}. /// ## Git overview @@ -33,7 +33,7 @@ Git uses branches to maintain multiple copies of a document alongside each other ## Local and remote: Moving work between your machine and a Git provider -A common pattern when using Git is to install Git on your own computer, and use a Git provider such as GitHub to work with Git in the cloud. In effect, you have a Git repository (project) on GitHub, and work with copies of it on your local machine. +A common pattern when using Git's to install Git on your own computer, and use a Git provider such as GitHub to work with Git in the cloud. In effect, you have a Git repository (project) on GitHub, and work with copies of it on your local machine. n8n uses this pattern for source control: you'll work with your workflows on your n8n instance, but send them to your Git provider to store them. diff --git a/styles/Vocab/default/accept.txt b/styles/Vocab/default/accept.txt index a3fee596b..b514dfb63 100644 --- a/styles/Vocab/default/accept.txt +++ b/styles/Vocab/default/accept.txt @@ -4,71 +4,126 @@ agent Airtable Asana Authentik +Automizy Axios Backblaze backend Beeminder +Bitly +Bitwarden Boolean boolean +Brandfetch +bcrypt Caddy Citrix +Clearbit Clockify +Contentful +ConvertKit Cron +Crypto Datastore +Demio Dockerfile eksctl +Emelia Enum enum +Eventbrite Fargate +FileMaker Firestore +Freshdesk GIMP +Gotify Hetzner +Homeserver +HubSpot +Humantic invalid Infisical +Iterable +iterable +Jira Keycloak kubectl Kafka Lemlist Luxon +Mailchimp Mattermost +Mautic Metabase Middleware middleware +Mindee n8n namespace +NASA +Nextcloud Nodelinter npm npx Okta Ollama onboarding +Oura +Peekalink +PhantomBuster Pipedrive Pinecone +Plivo Pluralsight Postbin Postgres PostHog +Prefilled +prefilled +Pushbullet +Pushcut Qdrant Realtime +Rekognition +Sendy Serverless serverless Shopify shopify +Spontit +Spotify +Stackby +Storyblok Strapi +Strava +Subfolder +subfolder Supabase +Tapfiliate There are +Todoist Tooltip tooltip Trello +Twake Twilio Typeahead typeahead +Typeform Unformatted unformatted +UpLead URI URIs URL Venafi +Vonage Vuex +Webflow +WeKan +WordPress +Wufoo Xata +Xero +Zendesk Zep