mirror of
https://github.com/n8n-io/n8n-docs.git
synced 2025-11-20 17:48:34 +00:00
Merge branch 'master' into docs/activation-trigger
This commit is contained in:
commit
e42e3f2804
42
docs/.vuepress/components/FurtherReadingBlog.vue
Normal file
42
docs/.vuepress/components/FurtherReadingBlog.vue
Normal file
@ -0,0 +1,42 @@
|
||||
<template>
|
||||
<ul>
|
||||
<li v-for="i in items" :key="i.label">
|
||||
<a :href="i.url" target="_blank">{{i.label}} {{i.icon}}</a>
|
||||
</li>
|
||||
</ul>
|
||||
</template>
|
||||
|
||||
<script>
|
||||
export default {
|
||||
data () {
|
||||
return {
|
||||
items: []
|
||||
}
|
||||
},
|
||||
props: ['node'],
|
||||
beforeMount() {
|
||||
fetch('https://api.n8n.io/graphql', {
|
||||
method: 'POST',
|
||||
headers: {
|
||||
'Content-Type': 'application/json',
|
||||
},
|
||||
body: JSON.stringify({
|
||||
query: `
|
||||
query GetNode{
|
||||
nodes (where: {displayName:"${this.node}"}){
|
||||
displayName
|
||||
codex
|
||||
}
|
||||
}
|
||||
`
|
||||
})
|
||||
})
|
||||
.then(response => response.json())
|
||||
.then(res => {
|
||||
this.$data.items = res.data.nodes[0].codex.data.resources.generic
|
||||
console.log(this.items)
|
||||
})
|
||||
.catch(error => console.log(error))
|
||||
}
|
||||
}
|
||||
</script>
|
||||
47
docs/.vuepress/components/NodeCard.vue
Normal file
47
docs/.vuepress/components/NodeCard.vue
Normal file
@ -0,0 +1,47 @@
|
||||
<template>
|
||||
<div class="container">
|
||||
<div v-for="i in items" :key="i.name">
|
||||
<a :href="`/nodes/${i.name}`" class="card-wrapper">
|
||||
<div class="card" v-if="i.iconData.fileBuffer">
|
||||
<div class="image-container">
|
||||
<div style="width: 100%; height: 100%;">
|
||||
<img :src="i.iconData.fileBuffer" style="width: 100%; height: 100%;">
|
||||
</div>
|
||||
</div>
|
||||
<p>{{i.displayName}}</p>
|
||||
</div>
|
||||
</a>
|
||||
</div>
|
||||
</div>
|
||||
</template>
|
||||
|
||||
<script>
|
||||
export default {
|
||||
props: ['items'],
|
||||
}
|
||||
</script>
|
||||
|
||||
<style scoped>
|
||||
.container {
|
||||
display:flex;
|
||||
flex-wrap:wrap;
|
||||
justify-content:center;
|
||||
}
|
||||
.card-wrapper {
|
||||
border-radius: 4px;
|
||||
text-decoration:none;
|
||||
}
|
||||
.card {
|
||||
border-radius: 4px;
|
||||
padding: .8em .6em;
|
||||
margin: .6em;
|
||||
text-align: center;
|
||||
width: 100px;
|
||||
}
|
||||
.image-container {
|
||||
width: 60px;
|
||||
height: 60px;
|
||||
line-height: 60px;
|
||||
margin:auto;
|
||||
}
|
||||
</style>
|
||||
40
docs/nodes/credentials/ERPNext/README.md
Normal file
40
docs/nodes/credentials/ERPNext/README.md
Normal file
@ -0,0 +1,40 @@
|
||||
---
|
||||
permalink: /credentials/erpnext
|
||||
description: Learn to configure credentials for the Emelia node in n8n
|
||||
---
|
||||
|
||||
# ERPNext
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Emelia.
|
||||
- [ERPNext](../../nodes-library/nodes/ERPNext/README.md)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Create a [ERPNext](https://erpnext.com) account.
|
||||
|
||||
## Using API Key
|
||||
|
||||
1. Open your ERPNext dashboard page.
|
||||
2. Click on ***Settings*** on the top and select 'My Settings'.
|
||||
3. Scroll down to the bottom of the page and click on ***API Access***.
|
||||
4. Click on the ***Generate Keys*** button.
|
||||
5. Copy the displayed API Secret.
|
||||
6. Enter a name for your credentials in the ***Credentials Name*** field in the 'ERPNext API' credentials in n8n.
|
||||
7. Paste the API Secret in the ***API Secret*** field in the 'ERPNext API' credentials in n8n.
|
||||
8. Copy the API Key from ERPNext.
|
||||
**Note:** You might have to refresh the ERPNext window to view the API Key.
|
||||
9. Paste the API Key in the ***API Key*** field in the 'ERPNext API' credentials in n8n.
|
||||
10. Enter the subdomain of your ERPNext account in the ***Subdomain*** field in the 'ERPNext API' credentials in n8n. Refer to the [FAQs](#how-to-find-the-subdomain-of-an-erpnext-account) to learn how to get your subdomain.
|
||||
11. Click on the ***Create*** button to create your credentials in n8n.
|
||||
|
||||
The following video demonstrates the steps mentioned above.
|
||||
|
||||
<div class="video-container">
|
||||
<iframe width="840" height="472.5" src="https://www.youtube.com/embed/Q12DmHS3FL4" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## FAQs
|
||||
|
||||
### How to find the subdomain of an ERPNext account?
|
||||
|
||||
In the address bar of your browser, you can find the subdomain. The string between `https://` and `.erpnext.com` is your subdomain. For example, if the URL in the address bar is `https://n8n.erpnext.com`, the subdomain will be `n8n`.
|
||||
@ -71,9 +71,38 @@ The following video demonstrates the steps mentioned above.
|
||||
<iframe width="840" height="472.5" src="https://www.youtube.com/embed/2SFGl3xBdOA" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## Using Outlook.com
|
||||
|
||||
1. Enter the name for your credentials in the ***Credentials Name*** field in the 'IMAP' credentials in n8n.
|
||||
2. Enter your email address in the ***User*** field.
|
||||
3. Enter your account password in the ***Password*** field.
|
||||
4. Enter `outlook.office365.com` in the ***Host*** field.
|
||||
5. Toggle ***SSL/TLS*** to `true`.
|
||||
6. Click on ***Create*** to create your credentials.
|
||||
|
||||
**Note** If you get a connection error, please follow the steps mentioned in the [FAQs](#how-to-solve-the-connection-error-when-connecting-to-outlook-com).
|
||||
|
||||
The following video demonstrates the steps mentioned above.
|
||||
|
||||
<div class="video-container">
|
||||
<iframe width="840" height="472.5" src="https://www.youtube.com/embed/gCWiILtHnPQ" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
|
||||
</div>
|
||||
|
||||
## FAQs
|
||||
|
||||
### How to solve the connection error when connecting to Outlook.com?
|
||||
|
||||
If you receive a connection error while configuring the credentials for your Outlook account, follow the steps mentioned below:
|
||||
1. Go to [account.live.com/activity](https://account.live.com/activity).
|
||||
2. Sign in using the email address and password of your account.
|
||||
3. Under the ***Recent activity*** section, find the Session Type event that matches the most recent time you received the connection error and click to expand it.
|
||||
4. Select ***This was me*** to let the system know you authorize the IMAP connection.
|
||||
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Set up IMAP for Gmail account](https://support.google.com/mail/answer/7126229?hl=en)
|
||||
- [Sign in with App Passwords for your Gmail Account](https://support.google.com/accounts/answer/185833?hl=en)
|
||||
- [Set up IMAP for Yahoo mail account](https://help.yahoo.com/kb/sln4075.html)
|
||||
- [Sign in with App Passwords for your Yahoo mail Account](https://help.yahoo.com/kb/generate-manage-third-party-passwords-sln15241.html)
|
||||
- [POP, IMAP, and SMTP settings for Outlook.com](https://support.microsoft.com/en-us/office/pop-imap-and-smtp-settings-for-outlook-com-d088b986-291d-42b8-9564-9c414e2aa040)
|
||||
|
||||
@ -56,8 +56,4 @@ If you want to trigger your workflow, for example, every day at 04:08, enter the
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automate Designs with Bannerbear and n8n](https://medium.com/n8n-io/automate-designs-with-bannerbear-and-n8n-2b64c94b54db)
|
||||
- [Creating scheduled text affirmations with n8n 🤟](https://medium.com/n8n-io/creating-scheduled-text-affirmations-with-n8n-1c4189efae19)
|
||||
- [Database Monitoring and Alerting with n8n 📡](https://medium.com/n8n-io/database-monitoring-and-alerting-with-n8n-f5082df7bdb2)
|
||||
- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Cron" />
|
||||
|
||||
@ -57,7 +57,6 @@ The Error Trigger node sends the actual error message thrown by the workflow. Yo
|
||||
|
||||
There is currently no functionality to call an Error Workflow manually.
|
||||
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating Error Workflows in n8n 🌪](https://medium.com/n8n-io/creating-error-workflows-in-n8n-6e03c9ecbc0f)
|
||||
<FurtherReadingBlog node="Error Trigger" />
|
||||
|
||||
@ -121,7 +121,7 @@ ls
|
||||
|
||||
You can also use the [HTTP Request](../../core-nodes/HTTPRequest/README.md) node to make a cURL request.
|
||||
|
||||
If you want to run the curl command in the Execute Command node, you will have to build a Docker image based on the existing n8n image. The default n8n Docker image uses Alpine Linux. You will have to install the curl package.
|
||||
If you want to run the curl command in the Execute Command node, you will have to build a Docker image based on the existing n8n image. The default n8n Docker image uses Alpine Linux. You will have to install the curl package.
|
||||
1. Create a file named Dockerfile.
|
||||
2. Add the below code snippet to the Dockerfile.
|
||||
```
|
||||
@ -134,3 +134,7 @@ docker build -t n8n-curl
|
||||
```
|
||||
4. Replace the Docker image you used before. For example, replace `n8nio/n8n` with `n8n-curl`.
|
||||
5. Run the newly created Docker image, and you will now be able to execute ssh via the Execute Command-Node.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Execute Command" />
|
||||
|
||||
@ -153,9 +153,4 @@ is active and it gets called by a Trigger or Webhook, the static data will be sa
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating triggers for n8n workflows using polling ⏲](https://n8n.io/blog/creating-triggers-for-n8n-workflows-using-polling/)
|
||||
- [Giving kudos to contributors with GitHub, Slack, and n8n 👏](https://medium.com/n8n-io/giving-kudos-to-contributors-with-github-slack-and-n8n-b3f5f4a653a6)
|
||||
- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Function" />
|
||||
|
||||
@ -76,4 +76,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Giving kudos to contributors with GitHub, Slack, and n8n 👏](https://medium.com/n8n-io/giving-kudos-to-contributors-with-github-slack-and-n8n-b3f5f4a653a6)
|
||||
<FurtherReadingBlog node="GraphQL" />
|
||||
|
||||
@ -12,8 +12,8 @@ The HTML Extract node is useful to extract the HTML content of a webpage.
|
||||
- **Source Data:** This field specifies if HTML should be read from binary or JSON data. In this dropdown list, there are two options.
|
||||
- Binary
|
||||
- JSON
|
||||
- ***JSON Property:*** The name of the JSON property in which the HTML (from which to extract the data) can be found. This field is displayed when 'JSON' is selected in the ***Source Data*** field.
|
||||
- ***Binary Property:*** The name of the binary property in which the HTML (from which to extract the data) can be found. This field is displayed when 'Binary' is selected in the ***Source Data*** field.
|
||||
- ***JSON Property:*** The name of the JSON property in which the HTML (from which to extract the data) can be found. This field is displayed when 'JSON' is selected in the ***Source Data*** field.
|
||||
- ***Binary Property:*** The name of the binary property in which the HTML (from which to extract the data) can be found. This field is displayed when 'Binary' is selected in the ***Source Data*** field.
|
||||
The property can either contain a string or an array of strings.
|
||||
- ***Extraction Values:***
|
||||
- ***Key:*** The key under which the extracted value should be saved.
|
||||
@ -84,4 +84,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [HTTP Request Node — The Swiss Army Knife](https://medium.com/n8n-io/http-request-node-the-swiss-army-knife-b14e22283383)
|
||||
<FurtherReadingBlog node="HTML Extract" />
|
||||
|
||||
@ -129,8 +129,4 @@ When the node gets executed, you will receive the HTTP status code, the HTTP sta
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Building an expense tracking app in 10 minutes 📱](https://medium.com/n8n-io/building-an-expense-tracking-app-in-10-minutes-74b0cececc90)
|
||||
- [Creating scheduled text affirmations with n8n 🤟](https://medium.com/n8n-io/creating-scheduled-text-affirmations-with-n8n-1c4189efae19)
|
||||
- [Cross-posting content automatically with n8n ✍️](https://medium.com/n8n-io/automating-cross-posting-blog-posts-using-n8n-%EF%B8%8F-af2a89601810)
|
||||
- [HTTP Request Node — The Swiss Army Knife](https://medium.com/n8n-io/http-request-node-the-swiss-army-knife-b14e22283383)
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
<FurtherReadingBlog node="HTTP Request" />
|
||||
|
||||
@ -35,3 +35,7 @@ The final workflow should look like the following image.
|
||||
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.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="EmailReadImap" />
|
||||
@ -118,4 +118,4 @@ return [
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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)
|
||||
<FurtherReadingBlog node="IF" />
|
||||
|
||||
@ -22,4 +22,4 @@ The Interval node has two fields:
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating triggers for n8n workflows using polling ⏲](https://n8n.io/blog/creating-triggers-for-n8n-workflows-using-polling/)
|
||||
<FurtherReadingBlog node="Interval" />
|
||||
|
||||
@ -119,5 +119,4 @@ return [
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Migrating Community Metrics to Orbit using n8n 📈](https://medium.com/n8n-io/migrating-community-metrics-to-orbit-using-n8n-b293372e8daf)
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
<FurtherReadingBlog node="Merge" />
|
||||
|
||||
@ -8,3 +8,7 @@ description: Learn how to use the No Operation, do nothing node in n8n
|
||||
The No Operation, do nothing node is used when you don't want to perform any operations. The purpose of this node is to make the workflow easier to read and understand where the flow of data stops. This can sometimes help others with a better understanding of the workflow, visually.
|
||||
|
||||
As an example, checkout how this node is being used in the [Create Your First Workflow](../../../../getting-started/create-your-first-workflow/create-your-first-workflow/README.md) guide.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="No Operation, do nothing" />
|
||||
@ -1,3 +1,21 @@
|
||||
# Code Nodes
|
||||
# Core Nodes
|
||||
|
||||
This section contains information about all the core nodes in n8n. Each node documentation contains information on the available resources and operations along with an example workflow.
|
||||
|
||||
<!-- <NodeCard :items="items" /> -->
|
||||
<div v-for="i in items" :key="i.name">
|
||||
<a :href="`/nodes/${i.name}`">
|
||||
<p>{{i.displayName}}</p>
|
||||
</a>
|
||||
</div>
|
||||
|
||||
<script>
|
||||
import data from './core-nodes.json'
|
||||
export default {
|
||||
data () {
|
||||
return {
|
||||
items: data
|
||||
}
|
||||
}
|
||||
}
|
||||
</script>
|
||||
|
||||
@ -32,3 +32,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
1. Enter the URL of the RSS feed that you want to read in the *URL* field.
|
||||
2. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="RSS Read" />
|
||||
|
||||
@ -38,3 +38,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
1. Enter the type of files you want to read in the *File Selector* field.
|
||||
2. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Read Binary File" />
|
||||
|
||||
@ -54,3 +54,7 @@ The start node exists by default when you create a new workflow.
|
||||
4. Enter a subject for your message in the *Subject* field.
|
||||
5. Enter your message in the *Text* field.
|
||||
6. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Send Email" />
|
||||
|
||||
@ -59,6 +59,4 @@ You can deactivate this behaviour by clicking on the *Add Option* button and set
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Building an expense tracking app in 10 minutes 📱](https://medium.com/n8n-io/building-an-expense-tracking-app-in-10-minutes-74b0cececc90)
|
||||
- [Effortless video collaboration with Whereby, Mattermost, and n8n 📹](https://medium.com/n8n-io/effortless-video-collaboration-with-whereby-mattermost-and-n8n-8fc397feb9cb)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Set" />
|
||||
|
||||
@ -85,3 +85,7 @@ Refer to this [workflow](https://n8n.io/workflows/995) to try it out.
|
||||
To get the current running index of the node, use the following expression: `{{$node["SplitInBatches"].context["currentRunIndex"];}}`.
|
||||
:::
|
||||
Refer to this [workflow](https://n8n.io/workflows/996) to try it out.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Split In Batches" />
|
||||
|
||||
@ -59,3 +59,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
1. Enter the *Property Name* you used in the previous node in the *Binary Property* field.
|
||||
2. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Spreadsheet File" />
|
||||
|
||||
@ -17,3 +17,7 @@ In case there is no Trigger node in the workflow, the workflow always starts fro
|
||||
### When is it necessary to use the Start node?
|
||||
|
||||
When using the *Execute Workflow* node in workflow A to execute workflow B, the *Start* node will act as the trigger node in workflow B. The second node in workflow B needs to be connected to the Start node for the workflow to execute correctly.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Start" />
|
||||
@ -145,3 +145,7 @@ return [
|
||||
**Note:** Notice that none of the ids made their way to this node since the values of the all the ids were either 0, 1, or 2.
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Switch" />
|
||||
|
||||
@ -221,8 +221,4 @@ When the Webhook gets called, it will send the string response that was set in t
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Webhook Node — The Versatile Toolbox 🧰](https://medium.com/n8n-io/webhook-node-the-versatile-toolbox-21cb17cee862)
|
||||
- [Creating Custom Incident Response Workflows with n8n 🚨](https://medium.com/n8n-io/creating-custom-incident-response-workflows-with-n8n-9baef0bbedb9)
|
||||
- [Cross-posting content automatically with n8n ✍️](https://medium.com/n8n-io/automating-cross-posting-blog-posts-using-n8n-%EF%B8%8F-af2a89601810)
|
||||
- [Effortless video collaboration with Whereby, Mattermost, and n8n 📹](https://medium.com/n8n-io/effortless-video-collaboration-with-whereby-mattermost-and-n8n-8fc397feb9cb)
|
||||
- [Webhooks Fun with n8n and Mattermost 🍸](https://medium.com/n8n-io/webhooks-fun-with-n8n-and-mattermost-4ebf7e2b4d2a)
|
||||
<FurtherReadingBlog node="Webhook" />
|
||||
|
||||
240
docs/nodes/nodes-library/core-nodes/core-nodes.json
Normal file
240
docs/nodes/nodes-library/core-nodes/core-nodes.json
Normal file
@ -0,0 +1,240 @@
|
||||
[
|
||||
{
|
||||
"displayName":"Compression",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.compression"
|
||||
},
|
||||
{
|
||||
"displayName":"Cron",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.cron"
|
||||
},
|
||||
{
|
||||
"displayName":"Crypto",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.crypto"
|
||||
},
|
||||
{
|
||||
"displayName":"Date & Time",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.datetime"
|
||||
},
|
||||
{
|
||||
"displayName":"Edit Image",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.editimage"
|
||||
},
|
||||
{
|
||||
"displayName":"Error Trigger",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.errortrigger"
|
||||
},
|
||||
{
|
||||
"displayName":"Execute Command",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.executecommand"
|
||||
},
|
||||
{
|
||||
"displayName":"Execute Workflow",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.executeworkflow"
|
||||
},
|
||||
{
|
||||
"displayName":"Function",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.function"
|
||||
},
|
||||
{
|
||||
"displayName":"Function Item",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.functionitem"
|
||||
},
|
||||
{
|
||||
"displayName":"GraphQL",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.graphql"
|
||||
},
|
||||
{
|
||||
"displayName":"HTML Extract",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.htmlextract"
|
||||
},
|
||||
{
|
||||
"displayName":"HTTP Request",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.httprequest"
|
||||
},
|
||||
{
|
||||
"displayName":"IF",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.if"
|
||||
},
|
||||
{
|
||||
"displayName":"IMAP Email",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.emailreadimap"
|
||||
},
|
||||
{
|
||||
"displayName":"Interval",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.interval"
|
||||
},
|
||||
{
|
||||
"displayName":"Merge",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.merge"
|
||||
},
|
||||
{
|
||||
"displayName":"Move Binary Data",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.movebinarydata"
|
||||
},
|
||||
{
|
||||
"displayName":"No Operation, do nothing",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.noop"
|
||||
},
|
||||
{
|
||||
"displayName":"Read Binary File",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.readbinaryfile"
|
||||
},
|
||||
{
|
||||
"displayName":"Read Binary Files",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.readbinaryfiles"
|
||||
},
|
||||
{
|
||||
"displayName":"Read PDF",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.readpdf"
|
||||
},
|
||||
{
|
||||
"displayName":"Rename Keys",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.renamekeys"
|
||||
},
|
||||
{
|
||||
"displayName":"RSS Read",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.rssfeedread"
|
||||
},
|
||||
{
|
||||
"displayName":"Send Email",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.emailsend"
|
||||
},
|
||||
{
|
||||
"displayName":"Set",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.set"
|
||||
},
|
||||
{
|
||||
"displayName":"Split In Batches",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.splitinbatches"
|
||||
},
|
||||
{
|
||||
"displayName":"Spreadsheet File",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.spreadsheetfile"
|
||||
},
|
||||
{
|
||||
"displayName":"SSE Trigger",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.ssetrigger/"
|
||||
},
|
||||
{
|
||||
"displayName":"Start",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.start"
|
||||
},
|
||||
{
|
||||
"displayName":"Switch",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.switch"
|
||||
},
|
||||
{
|
||||
"displayName":"Webhook",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.webhook"
|
||||
},
|
||||
{
|
||||
"displayName":"Write Binary File",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.writebinaryfile"
|
||||
},
|
||||
{
|
||||
"displayName":"XML",
|
||||
"iconData":{
|
||||
"fileBuffer":""
|
||||
},
|
||||
"name":"n8n-nodes-base.xml"
|
||||
}
|
||||
]
|
||||
@ -44,7 +44,7 @@ In the screenshot below, you will notice that the Cron node is configured to tri
|
||||
|
||||
This node will make a GET request to the API `https://api.wheretheiss.at/v1/satellites/25544/positions` to fetch the position of the ISS. This information gets passed on to the next node in the workflow.
|
||||
::: v-pre
|
||||
1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field.
|
||||
1. Enter `https://api.wheretheiss.at/v1/satellites/25544/positions` in the ***URL*** field.
|
||||
2. Click on the ***Add Parameter*** button in the ***Query Parameters*** section.
|
||||
3. Enter `timestamps` in the ***Name*** field.
|
||||
4. Click on the gears icon next to the ***Value*** field and click on ***Add Expression***.
|
||||
@ -102,4 +102,4 @@ This example workflow uses the Cron node, which is a Trigger node. You'll need t
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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)
|
||||
<FurtherReadingBlog node="AMQP Sender" />
|
||||
@ -53,3 +53,7 @@ The start node exists by default when you create a new workflow.
|
||||
2. Select 'Bucket' from the *Resource* dropdown list.
|
||||
3. Enter a name for your bucket in the *Name* field.
|
||||
4. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="AWS S3" />
|
||||
|
||||
@ -57,3 +57,7 @@ The start node exists by default when you create a new workflow.
|
||||
4. Enter the email address from which you want to send the email in the *From Email* field.
|
||||
5. Click on the *Add To Email* button and add your recipient email addresses.
|
||||
6. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="AWS SES" />
|
||||
|
||||
@ -143,5 +143,4 @@ Refer to the Airtable [documentation](https://support.airtable.com/hc/en-us/arti
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automating Conference Organization Processes with n8n](https://medium.com/n8n-io/automating-conference-organization-processes-with-n8n-ab8f64a7a520)
|
||||
- [Building an expense tracking app in 10 minutes 📱](https://medium.com/n8n-io/building-an-expense-tracking-app-in-10-minutes-74b0cececc90)
|
||||
<FurtherReadingBlog node="Airtable" />
|
||||
|
||||
@ -47,3 +47,7 @@ The start node exists by default when you create a new workflow.
|
||||
2. Select your workspace from the *Workspace* dropdown list.
|
||||
3. Enter the name of the task in the *Name* field.
|
||||
4. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Asana" />
|
||||
|
||||
@ -46,8 +46,6 @@ The start node exists by default when you create a new workflow.
|
||||
5. Enter the text in the *Text* field.
|
||||
6. Click on *Execute Node* to run the workflow.
|
||||
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Bannerbear" />
|
||||
|
||||
@ -134,3 +134,7 @@ The start node exists by default when you create a new workflow.
|
||||
5. Select your list ID from the *List ID* dropdown list.
|
||||
6. Enter the name of the task in the *Name* field.
|
||||
7. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="ClickUp" />
|
||||
|
||||
@ -5,7 +5,7 @@ description: Learn how to use the Coda node in n8n
|
||||
|
||||
# Coda
|
||||
|
||||
[Coda](https://coda.io/) is a new type of document that blends the flexibility of documents, the power of spreadsheets, and the utility of applications into a single new canvas.
|
||||
[Coda](https://coda.io/) is a new type of document that blends the flexibility of documents, the power of spreadsheets, and the utility of applications into a single new canvas.
|
||||
|
||||
::: tip 🔑 Credentials
|
||||
You can find authentication information for this node [here](../../../credentials/Coda/README.md).
|
||||
@ -63,7 +63,7 @@ The start node exists by default when you create a new workflow.
|
||||
1. Click on the *Add Value* button and select 'String' from the dropdown list.
|
||||
2. Enter `Column 1`in the *Name* field.
|
||||
3. Enter the value for the first column in the *Value* field.
|
||||
4. Repeat the first three steps of all the columns that you have in your Coda table.
|
||||
4. Repeat the first three steps of all the columns that you have in your Coda table.
|
||||
|
||||
**Note:** Here, we've used the default table in Coda, which has three columns namely Column 1, Column 2, and Column 3. Please make sure that the column names in the *Name* field matches the names of the table columns in Coda.
|
||||
|
||||
@ -73,3 +73,7 @@ The start node exists by default when you create a new workflow.
|
||||
2. Select the name of your document from the *Doc* dropdown list.
|
||||
3. Select the name of your table from the *Table* dropdown list.
|
||||
4. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Coda" />
|
||||
|
||||
@ -111,3 +111,7 @@ Adding this node here is optional, as the absence of this node won't make a diff
|
||||
:::
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="CoinGecko" />
|
||||
|
||||
@ -70,4 +70,4 @@ To specify the data type of a column, append the column name with `:type`, where
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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)
|
||||
<FurtherReadingBlog node="CrateDB" />
|
||||
|
||||
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext1_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext1_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 157 KiB |
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext2_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext2_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 140 KiB |
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/ERPNext/ERPNext_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 160 KiB |
92
docs/nodes/nodes-library/nodes/ERPNext/README.md
Normal file
92
docs/nodes/nodes-library/nodes/ERPNext/README.md
Normal file
@ -0,0 +1,92 @@
|
||||
---
|
||||
permalink: /nodes/n8n-nodes-base.erpNext
|
||||
description: Learn how to use the ERPNext node in n8n
|
||||
---
|
||||
|
||||
# ERPNext
|
||||
|
||||
[ERPNext](https://erpnext.com) is an open-source integrated Enterprise Resource Planning software. It is a generic ERP software used by manufacturers, distributors, and services companies.
|
||||
|
||||
::: tip 🔑 Credentials
|
||||
You can find authentication information for this node [here](../../../credentials/ERPNext/README.md).
|
||||
:::
|
||||
|
||||
## Basic Operations
|
||||
|
||||
::: details Document
|
||||
- Create a document
|
||||
- Delete a document
|
||||
- Retrieve a document
|
||||
- Retrieve all documents
|
||||
- Update a document
|
||||
:::
|
||||
|
||||
## Example Usage
|
||||
|
||||
This workflow allows you to create, update, and retrieve a document from ERPNext. You can also find the [workflow](https://n8n.io/workflows/961) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](../../core-nodes/Start/README.md)
|
||||
- [ERPNext]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||

|
||||
|
||||
### 1. Start node
|
||||
|
||||
The Start node exists by default when you create a new workflow.
|
||||
|
||||
### 2. ERPNext node (document: create)
|
||||
|
||||
This node will create a new document in ERPNext.
|
||||
|
||||
1. First of all, you'll have to enter credentials for the ERPNext node. You can find out how to do that [here](../../../credentials/ERPNext/README.md).
|
||||
2. Select 'Item' from the ***DocType*** dropdown list.
|
||||
3. Click on the ***Add Property*** button.
|
||||
4. Select 'Item Name' from the ***Field*** dropdown list.
|
||||
5. Enter `item 1` in the ***Value*** field.
|
||||
6. Click on the ***Add Property*** button.
|
||||
7. Select 'Item Code' from the ***Field*** dropdown list.
|
||||
8. Enter `item-1` in the ***Value*** field.
|
||||
9. Click on the ***Add Property*** button.
|
||||
10. Select 'Item Group' from the ***Field*** dropdown list.
|
||||
11. Enter `Products` in the ***Value*** field.
|
||||
**Note:** Make sure that the item group exists in your ERPNext account.
|
||||
12. Click on ***Execute Node*** to run the node.
|
||||
|
||||
In the screenshot below, you will notice that the node creates a new item with the name `item 1`.
|
||||
|
||||

|
||||
|
||||
### 3. ERPNext1 node (document: addContact)
|
||||
|
||||
This node will add the `Item Tax` property to the item that we created in the previous node.
|
||||
::: v-pre
|
||||
1. Select the credentials that you entered in the previous node.
|
||||
2. Select 'Update' from the ***Operation*** dropdown list.
|
||||
3. Select 'Item' from the ***DocType*** dropdown list.
|
||||
4. Click on the gears icon next to the ***Item Name*** field and click on ***Add Expression***.
|
||||
5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > name. You can also add the following expression: `{{$json["name"]}}`.
|
||||
6. Click on the ***Add Property*** button.
|
||||
7. Select 'Item Tax' from the ***Field*** dropdown list.
|
||||
8. Enter `5` in the ***Value*** field.
|
||||
10. Click on ***Execute Node*** to run the node.
|
||||
:::
|
||||
In the screenshot below, you will notice that the node adds the Item Tax property to the item that we created in the previous node.
|
||||
|
||||

|
||||
|
||||
### 4. ERPNext2 node (document: get)
|
||||
|
||||
This node will get the information about the item that we created earlier.
|
||||
::: v-pre
|
||||
1. Select the credentials that you entered in the previous node.
|
||||
2. Select 'Get' from the ***Operation*** dropdown list.
|
||||
3. Select 'Item' from the ***DocType*** dropdown list.
|
||||
4. Click on the gears icon next to the ***Item Name*** field and click on ***Add Expression***.
|
||||
5. Select the following in the ***Variable Selector*** section: Current Node > Input Data > JSON > name. You can also add the following expression: `{{$json["name"]}}`.
|
||||
6. Click on ***Execute Node*** to run the node.
|
||||
:::
|
||||
|
||||
In the screenshot below, you will notice that the node returns the information of the item.
|
||||
|
||||

|
||||
BIN
docs/nodes/nodes-library/nodes/ERPNext/workflow.png
Normal file
BIN
docs/nodes/nodes-library/nodes/ERPNext/workflow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 129 KiB |
@ -75,3 +75,7 @@ The start node exists by default when you create a new workflow.
|
||||
4. Enter the repository owner in the *Repository Owner* field.
|
||||
5. Enter the repository name in the *Repository Name* field.
|
||||
6. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="GitHub" />
|
||||
|
||||
@ -122,4 +122,4 @@ Refer to [Search operators you can use with Gmail](https://support.google.com/ma
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
<FurtherReadingBlog node="Gmail" />
|
||||
|
||||
@ -49,6 +49,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Google Calendar" />
|
||||
|
||||
@ -75,3 +75,7 @@ To list all the files and folders within a folder, follow the steps mentioned be
|
||||
3. Enter `'FOLDER_ID' in parents` in the ***Query String*** field. Replace `FOLDER_ID` with the folder ID you copied in the previous step.
|
||||
|
||||
There are several additional options available to fine grain the listed results. Refer to [Search for files and folders: Querystring](https://developers.google.com/drive/api/v3/search-files#query_string_examples) for more information.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Google Drive" />
|
||||
|
||||
@ -203,9 +203,10 @@ To insert the data in Google Sheets, you have to first convert the data in a val
|
||||
|
||||
By default, the Lookup operation returns only the first value that it matches. To return all the values that match, click on ***Add Option*** and select 'Return All Matches'. Toggle ***Return All Matches*** to true.
|
||||
|
||||
### How to specify a sheet?
|
||||
|
||||
By default, the Google Sheets node will operate on the default sheet, `Sheet 1`. If you rename the sheet or want to use a different sheet, you have to specify the name of the sheet. You can do that in the ***Range*** field. For example, if you need to use a sheet named `n8n` for the range `A` to `H`, enter `n8n!A:H` in the ***Range*** field.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating triggers for n8n workflows using polling ⏲](https://n8n.io/blog/creating-triggers-for-n8n-workflows-using-polling/)
|
||||
- [Migrating Community Metrics to Orbit using n8n 📈](https://medium.com/n8n-io/migrating-community-metrics-to-orbit-using-n8n-b293372e8daf)
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
<FurtherReadingBlog node="Google Sheets" />
|
||||
|
||||
@ -43,3 +43,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
1. Select the 'All' option from the *Resource* dropdown list.
|
||||
2. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Hacker News" />
|
||||
|
||||
@ -76,3 +76,7 @@ The start node exists by default when you create a new workflow.
|
||||
3. Select the 'Get' option under the *Operation* field.
|
||||
4. Enter the contact ID under the *Contact ID* field.
|
||||
3. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="HubSpot" />
|
||||
|
||||
@ -85,4 +85,4 @@ You can refer to the [official documentation](https://www.atlassian.com/software
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating Custom Incident Response Workflows with n8n 🚨](https://medium.com/n8n-io/creating-custom-incident-response-workflows-with-n8n-9baef0bbedb9)
|
||||
<FurtherReadingBlog node="Jira Software" />
|
||||
|
||||
@ -55,3 +55,7 @@ This node will translate the cocktail instructions that we got from the previous
|
||||
In the screenshot below, you will notice that the node translates the instructions of the cocktail to Italian.
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="LingvaNex" />
|
||||
|
||||
@ -50,3 +50,7 @@ The start node exists by default when you create a new workflow.
|
||||
6. Click on ***Execute Node*** to run the node.
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="LinkedIn" />
|
||||
|
||||
@ -40,3 +40,7 @@ The start node exists by default when you create a new workflow.
|
||||
3. Enter the email address from which you want to send the email in the *From Email* field.
|
||||
4. Enter the recipient email address in the *To Email* field.
|
||||
5. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Mandrill" />
|
||||
|
||||
@ -168,4 +168,4 @@ Adding this node here is optional, as the absence of this node won't make a diff
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
|
||||
<FurtherReadingBlog node="Matrix" />
|
||||
|
||||
@ -120,11 +120,4 @@ To find the Channel ID in Mattermost, follow the steps mentioned below.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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 triggers for n8n workflows using polling ⏲](https://n8n.io/blog/creating-triggers-for-n8n-workflows-using-polling/)
|
||||
- [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/giving-kudos-to-contributors-with-github-slack-and-n8n-b3f5f4a653a6)
|
||||
- [How to host virtual coffee breaks with n8n ☕️](https://n8n.io/blog/how-to-host-virtual-coffee-breaks-with-n8n/)
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
- [Webhooks Fun with n8n and Mattermost 🍸](https://medium.com/n8n-io/webhooks-fun-with-n8n-and-mattermost-4ebf7e2b4d2a)
|
||||
<FurtherReadingBlog node="Mattermost" />
|
||||
|
||||
@ -53,3 +53,7 @@ The start node exists by default when you create a new workflow.
|
||||
1. First of all, you'll have to enter credentials for the Mautic node. You can find out how to do that [here](../../../credentials/Mautic/README.md).
|
||||
2. Select 'Get All' from the *Operation* dropdown list.
|
||||
3. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Mautic" />
|
||||
|
||||
@ -46,3 +46,7 @@ The start node exists by default when you create a new workflow.
|
||||
5. Select the format from the ***Content Format*** dropdown list.
|
||||
6. Enter conent of the post in the ***Content*** field.
|
||||
7. Click on ***Execute Node*** to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Medium" />
|
||||
|
||||
@ -64,5 +64,4 @@ In the screenshot below, you will notice that the node extracts the information
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automatically Adding Expense Receipts to Google Sheets with Telegram, Mindee, Twilio, and n8n 🧾](https://medium.com/n8n-io/automatically-adding-expense-receipts-to-google-sheets-with-telegram-mindee-twilio-and-n8n-c47eb2f8d7a5)
|
||||
- [Building an expense tracking app in 10 minutes 📱](https://medium.com/n8n-io/building-an-expense-tracking-app-in-10-minutes-74b0cececc90)
|
||||
<FurtherReadingBlog node="Mindee" />
|
||||
|
||||
@ -5,7 +5,7 @@ description: Learn how to use the MongoDB node in n8n
|
||||
|
||||
# MongoDB
|
||||
|
||||
[MongoDB](https://www.mongodb.com/) is a cross-platform document-oriented database program developed by MongoDB Inc. It is classified as a NoSQL database program. MongoDB uses JSON-like documents with optional schemas.
|
||||
[MongoDB](https://www.mongodb.com/) is a cross-platform document-oriented database program developed by MongoDB Inc. It is classified as a NoSQL database program. MongoDB uses JSON-like documents with optional schemas.
|
||||
|
||||
::: tip 🔑 Credentials
|
||||
You can find authentication information for this node [here](../../../credentials/MongoDB/README.md).
|
||||
@ -47,3 +47,7 @@ The start node exists by default when you create a new workflow.
|
||||
3. Enter the name of your MongoDB collection in the *Collection* field.
|
||||
4. Enter `my_key` in the *Fields* field.
|
||||
5. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="MongoDB" />
|
||||
|
||||
@ -5,7 +5,7 @@ description: Learn how to use the OpenWeatherMap node in n8n
|
||||
|
||||
# OpenWeatherMap
|
||||
|
||||
[OpenWeatherMap](https://openweathermap.org/) is an online service that provides weather data. It provides current weather data, forecasts, and historical data.
|
||||
[OpenWeatherMap](https://openweathermap.org/) is an online service that provides weather data. It provides current weather data, forecasts, and historical data.
|
||||
|
||||
::: tip 🔑 Credentials
|
||||
You can find authentication information for this node [here](../../../credentials/OpenWeatherMap/README.md).
|
||||
@ -39,4 +39,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating Telegram Bots with n8n, a No-Code Platform](https://medium.com/n8n-io/creating-telegram-bots-with-n8n-a-no-code-platform-fdf1f0928da7)
|
||||
<FurtherReadingBlog node="OpenWeatherMap" />
|
||||
|
||||
@ -126,4 +126,4 @@ In the screenshot below, you will notice that the node creates a post for the me
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Migrating Community Metrics to Orbit using n8n 📈](https://medium.com/n8n-io/migrating-community-metrics-to-orbit-using-n8n-b293372e8daf)
|
||||
<FurtherReadingBlog node="Orbit" />
|
||||
|
||||
@ -93,5 +93,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating Custom Incident Response Workflows with n8n 🚨](https://medium.com/n8n-io/creating-custom-incident-response-workflows-with-n8n-9baef0bbedb9)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="PagerDuty" />
|
||||
|
||||
@ -70,4 +70,4 @@ To specify the data type of a column, append the column name with `:type`, where
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Database Monitoring and Alerting with n8n 📡](https://medium.com/n8n-io/database-monitoring-and-alerting-with-n8n-f5082df7bdb2)
|
||||
<FurtherReadingBlog node="Postgres" />
|
||||
|
||||
@ -69,3 +69,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
### How to specify the data type of a column?
|
||||
To specify the data type of a column, append the column name with `:type`, where `type` is the data type of that column. For example, if you want to specify the type `int` for the column *id* and type `text` for the column *name*, you can use the following snippet in the ***Columns*** field: `id:init,name:text`.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="QuestDB" />
|
||||
|
||||
@ -1,3 +1,39 @@
|
||||
# Nodes
|
||||
|
||||
This section contains information about all the regular nodes in n8n. Each node documentation contains information on the available resources and operations along with an example workflow.
|
||||
|
||||
<NodeCard :items="items" />
|
||||
|
||||
<script>
|
||||
export default {
|
||||
data () {
|
||||
return {
|
||||
items: []
|
||||
}
|
||||
},
|
||||
beforeMount() {
|
||||
fetch('https://api.n8n.io/graphql', {
|
||||
method: 'POST',
|
||||
headers: {
|
||||
'Content-Type': 'application/json',
|
||||
},
|
||||
body: JSON.stringify({
|
||||
query: `
|
||||
query GetRegularNodes{
|
||||
nodes(where: {categories:{name_ncontains: "Core Nodes"}, displayName_ncontains:"Trigger"}, sort:"displayName"){
|
||||
name
|
||||
displayName
|
||||
iconData
|
||||
}
|
||||
}
|
||||
`
|
||||
})
|
||||
})
|
||||
.then(response => response.json())
|
||||
.then(res => {
|
||||
this.$data.items = res.data.nodes
|
||||
})
|
||||
.catch(error => console.log(error))
|
||||
}
|
||||
}
|
||||
</script>
|
||||
|
||||
@ -40,3 +40,7 @@ The start node exists by default when you create a new workflow.
|
||||
2. Select the 'Get' option from the *Operation* dropdown list.
|
||||
3. Enter the key for which you want to retrieve the value in the *Key* field.
|
||||
4. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Redis" />
|
||||
|
||||
@ -41,4 +41,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automate Designs with Bannerbear and n8n](https://medium.com/n8n-io/automate-designs-with-bannerbear-and-n8n-2b64c94b54db)
|
||||
<FurtherReadingBlog node="RocketChat" />
|
||||
|
||||
@ -190,4 +190,4 @@ You can refer to the official documentation on [Scopes and permissions](https://
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Giving kudos to contributors with GitHub, Slack, and n8n 👏](https://medium.com/n8n-io/giving-kudos-to-contributors-with-github-slack-and-n8n-b3f5f4a653a6)
|
||||
<FurtherReadingBlog node="Slack" />
|
||||
|
||||
@ -91,3 +91,7 @@ This node returns the information of the activity that we created using the Stra
|
||||
In the screenshot below, you will notice that the node returns the information of the activity that we specified in this node.
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Strava" />
|
||||
|
||||
@ -130,5 +130,4 @@ There are two ways to get the Chat ID in Telegram.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automatically Adding Expense Receipts to Google Sheets with Telegram, Mindee, Twilio, and n8n 🧾](https://medium.com/n8n-io/automatically-adding-expense-receipts-to-google-sheets-with-telegram-mindee-twilio-and-n8n-c47eb2f8d7a5)
|
||||
- [Creating Telegram Bots with n8n, a No-Code Platform](https://medium.com/n8n-io/creating-telegram-bots-with-n8n-a-no-code-platform-fdf1f0928da7)
|
||||
<FurtherReadingBlog node="Telegram" />
|
||||
|
||||
@ -38,3 +38,7 @@ The start node exists by default when you create a new workflow.
|
||||
2. Select your project from the *Project* dropdown list.
|
||||
3. Enter the content for the task in the *Content* field.
|
||||
4. Click on *Execute Node* to run the workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Todoist" />
|
||||
|
||||
@ -101,4 +101,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automating Conference Organization Processes with n8n](https://medium.com/n8n-io/automating-conference-organization-processes-with-n8n-ab8f64a7a520)
|
||||
<FurtherReadingBlog node="Trello" />
|
||||
|
||||
@ -44,6 +44,4 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Creating Error Workflows in n8n 🌪](https://medium.com/n8n-io/creating-error-workflows-in-n8n-6e03c9ecbc0f)
|
||||
- [Database Monitoring and Alerting with n8n 📡](https://medium.com/n8n-io/database-monitoring-and-alerting-with-n8n-f5082df7bdb2)
|
||||
- [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)
|
||||
<FurtherReadingBlog node="Twilio" />
|
||||
|
||||
@ -44,7 +44,7 @@ In the screenshot below, you will notice that the Cron node is configured to tri
|
||||
|
||||
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).
|
||||
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.
|
||||
|
||||
@ -68,3 +68,7 @@ This node will send an SMS with the weather update, which was sent by the previo
|
||||
In the screenshot below, you will notice that the node sends an SMS to the phone number that we specified with the weather update, which was sent by the previous node.
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Vonage" />
|
||||
|
||||
@ -65,7 +65,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
### 2. Read Binary File node
|
||||
|
||||
1. Enter the path to the video file you want to upload in the ***File Path*** field.
|
||||
1. Enter the path to the video file you want to upload in the ***File Path*** field.
|
||||
2. Click on ***Execute Node*** to run the node.
|
||||
|
||||

|
||||
@ -77,7 +77,7 @@ The start node exists by default when you create a new workflow.
|
||||
1. First of all, you'll have to enter credentials for the YouTube node. You can find out how to do that [here](../../../credentials/Google/README.md).
|
||||
2. Select 'Video' from the ***Resource*** dropdown list.
|
||||
3. Select 'Upload' from the ***Operation*** dropdown list.
|
||||
4. Enter the title of the video in the ***Title*** field.
|
||||
4. Enter the title of the video in the ***Title*** field.
|
||||
5. Select the region code from ***Region Code*** dropdown list.
|
||||
6. Select the video category from the ***Category ID*** dropdown list.
|
||||
7. Click on ***Execute Node*** to run the node.
|
||||
@ -111,3 +111,7 @@ The start node exists by default when you create a new workflow.
|
||||
:::
|
||||
|
||||

|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="YouTube" />
|
||||
|
||||
@ -34,4 +34,4 @@ You'll need to save the workflow and then click on the Activate toggle on the to
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [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)
|
||||
<FurtherReadingBlog node="AMQP Trigger" />
|
||||
|
||||
@ -31,3 +31,7 @@ The final workflow should look like the following image.
|
||||
::: 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 HubSpot Trigger node.
|
||||
:::
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="HubSpot Trigger" />
|
||||
|
||||
@ -1,3 +1,40 @@
|
||||
# Trigger Nodes
|
||||
|
||||
This section contains information about all the trigger nodes in n8n. Each node documentation contains information on the available resources and operations along with an example workflow.
|
||||
|
||||
|
||||
<NodeCard :items="items" />
|
||||
|
||||
<script>
|
||||
export default {
|
||||
data () {
|
||||
return {
|
||||
items: []
|
||||
}
|
||||
},
|
||||
beforeMount() {
|
||||
fetch('https://api.n8n.io/graphql', {
|
||||
method: 'POST',
|
||||
headers: {
|
||||
'Content-Type': 'application/json',
|
||||
},
|
||||
body: JSON.stringify({
|
||||
query: `
|
||||
query GetTriggerNodes{
|
||||
nodes(where: {displayName_contains:"Trigger", categories:{name_ncontains: "Core Nodes"}}, sort:"displayName"){
|
||||
name
|
||||
displayName
|
||||
iconData
|
||||
}
|
||||
}
|
||||
`
|
||||
})
|
||||
})
|
||||
.then(response => response.json())
|
||||
.then(res => {
|
||||
this.$data.items = res.data.nodes
|
||||
})
|
||||
.catch(error => console.log(error))
|
||||
}
|
||||
}
|
||||
</script>
|
||||
|
||||
@ -31,3 +31,7 @@ The final workflow should look like the following image.
|
||||
::: 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 Stripe Trigger node.
|
||||
:::
|
||||
|
||||
## Further Reading
|
||||
|
||||
<FurtherReadingBlog node="Stripe Trigger" />
|
||||
|
||||
@ -86,5 +86,4 @@ You'll need to save the workflow and then click on the Activate toggle on the to
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automatically Adding Expense Receipts to Google Sheets with Telegram, Mindee, Twilio, and n8n 🧾](https://medium.com/n8n-io/automatically-adding-expense-receipts-to-google-sheets-with-telegram-mindee-twilio-and-n8n-c47eb2f8d7a5)
|
||||
- [Creating Telegram Bots with n8n, a No-Code Platform](https://medium.com/n8n-io/creating-telegram-bots-with-n8n-a-no-code-platform-fdf1f0928da7)
|
||||
<FurtherReadingBlog node="Telegram Trigger" />
|
||||
|
||||
@ -102,6 +102,4 @@ You'll need to save the workflow and then click on the Activate toggle on the to
|
||||
|
||||
## Further Reading
|
||||
|
||||
- [Automating Conference Organization Processes with n8n](https://medium.com/n8n-io/automating-conference-organization-processes-with-n8n-ab8f64a7a520)
|
||||
- [Building an expense tracking app in 10 minutes 📱](https://medium.com/n8n-io/building-an-expense-tracking-app-in-10-minutes-74b0cececc90)
|
||||
- [Supercharging your conference registration process with n8n 🎫](https://medium.com/n8n-io/supercharging-your-conference-registration-process-with-n8n-2831cdff37f9)
|
||||
<FurtherReadingBlog node="Typeform Trigger" />
|
||||
|
||||
@ -2,6 +2,25 @@
|
||||
|
||||
🛠 = 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.115.0
|
||||
For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n@0.114.0...n8n@0.115.0) for this version.<br />
|
||||
**Release date:** 2021-04-10
|
||||
|
||||
- New nodes
|
||||
- Google Slides
|
||||
- Enhanced nodes
|
||||
- GitHub: Added Release resource
|
||||
- TheHive: Added support to fetch observable data types
|
||||
- RabbitMQ: Added header parameters
|
||||
- Bug fixes
|
||||
- Jira: Fixed an issue with loading issue types with classic project type
|
||||
- RabbitMQ Trigger: Fixed an issue with the node reusing the same item
|
||||
- SendGrid: Fixed an issue with the dynamic field generation
|
||||
- Fixed an issue with expressions not being displayed in read-only mode
|
||||
- Fixed an issue that didn't allow editing JavaScript code in read-only mode
|
||||
- Added support for configuring the maximum payload size
|
||||
- Added support to dynamically add menu items
|
||||
|
||||
## 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
|
||||
|
||||
@ -254,8 +254,7 @@ export WEBHOOK_TUNNEL_URL=https://n8n.example.com/
|
||||
|
||||
## Prometheus
|
||||
|
||||
In order to collect and expose metrics, n8n uses the
|
||||
[prom-client](https://www.npmjs.com/package/prom-client) library.
|
||||
In order to collect and expose metrics, n8n uses the [prom-client](https://www.npmjs.com/package/prom-client) library.
|
||||
|
||||
The `/metrics` endpoint is disabled by default, but it is possible to enable it using the `N8N_METRICS` environment variable.
|
||||
|
||||
@ -280,6 +279,15 @@ It is also possible to set default values for credentials. These credentials get
|
||||
export CREDENTIALS_OVERWRITE_DATA={CREDENTIAL_NAME:{ PARAMATER: Value }}
|
||||
```
|
||||
|
||||
## Maximum payload limit
|
||||
|
||||
The default maximum incoming payload limit is **16MB**. To increase the maximum payload limit, the following format.
|
||||
|
||||
```bash
|
||||
export N8N_PAYLOAD_SIZE_MAX=VALUE
|
||||
```
|
||||
|
||||
The value should be in megabytes. For example, if you want to set the limit to 32MB, use `N8N_PAYLOAD_SIZE_MAX=32`.
|
||||
|
||||
## Configuration via file
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user