Merge branch 'master' into update/airtable

.github/workflows/deploy.yml

@@ -1,21 +1,37 @@
-name: Deploy
+name: Deploy Docs
 
 on:
-  push:
-    branches:
-      - masterDEACTIVATED
+  workflow_dispatch
 
 jobs:
   build:
-
     runs-on: ubuntu-latest
-
     steps:
-    - uses: actions/checkout@v1
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v1
-      with:
-        node-version: 12.x
-    - name: npm install, build, and test
-      run: |
-        ./deploy.sh
+      - uses: actions/checkout@v2
+      - name: Build and deploy
+        uses: actions/setup-node@v1
+        with:
+          node-version: 12.x
+          persist-credentials: false # otherwise, the token used is the GITHUB_TOKEN, instead of your personal token
+          fetch-depth: 0 # otherwise, you will failed to push refs to dest repo
+      - name: build
+        run: |
+          npm install
+          npm run build
+          cd docs/.vuepress/dist
+          echo 'docs.n8n.io' > CNAME
+      - name: commit
+        run: |
+          cd docs/.vuepress/dist
+          git init
+          git config --local user.email "github-actions@users.noreply.github.com"
+          git config --local user.name "github-actions"
+          git add -A
+          git commit -m "Deploy" -a
+      - name: push
+        uses: ad-m/github-push-action@master
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          branch: gh-pages
+          force: true
+          directory: 'docs/.vuepress/dist'

docs/.vuepress/components/BlogCard.vue

@@ -0,0 +1,92 @@
+<template>
+	<div class="band">
+		<div v-for="i in items" :key="i.id">
+			<a class="card" :href="`https://n8n.io/blog/${i.slug}`" target="_blank" style="text-decoration:none;">
+				<div class="thumb" :style="`background-image: url(${i.feature_image})`"></div>
+				<article>
+					<h1>{{i.title}}</h1>
+					<span>{{i.primary_author.name}}</span>
+				</article>
+			</a>
+		</div>
+	</div>
+</template>
+
+<script>
+export default {
+	props: ['items'],
+}
+</script>
+
+<style scoped>
+.band {
+	width: 100%;
+	max-width: 1240px;
+	margin: 0 auto;
+	display: grid;
+	grid-template-columns: 1fr;
+	grid-template-rows: auto;
+	grid-gap: 20px;
+}
+
+.card {
+	background: white;
+	text-decoration: none;
+	color: #444;
+	box-shadow: 0 2px 5px rgba(0,0,0,0.1);
+	display: flex;
+	flex-direction: column;
+	min-height: 100%;
+	position: relative;
+	top: 0;
+	transition: all .1s ease-in;
+	border-radius: 5px;
+}
+
+.card:hover {
+	top: -2px;
+	box-shadow: 0 4px 5px rgba(0,0,0,0.2);
+}
+
+.card article {
+	padding: 20px;
+	flex: 1;
+	display: flex;
+	flex-direction: column;
+	justify-content: space-between;
+}
+
+.card h1 {
+	font-size: 20px;
+	margin: 0;
+	color: #ff6d5a;
+}
+
+.card span {
+	font-size: 12px;
+	font-weight: bold;
+	color: #999;
+	text-transform: uppercase;
+	letter-spacing: .05em;
+	margin: 2em 0 0 0;
+}
+
+.thumb {
+	padding-bottom: 60%;
+	background-size: cover;
+	background-position: center center;
+	border-top-left-radius: 5px;
+	border-top-right-radius: 5px;
+}
+
+@media (min-width: 30em) {
+	.band {
+		grid-template-columns: 1fr 1fr;
+	}
+}
+@media (min-width: 60em) {
+		.band{
+			grid-template-columns: repeat(2, 1fr);
+	}
+}
+</style>

docs/getting-started/create-your-first-workflow/README.md

@@ -2,5 +2,5 @@
 
 We have created two tutorials that you can follow to get familiar with the process of building workflows in n8n. Feel free to choose one that resonates the most with you and the tasks that you plan to automate.
 
-- Option A: [Daily Weather Notifications with OpenWeatherMap and Twilio ☀️](../daily-weather-notifications/README.md)
-- Option B: [Automate Product Feedback with Typeform, Airtable, and Trello 📈](../get-product-feedback/README.md)
+- Option A: [Daily Weather Notifications with OpenWeatherMap and Twilio ☀️](./daily-weather-notifications/README.md)
+- Option B: [Automate Product Feedback with Typeform, Airtable, and Trello 📈](./get-product-feedback/README.md)

docs/getting-started/create-your-first-workflow/get-product-feedback/README.md

@@ -11,7 +11,7 @@ Here's a video that will take you through the process of creating this workflow.
 You’ll need the following tools and resources to complete the tutorial:
 
 - **n8n** — You can find details on how to install n8n on the [Quickstart](../../quickstart.md) page. Make sure that you start [n8n with tunnel](../../quickstart.md#starting-n8n-with-tunnel).
-- **Typeform account** - You'll need to obtain the credentials for the Typeform Trigger node. You can find instructions on how to obtain them [here](../../../nodes/credentials/typeform/README.md). You will also need to create a form to collect feedback with the following questions:
+- **Typeform account** - You'll need to obtain the credentials for the Typeform Trigger node. You can find instructions on how to obtain them [here](../../../nodes/credentials/Typeform/README.md). You will also need to create a form to collect feedback with the following questions:
 	- What is your name? *(Short Text)*
 	- What is your email address? *(Email)*
 	- Anything else you want to share? *(Long Text)*

docs/getting-started/key-components.md

@@ -12,6 +12,10 @@ A node is an entry point for retrieving data, a function to process data or an e
 
 For example, consider a Google Sheets node. It can be used to retrieve or write data to a Google Sheet.
 
+::: tip 💡 Keep in mind
+If an application you need does not have a dedicated node yet, you can access the data by using the [HTTP Request](../nodes/nodes-library/core-nodes/HTTPRequest/README.md) or the [Webhook](../nodes/nodes-library/core-nodes/Webhook/README.md) node.
+:::
+
 
 ## Trigger Node
 

docs/getting-started/tutorials.md

@@ -2,26 +2,9 @@
 
 ## Blogposts
 
-- [Automating Conference Organization Processes with n8n](https://medium.com/n8n-io/automating-conference-organization-processes-with-n8n-ab8f64a7a520)
-- [Automate Designs with Bannerbear and n8n](https://medium.com/n8n-io/automate-designs-with-bannerbear-and-n8n-2b64c94b54db)
-- [Building an expense tracking app in 10 minutes 📱](https://n8n.io/blog/building-an-expense-tracking-app-in-10-minutes/)
-- [Creating Custom Incident Response Workflows with n8n 🚨](https://medium.com/n8n-io/creating-custom-incident-response-workflows-with-n8n-9baef0bbedb9)
-- [Creating Error Workflows in n8n 🌪](https://medium.com/n8n-io/creating-error-workflows-in-n8n-6e03c9ecbc0f)
-- [Creating scheduled text affirmations with n8n 🤟](https://n8n.io/blog/creating-scheduled-text-affirmations-with-n8n/)
-- [Creating Telegram Bots with n8n, a No-Code Platform](https://medium.com/n8n-io/creating-telegram-bots-with-n8n-a-no-code-platform-fdf1f0928da7)
-- [Creating triggers for n8n workflows using polling ⏲](https://n8n.io/blog/creating-triggers-for-n8n-workflows-using-polling/)
-- [Cross-posting content automatically with n8n ✍️](https://medium.com/n8n-io/automating-cross-posting-blog-posts-using-n8n-%EF%B8%8F-af2a89601810)
-- [Database Monitoring and Alerting with n8n 📡](https://medium.com/n8n-io/database-monitoring-and-alerting-with-n8n-f5082df7bdb2)
-- [Effortless video collaboration with Whereby, Mattermost, and n8n 📹](https://medium.com/n8n-io/effortless-video-collaboration-with-whereby-mattermost-and-n8n-8fc397feb9cb)
-- [Giving kudos to contributors with GitHub, Slack, and n8n 👏](https://medium.com/n8n-io/effortless-video-collaboration-with-whereby-mattermost-and-n8n-8fc397feb9cb)
-- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
-- [HTTP Request Node — The Swiss Army Knife](https://medium.com/n8n-io/http-request-node-the-swiss-army-knife-b14e22283383)
-- [Migrating Community Metrics to Orbit using n8n 📈](https://medium.com/n8n-io/migrating-community-metrics-to-orbit-using-n8n-b293372e8daf)
-- [Smart Factory Automation using IoT and Sensor Data with n8n 🏭](https://medium.com/n8n-io/smart-factory-automation-using-iot-and-sensor-data-with-n8n-27675de9943b)
-- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
-- [Tracking Time Spent in Meetings With Google Calendar, Twilio, and n8n 🗓](https://medium.com/n8n-io/tracking-time-spent-in-meetings-with-google-calendar-twilio-and-n8n-a5d00f77da8c)
-- [Webhooks Fun with n8n and Mattermost 🍸](https://medium.com/n8n-io/webhooks-fun-with-n8n-and-mattermost-4ebf7e2b4d2a)
+<br>
 
+<BlogCard :items="items" />
 
 ## Videos
 
@@ -37,3 +20,23 @@
 - [n8n basics 3/3 - Transforming JSON](https://www.youtube.com/watch?v=wGAEAcfwV8w)
 - [n8n nodes - Using Google Sheets and Google API](https://www.youtube.com/watch?v=KFqx8OmkqVE)
 - [Raspberry Pi as a local server for self-hosting applications like n8n](https://cri.dev/posts/2020-09-12-Raspberry-Pi-as-a-local-server-for-self-hosting-applications/)
+
+<script>
+export default {
+  data () {
+	  return {
+		  items: []
+	  }
+  },
+  beforeMount() {
+	fetch('https://n8n.io/blog/ghost/api/v3/content/posts/?key=416a0c50506dfc7b58227219fd&include=authors&filter=tag:tutorial&limit=all')
+	.then(response => response.json())
+	.then(res => {
+		this.$data.items = res.posts
+	})
+	.catch(error => {
+		console.log(error);
+	})
+  }
+}
+</script>

docs/getting-started/whats-next.md

@@ -1,7 +1,7 @@
 # What's Next?
 
-Addicted to n8n? Here's what you can do next:
+Do you enjoy automating workflows? Here's what you can do next:
 
-- Learn more about the different [nodes](../nodes/nodes.md) in n8n.
-- Check out the [reference](../reference/reference.md) section to learn more about n8n.
-- Check out our [blog](https://medium.com/n8n-io) for tutorials and learn about what others are doing with n8n.
+- See all n8n [nodes](../nodes/nodes-library/README.md) and try out new workflows.
+- Check out the [reference](../reference/README.md) section to learn more about how n8n works.
+- Read our [blog](https://n8n.io/blog/) and discover what others are doing with n8n.

docs/nodes/creating-nodes/node-review-checklist.md

@@ -0,0 +1,70 @@
+# Node review checklist
+
+If you want to create a new node for a service - that's great, thank you! We recommend you take a look at the [existing nodes](https://github.com/n8n-io/n8n/tree/master/packages/nodes-base/nodes) to get an idea of how your code should look and work like.
+
+There are several things to keep in mind when creating the node. To help you, we prepared a checklist that covers the requirements for creating nodes, from preparation to submission.
+
+Make sure you tick the boxes below before submitting a node for review, as this will help our team review your PR easier and faster.
+
+## Preparation
+<input type="checkbox"> Set up your editor for code formatting (indentation, new lines, linting). If you use Visual Studio Code, you can use the <a href="https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-tslint-plugin">TSLint extension</a> for linting.</input> <br>
+<input type="checkbox"> Get credentials (e.g., Client ID, Client Secret, API key, user login, user password, website URL) for the service you are building a node for.</input>
+
+## Development
+
+<input type="checkbox"> Ensure complementary operations to each resource (e.g., create, delete) have been added.</input><br>
+<input type="checkbox"> Ensure the node works with multiple items via one input.</input><br>
+<input type="checkbox"> Ensure the parameters have the correct type.</input><br>
+<input type="checkbox"> Mind the defaults: if the service has a default as true, keep it as true. Changing default values can break the existing workflows of the users.</input><br>
+<input type="checkbox"> Check if the node disposes of everything properly, in particular, if connections were properly closed.</input><br>
+
+## Testing
+
+<input type="checkbox"> Test "create" and "update" operations with all fields/operations.</input><br>
+<input type="checkbox"> Test the `continueOnFail` option with a Function node. (For example, a Widget node has a GET operation that takes a widgetId and returns information on the widget. To test that the workflow continues on fail, set the Widget node to continue on fail, create a Function node, return a valid and an invalid widgetId, connect the Function node to Widget node, and run the workflow. The Widget node should show two items: one with information on the widget and another one with the error from having passed an invalid ID.)</input><br>
+
+## Code formatting
+
+<input type="checkbox"> Ensure the branch lints cleanly by running `npm run tslint`.</input><br>
+<input type="checkbox"> Ensure the indentation is correct. Check this in the editorconfig.</input><br>
+<input type="checkbox"> Ensure there are no extra spaces. Check this in the editorconfig.</input><br>
+<input type="checkbox"> Code comment dividers inside if-branches.</input><br>
+<input type="checkbox"> Use "create/delete" verbs for operations, except for tags, where you should use "add/remove".</input><br>
+
+## Errors and Outputs
+
+<input type="checkbox"> Ensure empty API responses return `{ success: true }`.</input><br>
+<input type="checkbox"> Ensure the error responses are handled and displayed correctly (e.g., malformed requests, requests with invalid credentials) and use the current format. You can check this by making failing requests to the API.</input><br>
+<input type="checkbox"> Check if the response can be simplified and add a simplify function (e.g., <a href="https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/SecurityScorecard/GenericFunctions.ts">SecurityScorecard node</a>).</input><br>
+<input type="checkbox"> Ensure the response from `Create` is consistent with `Get`.</input><br>
+<input type="checkbox"> Ensure the response from `Get All` is consistent with `Get`.</input><br>
+
+## Presentation
+
+<input type="checkbox"> Ensure the primary menu contains only required parameters.</input><br>
+<input type="checkbox"> Ensure a JSON object is not shown in a single column in Table view.</input><br>
+<input type="checkbox"> Make sure all GetAll operations have the fields `return` and `limit`.</input><br>
+<input type="checkbox"> Ensure the property subtitle is set.</input><br>
+<input type="checkbox"> Make sure the pagination (if any) is working correctly. Set Limit 1.</input><br>
+
+## Writing
+
+<input type="checkbox"> Ensure all descriptions are correct and end with a period.</input><br>
+<input type="checkbox"> Ensure that most descriptions exist, excluding redundant ones.</input><br>
+<input type="checkbox"> Ensure IDs in displayNames are capitalized (i.e.: "IDs", not "ids" or "Ids").</input><br>
+<input type="checkbox"> Ensure that IDs, if multiple, have descriptive qualifiers.</input><br>
+<input type="checkbox"> Ensure the `name` property in `description` in the node class is written in camelCase.</input><br>
+<input type="checkbox"> Ensure the file name and the Class name are identical.</input><br>
+
+## Branding
+
+<input type="checkbox"> Ensure the name of the service is written correctly (e.g., "GitHub" not "Github"). If the node is a trigger node, ensure it is named as such, by adding "Trigger" after the service name (e.g., "Trello Trigger").</input><br>
+<input type="checkbox"> Ensure the logo is either a PNG or SVG, ideally the latter. <a href="https://vecta.io/symbols">Vecta</a> is a good website to find SVGs of different applications.</input><br>
+<input type="checkbox"> If the logo is an SVG, ensure the canvas is a perfect square. If the logo is PNG, ensure it is 60x60 pixels and compressed.</input><br>
+<input type="checkbox"> Ensure the border color of the node matches the branding of the service.</input><br>
+
+## Nice-to-haves (optional)
+<input type="checkbox"> Add handler for `continueOnFail`. This feature is included in some of the newest nodes (e.g <a href="https://github.com/n8n-io/n8n/blob/master/packages/nodes-base/nodes/Lemlist/Lemlist.node.ts">Lemlist node</a>) to continue the workflow even if the node's execution fails.</input><br>
+<input type="checkbox"> Remove `required: false` and `description: ''` in the node descriptions (e.g., <a href="https://github.com/n8n-io/n8n/tree/master/packages/nodes-base/nodes/Lemlist/descriptions">Lemlist node</a>).</input><br>
+<input type="checkbox"> At call site, specify first `body` and then `qs`.</input><br>
+<input type="checkbox"> At call site, prepend the endpoint with slash `/` (e.g., "/campaign").</input><br>

docs/nodes/credentials/Bitwarden/README.md

@@ -0,0 +1,36 @@
+---
+permalink: /credentials/bitwarden
+description: Learn to configure credentials for the Bitwarden node in n8n
+---
+
+# Bitwarden
+
+You can use these credentials to authenticate the following nodes with Bitwarden.
+- [Bitwarden](../../nodes-library/nodes/Bitwarden/README.md)
+
+## Prerequisites
+
+Create a [Bitwarden](https://vault.bitwarden.com/#/register?org=teams) organisation account.
+
+## Using API Key
+
+1. Open your Bitwarden [vault](https://vault.bitwarden.com/).
+2. Click on your organisation under the ***ORGANISATIONS*** section.
+3. Click on the ***Settings*** tab.
+4. Click on the ***View API key*** button under the ***API key*** section.
+5. Enter your master password in the ***Master password*** field.
+6. Click on the ***View API key*** button.
+7. Copy the displayed client id.
+8. Enter the name for your credentials in the ***Credentials Name*** field in the 'Bitwarden API' credentials in n8n.
+9. Paste the client id in the ***Client ID*** field in the 'Bitwarden API' credentials in n8n.
+10. Copy the client secret from Bitwarden.
+11. Paste the client secret in the ***Client Secret*** field in the 'Bitwarden API' credentials in n8n.
+12. Click on the ***Create*** button to create your credentials.
+
+**Note:** If you're hosting Bitwarden on your server, select 'Self-hosted' from the ***Environment*** dropdown list. You also need to enter the domain of your hosted instance in the ***Self-hosted domain*** field.
+
+The following video demonstrates the steps mentioned above.
+
+<div class="video-container">
+    <iframe width="840" height="472.5" src="https://www.youtube.com/embed/lK-XdhKDSkk" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>

docs/nodes/credentials/Copper/README.md

@@ -6,6 +6,7 @@ description: Learn to configure credentials for the Copper node in n8n
 # Copper
 
 You can use these credentials to authenticate the following nodes with Copper.
+- [Copper](../../nodes-library/nodes/Copper/README.md)
 - [Copper Trigger](../../nodes-library/trigger-nodes/CopperTrigger/README.md)
 
 ## Prerequisites
@@ -15,10 +16,17 @@ Create a [Copper](https://www.copper.com/) account.
 ## Using Access Token
 
 1. Open your Copper dashboard.
-2. Click on Settings.
-3. Click on Integrations, API Keys.
-4. Generate API key.
-5. Use selected API key and your registered email in your Copper node credentials in n8n.
+2. Click on the ***Settings*** tab on the left-sidebar.
+3. Click on ***Integrations*** and select ***API Keys***.
+4. Click on the ***GENERATE API KEY*** button.
+5. Copy the displayed API key.
+6. Enter the name for your credentials in the ***Credentials Name*** field in the 'Copper API' credentials in n8n.
+7. Paste the API key in the ***API Key*** field in the 'Copper API' credentials in n8n.
+8. Enter the email address in the ***Email*** field in the 'Copper API' credentials in n8n.
+9. Click the ***Create*** button to create your credentials in n8n.
 
+The following video demonstrates the steps mentioned above.
 
-![Getting Copper credentials](./using-access-token.gif)
+<div class="video-container">
+    <iframe width="840" height="472.5" src="https://www.youtube.com/embed/4yV9GI3UF_o" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>

docs/nodes/credentials/Plivo/README.md

@@ -0,0 +1,29 @@
+---
+permalink: /credentials/plivo
+description: Learn to configure credentials for the Plivo node in n8n
+---
+
+# Plivo
+
+You can use these credentials to authenticate the following nodes with Plivo.
+- [Plivo](../../nodes-library/nodes/Plivo/README.md)
+
+## Prerequisites
+
+Create a [Plivo](https://console.plivo.com/accounts/register/) account.
+
+## Using Access Token
+
+1. Open your Plivo [console](https://console.plivo.com/dashboard/).
+2. Copy the displayed Auth ID under the ***Account and Payments*** section.
+3. Enter a name for your credentials in the ***Credentials Name*** field in the 'Plivo API' credentials in n8n.
+4. Paste the Auth ID in the ***Auth ID*** field in the 'Plivo API' credentials in n8n.
+5. Copy the Auth Token displayed on your Plivo console.
+6. Paste the Auth Token in the ***Auth Token*** field in the 'Plivo API' credentials in n8n.
+7. Click on the ***Create*** button to create your credentials.
+
+The following video demonstrates the steps mentioned above.
+
+<div class="video-container">
+<iframe width="840" height="472.5" src="https://www.youtube.com/embed/Zui5fzFtO1E" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+</div>

docs/nodes/nodes-library/core-nodes/DateTime/README.md

@@ -71,16 +71,16 @@ You can use the following values in the ***From Format*** field:
 | DD-MM-YYYY | 19-03-2021 | Date, month, and year separated by `-` |
 | DD/MM/YYYY | 19/03/2021 | Date, month, and year separated by `/` |
 | DD.MM.YYYY | 19.03.2021 | Date, month, and year separated by `.` |
-| DD/MM/YYYY HH:MM:SS | 19.03.2021 08:00:00 | Date, month, year, hours, minutes, and seconds|
+| DD.MM.YYYY HH:mm:ss | 19.03.2021 08:00:00 | Date, month, year, hours, minutes, and seconds|
 | MM/DD/YYYY | 03/19/2021 | Month, date, and year separated by `/` |
 | MM-DD-YYYY | 03-19-2021 | Month, date, and year separated by `-` |
 | MM.DD.YYYY | 03.19.2021 | Month, date, and year separated by `.` |
-| MM/DD/YYYY HH:MM:SS | 03/19/2021 08:00:00 | Month, date, year, hours, minutes, and seconds |
+| MM/DD/YYYY HH:mm:ss | 03/19/2021 08:00:00 | Month, date, year, hours, minutes, and seconds |
 | YYYY/MM/DD | 2021/03/19 | Year, month, and date separated by `/` |
 | YYYY-MM-DD | 2021-03-19 | Year, month, and date separated by `-` |
 | YYYY.MM.DD | 2021.03.19 | Year, month, and date separated by `.` |
-| YYYY/MM/DD HH:MM:SS | 2021/03/19 08:00:00 | Year, month, date, hours, minutes, and seconds |
+| YYYY/MM/DD HH:mm:ss | 2021/03/19 08:00:00 | Year, month, date, hours, minutes, and seconds |
 | MMMM DD YYYY | March 03 2021 | Month, date, and year |
-| MMMM DD YYYY HH:MM:SS | March 03 2021 08:00:00 | Month, date, year, hours, minutes, and seconds |
+| MMMM DD YYYY HH:mm:ss | March 03 2021 08:00:00 | Month, date, year, hours, minutes, and seconds |
 | DD MMMM YYYY | 03 March 2021 | Date, month, and year |
-| DD MMMM YYYY HH:MM:SS | 03 March 2021 08:00:00 | Date, month, year, hours, minutes, and seconds |
+| DD MMMM YYYY HH:mm:ss | 03 March 2021 08:00:00 | Date, month, year, hours, minutes, and seconds |

docs/nodes/nodes-library/core-nodes/IMAPEmail/README.md

@@ -32,6 +32,6 @@ The final workflow should look like the following image.
 
 ### 1. IMAP Email node
 
-1. First of all, you'll have to enter credentials for the IMAP Email node. You can find out how to do that [here](../../../credentials/IMAPEmail/README.md).
+1. First of all, you'll have to enter credentials for the IMAP Email node. You can find out how to do that [here](../../../credentials/IMAP/README.md).
 2. Enter the name of the mailbox from which you want to receive emails in the ***Mailbox Name*** field.
 3. Click on ***Execute Node*** to run the workflow.

docs/nodes/nodes-library/core-nodes/MoveBinaryData/README.md

@@ -12,19 +12,21 @@ The Move Binary Data node is useful to move data between binary and JSON propert
 - ***Mode:*** This field specifies from where and to the data should be moved.
     - Binary to JSON
     - JSON to Binary
-- ***Set all Data:*** If set to active, all JSON data is replaced with the data retrieved from binary key. If it is not set to active, the data will be written to a single key. This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list. 
+- ***Set all Data:*** If set to active, all JSON data is replaced with the data retrieved from binary key. If it is not set to active, the data will be written to a single key. This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list.
 - ***Source Key:*** The name of the binary key to get data from. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.currentKey". This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list.
 - ***Destination Key:*** The name the JSON key to copy data to. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.newKey". This field is displayed when 'Binary to JSON' is selected from the ***Mode*** dropdown list.
-- ***Convert all Data:*** If set to active all JSON data will be converted to binary. If it is not set to active only the data with one key will be converted. This field is displayed when 'JSON to Binary' is selected from the ***Mode*** dropdown list. 
+- ***Convert all Data:*** If set to active all JSON data will be converted to binary. If it is not set to active only the data with one key will be converted. This field is displayed when 'JSON to Binary' is selected from the ***Mode*** dropdown list.
 - ***Destination Key:*** The name of the binary key to copy data to. It is also possible to define deep keys by using dot-notation. For example, "level1.level2.newKey". This field is displayed when 'JSON to Binary' is selected from the ***Mode*** dropdown list.
 
 - ***Options***
     - ***Keep Source:*** Keep the source key. By default it gets deleted.
+    - ***Encoding:*** Set the encoding of the data stream.
     - The following are the options when 'Binary to JSON' is selected from the ***Mode*** dropdown list.
-        - ***Encoding:*** Set the encoding of the datastream.
         - ***JSON Parse:*** Run JSON parse on the data to get proper object data. This field is displayed when ***Set all Data*** is set to 'false'.
         - ***Keep As Base64:*** Keeps the binary data as base64 string. This field is displayed when ***Set all Data*** is set to 'false'.
+        - ***Strip BOM:*** Strip the byte order mark (BOM) from the string. This field is displayed when ***Encoding*** is selected.
     - The following are the options when 'JSON to Binary' is selected from the ***Mode*** dropdown list.
+        - ***Add BOM:*** Add the byte order mark (BOM) to the string. This field is displayed when ***Encoding*** is selected.
         - ***File Name:*** The file name to set.
         - ***Mime Type:*** The mime-type to set. By default the JSON mime-type will be set.
         - ***Use Raw Data:*** Use data as is and do not stringify it.

docs/nodes/nodes-library/nodes/AWSSES/README.md

@@ -13,6 +13,15 @@ You can find authentication information for this node [here](../../../credential
 
 ## Basic Operations
 
+::: details Custom Verification Email
+- Create a new custom verification email template
+- Delete an existing custom verification email template
+- Get the custom email verification template
+- Get all the existing custom verification email templates for your account
+- Add an email address to the list of identities
+- Update an existing custom verification email template
+:::
+
 ::: details Email
 - Send Email
 - Send Template

docs/nodes/nodes-library/nodes/Affinity/README.md

@@ -13,6 +13,18 @@ You can find authentication information for this node [here](../../../credential
 
 ## Basic Operations
 
+::: details List
+- Get a list
+- Get all lists
+:::
+
+::: details List Entry
+- Create a list entry
+- Delete a list entry
+- Get a list entry
+- Get all list entries
+:::
+
 ::: details Organization
 - Create an organization
 - Delete an organization

docs/nodes/nodes-library/nodes/Bitwarden/README.md

@@ -0,0 +1,122 @@
+---
+permalink: /nodes/n8n-nodes-base.bitwarden
+description: Learn how to use the Bitwarden node in n8n
+---
+
+# Bitwarden
+
+[Bitwarden](https://www.bitwarden.com/) is an open-source password management solution for individuals, teams, and business organizations.
+
+::: tip 🔑 Credentials
+You can find authentication information for this node [here](../../../credentials/Bitwarden/README.md).
+:::
+
+
+## Basic Operations
+
+::: details Collection
+- Delete a collection
+- Get a collection
+- Get all collections
+- Update a collection
+:::
+
+::: details Event
+- Get all events
+:::
+
+::: details Group
+- Create a group
+- Delete a group
+- Get a group
+- Get all groups
+- Get members of a group
+- Update a group
+- Update members of a group
+:::
+
+::: details Member
+- Create a member
+- Delete a member
+- Get a member
+- Get all members
+- Get groups of a member
+- Update a member
+- Update groups of a member
+:::
+
+## Example Usage
+
+This workflow allows you to create a group, add members to the group, and get the members of the group in Bitwarden. You can also find the [workflow](https://n8n.io/workflows/1001) on n8n.io. This example usage workflow would use the following nodes.
+- [Start](../../core-nodes/Start/README.md)
+- [Bitwarden]()
+
+The final workflow should look like the following image.
+
+![A workflow with the Bitwarden node](./workflow.png)
+
+### 1. Start node
+
+The start node exists by default when you create a new workflow.
+
+### 2. Bitwarden node (create: group)
+
+This node will create a new group called `documentation` in Bitwarden.
+
+1. First of all, you'll have to enter credentials for the Bitwarden node. You can find out how to do that [here](../../../credentials/Bitwarden/README.md).
+2. Select 'Group' from the ***Resource*** dropdown list.
+3. Select 'Create' from the ***Operation*** dropdown list.
+4. Enter `documentation` in the ***Name*** field.
+5. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the node creates a new group in Bitwarden.
+
+![Using the Bitwarden node to create a new group](./Bitwarden_node.png)
+
+### 3. Bitwarden1 node (getAll: member)
+
+This node will get all the members from Bitwarden.
+
+1. Select the credentials that you entered in the previous node.
+2. Select 'Member' from the ***Resource*** dropdown list.
+3. Select 'Get All' from the ***Operation*** dropdown list.
+4. Toggle ***Return All*** to `true`.
+5. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the node retrieves all the members from Bitwarden.
+
+![Using the Bitwarden node to get all the members](./Bitwarden1_node.png)
+
+### 4. Bitwarden2 node (updateMembers: group)
+
+This node will update all the members in the group that we created earlier.
+::: v-pre
+1. Select the credentials that you entered in the previous node.
+2. Select 'Group' from the ***Resource*** dropdown list.
+3. Select 'Update Members' from the ***Operation*** dropdown list.
+4. Click on the gears icon next to the ***Group ID*** field and click on ***Add Expression***.
+5. Select the following in the ***Variable Selector*** section: Nodes > Bitwarden > Output Data > JSON > id. You can also add the following expression: `{{$node["Bitwarden"].json["id"]}}`.
+6. Click on the gears icon next to the ***Member IDs*** field and click on ***Add Expression***.
+7. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`.
+8. Click on ***Execute Node*** to run the node.
+:::
+
+In the screenshot below, you will notice that the node updates the members of the group.
+
+![Using the Bitwarden node to update members in a group](./Bitwarden2_node.png)
+
+### 5. Bitwarden3 node (getMembers: group)
+
+This node will get all the members in the group that we created earlier.
+::: v-pre
+1. Select the credentials that you entered in the previous node.
+2. Select 'Group' from the ***Resource*** dropdown list.
+3. Select 'Get Members' from the ***Operation*** dropdown list.
+4. Click on the gears icon next to the ***Group ID*** field and click on ***Add Expression***.
+5. Select the following in the ***Variable Selector*** section: Nodes > Bitwarden > Output Data > JSON > id. You can also add the following expression: `{{$node["Bitwarden"].json["id"]}}`.
+6. Click on ***Execute Node*** to run the node.
+:::
+
+In the screenshot below, you will notice that the node retrieves the members in the group.
+
+![Using the Bitwarden node to get members in a group](./Bitwarden3_node.png)

docs/nodes/nodes-library/nodes/Box/README.md

@@ -24,6 +24,7 @@ You can find authentication information for this node [here](../../../credential
 
 ::: details Folder
 - Create a folder
+- Get a folder
 - Delete a folder
 - Search files
 :::

docs/nodes/nodes-library/nodes/ClickUp/README.md

@@ -60,28 +60,55 @@ You can find authentication information for this node [here](../../../credential
 - Delete a list
 - Get a list
 - Get all lists
+- Get list members
 - Update a list
 :::
 
+::: details Space Tag
+- Create a space tag
+- Delete a space tag
+- Get all space tags
+- Update a space tag
+:::
+
 ::: details Task
 - Create a task
 - Delete a task
 - Get a task
 - Get all tasks
+- Get task members
 - Set a custom field
 - Update a task
 :::
 
+::: details Task List
+- Add a task to a list
+- Remove a task from a list
+:::
+
+::: details Task Tag
+- Add a tag to a task
+- Remove a tag from a task
+:::
+
 ::: details Task Dependency
 - Create a task dependency
 - Delete a task dependency
 :::
 
-::: details Time Tracking
-- Log time on task
-- Delete a logged time
-- Get all logging times on task
-- Update a logged time
+::: details Time Entry
+- Create a time entry
+- Delete a time entry
+- Get a time entry
+- Start a time entry
+- Stop the current running timer
+- Update a time entry
+:::
+
+::: details Time Entry Tag
+- Add a tag to a time entry
+- Get all time entry tags
+- Remove a tag from time entry
 :::
 
 ## Example Usage

docs/nodes/nodes-library/nodes/Copper/README.md

@@ -0,0 +1,138 @@
+---
+permalink: /nodes/n8n-nodes-base.copper
+description: Learn how to use the Copper node in n8n
+---
+
+# Copper
+
+[Copper](https://www.copper.com/) is a CRM that focuses on strong integration with Google's G Suite, targeted towards small and medium-sized businesses.
+
+::: tip 🔑 Credentials
+You can find authentication information for this node [here](../../../credentials/Copper/README.md).
+:::
+
+## Basic Operations
+
+::: details Company
+- Create a company
+- Delete a company
+- Get a company
+- Get all companies
+- Update a company
+:::
+
+::: details Customer Source
+- Get all customer sources
+:::
+
+::: details Lead
+- Create a lead
+- Delete a lead
+- Get a lead
+- Get all leads
+- Update a lead
+:::
+
+::: details Opportunity
+- Create an opportunity
+- Delete an opportunity
+- Get an opportunity
+- Get all opportunities
+- Update an opportunity
+:::
+
+::: details Person
+- Create a person
+- Delete a person
+- Get a person
+- Get all persons
+- Update a person
+:::
+
+::: details Project
+- Create a project
+- Delete a project
+- Get a project
+- Get all projects
+- Update a project
+:::
+
+::: details Task
+- Create a task
+- Delete a task
+- Get a task
+- Get all tasks
+- Update a task
+:::
+
+::: details User
+- Get all users
+:::
+
+## Example Usage
+
+This workflow allows you to create, update, and get a person from Copper. You can also find the [workflow](https://n8n.io/workflows/1021) on n8n.io. This example usage workflow would use the following nodes.
+- [Start](../../core-nodes/Start/README.md)
+- [Copper]()
+
+The final workflow should look like the following image.
+
+![A workflow with the Copper node](./workflow.png)
+
+### 1. Start node
+
+The start node exists by default when you create a new workflow.
+
+### 2. Copper node (create: person)
+
+This node will create a new person in Copper.
+
+1. First of all, you'll have to enter credentials for the Copper node. You can find out how to do that [here](../../../credentials/Copper/README.md).
+2. Select 'Person' from the ***Resource*** dropdown list.
+3. Enter the name of the lead in the ***Name*** field.
+4. Click on the ***Add Field*** button and select 'Emails' from the dropdown list.
+5. Click on the ***Add Email*** button.
+6. Enter the email in the ***Email*** field.
+7. Enter the category of the email in the ***Category*** field.
+8. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the node creates a new person in Copper.
+
+![Using the Copper node to create a new person](./Copper_node.png)
+
+
+### 3. Copper1 node (update: person)
+
+This node will update the information of the person that we created using the previous node.
+::: v-pre
+1. Select the credentials that you entered in the previous Copper node.
+2. Select 'Person' from the ***Resource*** dropdown list.
+3. Select 'Update' from the ***Operation*** dropdown list.
+4. Click on the gears icon next to the ***Person ID*** field and click on ***Add Expression***.
+5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`.
+6. Click on the ***Add Field*** button and select 'Phone Numbers' from the dropdown list.
+7. Click on the ***Add Phone Number*** field.
+8. Enter the phone number in the ***Phone Number*** field.
+9. Enter the category in the ***Category*** field.
+10. Click on ***Execute Node*** to run the node.
+:::
+
+In the screenshot below, you will notice that the node updates the information of the person that got created previously.
+
+![Using the Copper node to update the information of a person](./Copper1_node.png)
+
+### 4. Copper2 node (get: person)
+
+This node will retrieve the information of the person that we created earlier.
+
+::: v-pre
+1. Select the credentials that you entered in the previous Copper node.
+2. Select 'Person' from the ***Resource*** dropdown list.
+3. Select 'Update' from the ***Operation*** dropdown list.
+4. Click on the gears icon next to the ***Person ID*** field and click on ***Add Expression***.
+5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > id. You can also add the following expression: `{{$json["id"]}}`.
+6. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the node retrieves the information of the person that we created earlier.
+
+![Using the Copper node to retrieve the information of a person](./Copper2_node.png)

docs/nodes/nodes-library/nodes/Dropbox/README.md

@@ -29,6 +29,10 @@ You can find authentication information for this node [here](../../../credential
 - Move a folder
 :::
 
+::: details Search
+- Query
+:::
+
 ## Example Usage
 
 This workflow allows you to create a folder in Dropbox, upload a file into that folder, and list the contents of the folder. You can also find the [workflow](https://n8n.io/workflows/615) on n8n.io. This example usage workflow uses the following nodes.

docs/nodes/nodes-library/nodes/GoogleDrive/README.md

@@ -27,6 +27,7 @@ You can find authentication information for this node [here](../../../credential
 - Download a file
 - List files and folders
 - Share a file
+- Update a file
 - Upload a file
 :::
 

docs/nodes/nodes-library/nodes/Jira/README.md

@@ -24,6 +24,27 @@ You can find authentication information for this node [here](../../../credential
 - Delete an issue
 :::
 
+::: details Issue Attachment
+- Add attachment to an issue
+- Get an attachment
+- Get all attachments
+- Remove an attachment
+:::
+
+::: details Issue Comment
+- Add comment to issue
+- Get a comment
+- Get all comments
+- Remove a comment
+- Update a comment
+:::
+
+::: details User
+- Create a new user
+- Delete a user
+- Retrieve a user
+:::
+
 ## Example Usage
 
 This workflow allows you to create a new issue in Jira. You can also find the [workflow](https://n8n.io/workflows/459) on the website. This example usage workflow would use the following two nodes.

docs/nodes/nodes-library/nodes/Mattermost/README.md

@@ -25,6 +25,13 @@ You can find authentication information for this node [here](../../../credential
 ::: details Message
 - Soft delete a post, by marking the post as deleted in the database
 - Post a message into a channel
+- Post an ephemeral message into a channel
+:::
+
+::: details Reaction
+- Add a reaction to a post
+- Remove a reaction from a post
+- Get all the reactions to one or more posts
 :::
 
 ::: details User

docs/nodes/nodes-library/nodes/MicrosoftTeams/README.md

@@ -26,6 +26,14 @@ You can find authentication information for this node [here](../../../credential
 - Get all messages
 :::
 
+::: details Task
+- Create a task
+- Delete a task
+- Get a task
+- Get all tasks
+- Update a task
+:::
+
 ## Example Usage
 
 This workflow allows you to create, update and send a message to a channel in Microsoft Teams. You can also find the [workflow](https://n8n.io/workflows/680) on n8n.io. This example usage workflow would use the following nodes.

docs/nodes/nodes-library/nodes/Mondaycom/README.md

@@ -28,18 +28,19 @@ You can find authentication information for this node [here](../../../credential
 ::: details Board Group
 - Delete a group in a board
 - Create a group in a board
-- Get boards' groups
+- Get a list of groups in a board
 :::
 
 ::: details Board Item
 - Add an update to an item
-- Change a column value for a board item 
+- Change a column value for a board item
 - Change multiple column values for a board item
 - Create an item in a board's group
 - Delete an item
 - Get an item
 - Get all items
 - Get items by column value
+- Move item to group
 :::
 
 ## Example Usage

docs/nodes/nodes-library/nodes/Plivo/README.md

@@ -0,0 +1,82 @@
+---
+permalink: /nodes/n8n-nodes-base.plivo
+description: Learn how to use the Plivo node in n8n
+---
+
+# Plivo
+
+[Plivo](https://www.plivo.com/) is a cloud communications platform as a service company that allows you to add SMS, MMS, and Voice calling functionality within your apps programmatically.
+
+::: tip 🔑 Credentials
+You can find authentication information for this node [here](../../../credentials/Plivo/README.md).
+:::
+
+## Basic Operations
+
+::: details SMS
+- Send an SMS message
+:::
+
+::: details MMS
+- Send an MMS message (US/Canada only)
+:::
+
+::: details Call
+- Make a voice call
+:::
+
+## Example Usage
+
+This workflow allows you to send daily weather updates via an SMS message using the Plivo node. You can also find the [workflow](https://n8n.io/workflows/1005) on n8n.io. This example usage workflow uses the following nodes.
+- [Cron](../../core-nodes/Cron/README.md)
+- [OpenWeatherMap](../../nodes/OpenWeatherMap/README.md)
+- [Plivo]()
+
+The final workflow should look like the following image.
+
+![A workflow with the Plivo node](./workflow.png)
+
+### 1. Cron node
+
+The Cron node will trigger the workflow daily at 9 AM.
+
+1. Click on ***Add Cron Time***.
+2. Set hours to 9 in the ***Hour*** field.
+3. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the Cron node is configured to trigger the workflow every day at 9 AM.
+
+![Using the Cron node to trigger the workflow daily at 9 am](./Cron_node.png)
+
+### 2. OpenWeatherMap node (Current Weather)
+
+This node will return data about the current weather in Berlin. To get the weather updates for your city, you can enter the name of your city instead.
+
+1. First of all, you'll have to enter credentials for the OpenWeatherMap node. You can find out how to do that [here](../../../credentials/OpenWeatherMap/README.md).
+2. Enter `berlin` in the ***City*** field.
+3. Click on ***Execute Node*** to run the node.
+
+In the screenshot below, you will notice that the node returns data about the current weather in Berlin.
+
+![Using the OpenWeatherMap node to get weather updates for Berlin](./OpenWeatherMap_node.png)
+
+### 3. Plivo node (send: sms)
+
+This node will send an SMS with the weather update, which was sent by the previous node.
+
+1. First of all, you'll have to enter credentials for the Plivo node. You can find out how to do that [here](../../../credentials/Plivo/README.md).
+2. Enter a Plivo phone number in the ***From*** field.
+3. Enter the receiver's phone number in the ***To*** field.
+4. Click on the gears icon next to the ***Message*** field and click on ***Add Expression***.
+::: v-pre
+5. Enter the following message in the ***Expression*** field: `Hey! The temperature outside is {{$node["OpenWeatherMap"].json["main"]["temp"]}}°C.`.
+6. Click on ***Execute Node*** to run the node.
+:::
+
+In the screenshot below, you will notice that the node sends an SMS to the phone number that we specified with the weather update.
+
+![Using the Plivo node to send weather updates via SMS](./Plivo_node.png)
+
+::: tip 💡 Activate workflow for production
+You'll need to save the workflow and then click on the Activate toggle on the top right of the screen to activate the workflow. Your workflow will then be triggered as specified by the settings in the Cron node.
+:::

docs/nodes/nodes-library/nodes/SendGrid/README.md

@@ -28,6 +28,10 @@ You can find authentication information for this node [here](../../../credential
 - Update a list
 :::
 
+::: detials Mail
+- Send an email
+:::
+
 ## Example Usage
 
 This workflow allows you to create, update and get a contact using the SendGrid node. You can also find the [workflow](https://n8n.io/workflows/901) on n8n.io. This example usage workflow uses the following nodes.

docs/nodes/nodes-library/nodes/Spotify/README.md

@@ -15,6 +15,7 @@ You can find authentication information for this node [here](../../../credential
 
 ::: details Album
 - Get an album by URI or ID
+- Get a list of new album releases
 - Get an album's tracks by URI or ID
 :::
 
@@ -25,6 +26,10 @@ You can find authentication information for this node [here](../../../credential
 - Get an artist's top tracks by URI or ID
 :::
 
+::: details Library
+- Get the user's liked tracks
+:::
+
 ::: details Player
 - Add a song to your queue
 - Get your currently playing track
@@ -37,6 +42,7 @@ You can find authentication information for this node [here](../../../credential
 
 ::: details Playlist
 - Add tracks from a playlist by track and playlist URI or ID
+- Create a new playlist
 - Get a playlist by URI or ID
 - Get a playlist's tracks by URI or ID
 - Get a user's playlists
@@ -69,4 +75,3 @@ The start node exists by default when you create a new workflow.
 3. Click on *Execute Node* to run the workflow.
 
 ![Spotify URI](./spotifyURI.gif)
-

docs/nodes/nodes-library/nodes/Telegram/README.md

@@ -23,13 +23,22 @@ You can find authentication information for this node [here](../../../credential
 
 ::: details Callback
 - Send an answer to a callback query sent from the inline keyboard
+- Send an answer to a callback query from inline bot
+:::
+
+::: details File
+- Get a file
 :::
 
 ::: details Message
 - Edit a text message
+- Pin a chat message
+- Unpin a chat message
+- Send an animated file
 - Send an audio file
 - Send a chat action
 - Send a document
+- Send a location
 - Send a text message
 - Send a group of photos or videos to an album
 - Send a photo

docs/nodes/nodes-library/nodes/TheHive/README.md

@@ -19,6 +19,8 @@ You can find authentication information for this node [here](../../../credential
 - Execute a responder on a specified alert
 - Get an alert
 - Get all alerts
+- Mark an alert as read
+- Mark an alert as unread
 - Merge an alert into an existing case
 - Promote an alert into a case
 - Update an alert

docs/nodes/nodes-library/nodes/Trello/README.md

@@ -35,6 +35,7 @@ You can find authentication information for this node [here](../../../credential
 :::
 
 ::: details Checklist
+- Create a checklist item
 - Create a new checklist
 - Delete a checklist
 - Delete a checklist item

docs/nodes/nodes-library/nodes/Twitter/README.md

@@ -19,6 +19,7 @@ You can find authentication information for this node [here](../../../credential
 
 ::: details Tweet
 - Create or reply to a tweet
+- Delete a tweet
 - Search tweets
 - Like a tweet
 - Retweet a tweet

docs/nodes/nodes-library/nodes/uProc/README.md

@@ -87,6 +87,9 @@ You can find authentication information for this node [here](../../../credential
 - Send a custom invitation message if a profile is connected or a custom message otherwise
 - Visits a profile to show interest and get profile views in return from contact, increasing your LinkedIn network
 - Send a custom private message to a connected LinkedIn profile
+- Get an email by contact's LinkedIn profile URI
+- Discover an email by company's name and prospect's full name
+- Discover an email by company's website or domain and prospect's full name
 :::
 
 ::: details Company
@@ -359,6 +362,7 @@ You can find authentication information for this node [here](../../../credential
 - Allows checking if an ISBN13 code has a valid format
 - Check if a UPC exists
 - Check if a UPC has a valid format
+- Get ASIN by EAN
 - Get a book by author's surname
 - Get all publications by category
 - Get book data by an editor's name
@@ -368,6 +372,7 @@ You can find authentication information for this node [here](../../../credential
 - Get all books by category
 - Get all books by editor
 - Get all books by title
+- Get EAN code by ASIN code
 - Get product data on a UPC on Amazon Marketplace
 :::
 

docs/reference/changelog.md

@@ -2,6 +2,51 @@
 
 🛠 = Version contains a breaking change. Check out the list of all the breaking changes [here](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md).
 
+## n8n@0.114.0
+For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.113.0...n8n@0.114.0) for this version.<br />
+**Release date:** 2021-04-03
+
+- New nodes
+	- AWS SQS
+	- Copper
+	- ERPNext
+	- Oura
+- Enhanced node
+	- Google Drive: Added support for creating folders for shared drives
+	- Google Sheets: Added Create and Remove operation to the Sheet resource
+	- Harvest: Added Update operation to the Task resource
+	- Jira: Added Reporter field to the Issue resource
+	- Postgres: Added support for type casting
+- Bug fixes
+	- Bitwarden: Fixed an issue with the Update operation of the Group resource
+	- Cortex: Fixed an issue where only the last item got returned
+	- Invoice Ninja: Fixed an issue with the Project parameter
+	- Salesforce: Fixed an issue with the Get All operation of the Custom Object resource
+- Fixed an issue with the Redis connection to prevent memory leaks
+
+## n8n@0.113.0 🛠
+For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.112.0...n8n@0.113.0) for this version.<br />
+**Release date:** 2021-03-26
+
+- New nodes
+    - Activation Trigger
+    - Plivo
+- Enhanced nodes
+    - ClickUp: Added Space Tag, Task List, and Task Tag resource
+    - GitHub: Added pagination to Get Issues and Get Repositories operations
+    - Mattermost: Added Reaction resource and Post Ephemeral operation
+    - Move Binary Data: Added Encoding and Add BOM option to JSON to Binary mode and Strip BOM to Binary to JSON mode
+    - 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
+- 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
+    - Spotify: Fixed an issue with the Delete operation of the Playlist resource
+- The variable selector now displays empty arrays
+- Fixed a permission issue with the Raspberry Pi Docker image
+
 ## n8n@0.112.0
 For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.111.0...n8n@0.112.0) for this version.<br />
 **Release date:** 2021-03-19

docs/reference/workflow.md

@@ -66,21 +66,6 @@ All information is always present except:
 An "Error Workflow" can be set in the Workflow Settings which can be accessed by pressing the "Workflow" button in the menu on the on the left side. The last option is "Settings". In the window that appears, the "Error Workflow" can be selected via the Dropdown "Error Workflow".
 
 
-## Share Workflows
-
-All workflows are JSON and can be shared with others.
-
-There are multiple ways to download a workflow as JSON to then share it with other people via Email, Slack, Skype, Dropbox, …
-
-  1. Press the "Download" button under the Workflow menu in the sidebar on the left. It then downloads the workflow as a JSON file.
-  1. Select the nodes in the editor which should be exported and then copy them (Ctrl + c). The nodes then get saved as JSON in the clipboard and can be pasted wherever desired (Ctrl + v).
-
-Importing that JSON representation again into n8n can also be done in different ways:
-
-  1. Press "Import from File" or "Import from URL" under the Workflow menu in the sidebar on the left.
-  1. Copy the JSON workflow to the clipboard (Ctrl + c) and then pasting it directly into the editor (Ctrl + v).
-
-
 ## Workflow Settings
 
 On each workflow, it is possible to set some custom settings and overwrite some of the global default settings. Currently, the following settings can be set:
@@ -110,6 +95,10 @@ If the Execution data of the workflow should be saved when it succeeds.
 
 If executions started from the Editor UI should be saved.
 
+### Save Execution Progress
+
+This setting allows you to save the execution data of each node. By setting it to `Yes`, you can resume the workflow from where it stopped in case of an error. However, it may increase latency.
+
 ## Retry Failed Workflow Executions
 
 If your workflow execution fails, you can retry the execution. To retry a failed workflow execution, follow the steps mentioned below: