mirror of
https://github.com/n8n-io/n8n-docs.git
synced 2025-11-20 17:48:34 +00:00
complete lowercasing links to integrations
This commit is contained in:
Deborah Barnard
parent
dd86715922
commit
e953c25c9d
@ -1 +1 @@
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.errorTrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(0, 0, 255);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="bug" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" class="svg-inline--fa fa-bug fa-w-16"><path fill="currentColor" d="M511.988 288.9c-.478 17.43-15.217 31.1-32.653 31.1H424v16c0 21.864-4.882 42.584-13.6 61.145l60.228 60.228c12.496 12.497 12.496 32.758 0 45.255-12.498 12.497-32.759 12.496-45.256 0l-54.736-54.736C345.886 467.965 314.351 480 280 480V236c0-6.627-5.373-12-12-12h-24c-6.627 0-12 5.373-12 12v244c-34.351 0-65.886-12.035-90.636-32.108l-54.736 54.736c-12.498 12.497-32.759 12.496-45.256 0-12.496-12.497-12.496-32.758 0-45.255l60.228-60.228C92.882 378.584 88 357.864 88 336v-16H32.666C15.23 320 .491 306.33.013 288.9-.484 270.816 14.028 256 32 256h56v-58.745l-46.628-46.628c-12.496-12.497-12.496-32.758 0-45.255 12.498-12.497 32.758-12.497 45.256 0L141.255 160h229.489l54.627-54.627c12.498-12.497 32.758-12.497 45.256 0 12.496 12.497 12.496 32.758 0 45.255L424 197.255V256h56c17.972 0 32.484 14.816 31.988 32.9zM257 0c-61.856 0-112 50.144-112 112h224C369 50.144 318.856 0 257 0z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Error Trigger</p></div></a></div>
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.errortrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(0, 0, 255);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="bug" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512" class="svg-inline--fa fa-bug fa-w-16"><path fill="currentColor" d="M511.988 288.9c-.478 17.43-15.217 31.1-32.653 31.1H424v16c0 21.864-4.882 42.584-13.6 61.145l60.228 60.228c12.496 12.497 12.496 32.758 0 45.255-12.498 12.497-32.759 12.496-45.256 0l-54.736-54.736C345.886 467.965 314.351 480 280 480V236c0-6.627-5.373-12-12-12h-24c-6.627 0-12 5.373-12 12v244c-34.351 0-65.886-12.035-90.636-32.108l-54.736 54.736c-12.498 12.497-32.759 12.496-45.256 0-12.496-12.497-12.496-32.758 0-45.255l60.228-60.228C92.882 378.584 88 357.864 88 336v-16H32.666C15.23 320 .491 306.33.013 288.9-.484 270.816 14.028 256 32 256h56v-58.745l-46.628-46.628c-12.496-12.497-12.496-32.758 0-45.255 12.498-12.497 32.758-12.497 45.256 0L141.255 160h229.489l54.627-54.627c12.498-12.497 32.758-12.497 45.256 0 12.496 12.497 12.496 32.758 0 45.255L424 197.255V256h56c17.972 0 32.484 14.816 31.988 32.9zM257 0c-61.856 0-112 50.144-112 112h224C369 50.144 318.856 0 257 0z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Error Trigger</p></div></a></div>
|
||||
|
||||
@ -1 +1 @@
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.localFileTrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(64, 64, 64);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="folder-open" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512" class="svg-inline--fa fa-folder-open fa-w-18"><path fill="currentColor" d="M572.694 292.093L500.27 416.248A63.997 63.997 0 0 1 444.989 448H45.025c-18.523 0-30.064-20.093-20.731-36.093l72.424-124.155A64 64 0 0 1 152 256h399.964c18.523 0 30.064 20.093 20.73 36.093zM152 224h328v-48c0-26.51-21.49-48-48-48H272l-64-64H48C21.49 64 0 85.49 0 112v278.046l69.077-118.418C86.214 242.25 117.989 224 152 224z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Local File Trigger</p></div></a></div>
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.localfiletrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(64, 64, 64);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="folder-open" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512" class="svg-inline--fa fa-folder-open fa-w-18"><path fill="currentColor" d="M572.694 292.093L500.27 416.248A63.997 63.997 0 0 1 444.989 448H45.025c-18.523 0-30.064-20.093-20.731-36.093l72.424-124.155A64 64 0 0 1 152 256h399.964c18.523 0 30.064 20.093 20.73 36.093zM152 224h328v-48c0-26.51-21.49-48-48-48H272l-64-64H48C21.49 64 0 85.49 0 112v278.046l69.077-118.418C86.214 242.25 117.989 224 152 224z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Local File Trigger</p></div></a></div>
|
||||
|
||||
@ -1 +1 @@
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.n8nTrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%;"><img src="data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjUgNSA1NSA1NSI+PHBhdGggZD0iTTUwLjI4IDE3LjI2Yy0yLjM5IDAtNC40IDEuNjQtNC45NyAzLjg2aC03LjE1Yy0yLjggMC01LjA4IDIuMjgtNS4wOCA1LjA4IDAgMS40LTEuMTQgMi41NC0yLjU0IDIuNTRoLTEuMDJhNS4xMzggNS4xMzggMCAwMC00Ljk3LTMuODZjLTIuMzkgMC00LjQgMS42NC00Ljk3IDMuODZIMTUuNWE1LjEzOCA1LjEzOCAwIDAwLTQuOTctMy44NmMtMi44MyAwLTUuMTMgMi4zLTUuMTMgNS4xM3MyLjMgNS4xMyA1LjEzIDUuMTNjMi4zOSAwIDQuNC0xLjY0IDQuOTctMy44Nmg0LjA4YTUuMTM4IDUuMTM4IDAgMDA0Ljk3IDMuODYgNS4xMyA1LjEzIDAgMDA0Ljk1LTMuODFoMS4wM2MxLjQgMCAyLjU0IDEuMTQgMi41NCAyLjU0IDAgMi44IDIuMjggNS4wOSA1LjA4IDUuMDloMS42NmE1LjEzOCA1LjEzOCAwIDAwNC45NyAzLjg2YzIuODMgMCA1LjEzLTIuMyA1LjEzLTUuMTNzLTIuMy01LjEzLTUuMTMtNS4xM2MtMi4zOSAwLTQuNCAxLjY0LTQuOTcgMy44NmgtMS42NmMtMS40IDAtMi41NC0xLjE0LTIuNTQtMi41NCAwLTEuNTMtLjY4LTIuOS0xLjc2LTMuODRhNS4wOTIgNS4wOTIgMCAwMDEuNzYtMy44NGMwLTEuNCAxLjE0LTIuNTQgMi41NC0yLjU0aDcuMTVhNS4xMzggNS4xMzggMCAwMDQuOTcgMy44NmMyLjgzIDAgNS4xMy0yLjMgNS4xMy01LjEzcy0yLjI5LTUuMTMtNS4xMi01LjEzek0xMC41NCAzMi42MWEyLjU5IDIuNTkgMCAxMS4wMDEtNS4xODEgMi41OSAyLjU5IDAgMDEtLjAwMSA1LjE4MXptMTQuMDIgMGEyLjU5IDIuNTkgMCAxMTIuNTktMi41OWMwIDEuNDMtMS4xNyAyLjU5LTIuNTkgMi41OXptMjAuMjQgMi41YTIuNTkgMi41OSAwIDExLS4wMDEgNS4xODEgMi41OSAyLjU5IDAgMDEuMDAxLTUuMTgxem01LjQ4LTEwLjEzYTIuNTkgMi41OSAwIDExLjAwMS01LjE4MSAyLjU5IDIuNTkgMCAwMS0uMDAxIDUuMTgxeiIgZmlsbD0iI2ZmNmQ1YSIvPjwvc3ZnPg==" class="medium-zoom-image" style="width: 100%; height: 100%;"></div></div> <p data-v-bd58f1ae="">n8n Trigger</p></div></a></div>
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.n8ntrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%;"><img src="data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjUgNSA1NSA1NSI+PHBhdGggZD0iTTUwLjI4IDE3LjI2Yy0yLjM5IDAtNC40IDEuNjQtNC45NyAzLjg2aC03LjE1Yy0yLjggMC01LjA4IDIuMjgtNS4wOCA1LjA4IDAgMS40LTEuMTQgMi41NC0yLjU0IDIuNTRoLTEuMDJhNS4xMzggNS4xMzggMCAwMC00Ljk3LTMuODZjLTIuMzkgMC00LjQgMS42NC00Ljk3IDMuODZIMTUuNWE1LjEzOCA1LjEzOCAwIDAwLTQuOTctMy44NmMtMi44MyAwLTUuMTMgMi4zLTUuMTMgNS4xM3MyLjMgNS4xMyA1LjEzIDUuMTNjMi4zOSAwIDQuNC0xLjY0IDQuOTctMy44Nmg0LjA4YTUuMTM4IDUuMTM4IDAgMDA0Ljk3IDMuODYgNS4xMyA1LjEzIDAgMDA0Ljk1LTMuODFoMS4wM2MxLjQgMCAyLjU0IDEuMTQgMi41NCAyLjU0IDAgMi44IDIuMjggNS4wOSA1LjA4IDUuMDloMS42NmE1LjEzOCA1LjEzOCAwIDAwNC45NyAzLjg2YzIuODMgMCA1LjEzLTIuMyA1LjEzLTUuMTNzLTIuMy01LjEzLTUuMTMtNS4xM2MtMi4zOSAwLTQuNCAxLjY0LTQuOTcgMy44NmgtMS42NmMtMS40IDAtMi41NC0xLjE0LTIuNTQtMi41NCAwLTEuNTMtLjY4LTIuOS0xLjc2LTMuODRhNS4wOTIgNS4wOTIgMCAwMDEuNzYtMy44NGMwLTEuNCAxLjE0LTIuNTQgMi41NC0yLjU0aDcuMTVhNS4xMzggNS4xMzggMCAwMDQuOTcgMy44NmMyLjgzIDAgNS4xMy0yLjMgNS4xMy01LjEzcy0yLjI5LTUuMTMtNS4xMi01LjEzek0xMC41NCAzMi42MWEyLjU5IDIuNTkgMCAxMS4wMDEtNS4xODEgMi41OSAyLjU5IDAgMDEtLjAwMSA1LjE4MXptMTQuMDIgMGEyLjU5IDIuNTkgMCAxMTIuNTktMi41OWMwIDEuNDMtMS4xNyAyLjU5LTIuNTkgMi41OXptMjAuMjQgMi41YTIuNTkgMi41OSAwIDExLS4wMDEgNS4xODEgMi41OSAyLjU5IDAgMDEuMDAxLTUuMTgxem01LjQ4LTEwLjEzYTIuNTkgMi41OSAwIDExLjAwMS01LjE4MSAyLjU5IDIuNTkgMCAwMS0uMDAxIDUuMTgxeiIgZmlsbD0iI2ZmNmQ1YSIvPjwvc3ZnPg==" class="medium-zoom-image" style="width: 100%; height: 100%;"></div></div> <p data-v-bd58f1ae="">n8n Trigger</p></div></a></div>
|
||||
|
||||
@ -1 +1 @@
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.sseTrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(34, 85, 119);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="cloud-download-alt" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="svg-inline--fa fa-cloud-download-alt fa-w-20"><path fill="currentColor" d="M537.6 226.6c4.1-10.7 6.4-22.4 6.4-34.6 0-53-43-96-96-96-19.7 0-38.1 6-53.3 16.2C367 64.2 315.3 32 256 32c-88.4 0-160 71.6-160 160 0 2.7.1 5.4.2 8.1C40.2 219.8 0 273.2 0 336c0 79.5 64.5 144 144 144h368c70.7 0 128-57.3 128-128 0-61.9-44-113.6-102.4-125.4zm-132.9 88.7L299.3 420.7c-6.2 6.2-16.4 6.2-22.6 0L171.3 315.3c-10.1-10.1-2.9-27.3 11.3-27.3H248V176c0-8.8 7.2-16 16-16h48c8.8 0 16 7.2 16 16v112h65.4c14.2 0 21.4 17.2 11.3 27.3z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">SSE Trigger</p></div></a></div>
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.ssetrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(34, 85, 119);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="cloud-download-alt" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="svg-inline--fa fa-cloud-download-alt fa-w-20"><path fill="currentColor" d="M537.6 226.6c4.1-10.7 6.4-22.4 6.4-34.6 0-53-43-96-96-96-19.7 0-38.1 6-53.3 16.2C367 64.2 315.3 32 256 32c-88.4 0-160 71.6-160 160 0 2.7.1 5.4.2 8.1C40.2 219.8 0 273.2 0 336c0 79.5 64.5 144 144 144h368c70.7 0 128-57.3 128-128 0-61.9-44-113.6-102.4-125.4zm-132.9 88.7L299.3 420.7c-6.2 6.2-16.4 6.2-22.6 0L171.3 315.3c-10.1-10.1-2.9-27.3 11.3-27.3H248V176c0-8.8 7.2-16 16-16h48c8.8 0 16 7.2 16 16v112h65.4c14.2 0 21.4 17.2 11.3 27.3z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">SSE Trigger</p></div></a></div>
|
||||
|
||||
@ -1 +1 @@
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.workflowTrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(255, 109, 90);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="network-wired" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="svg-inline--fa fa-network-wired fa-w-20"><path fill="currentColor" d="M640 264v-16c0-8.84-7.16-16-16-16H344v-40h72c17.67 0 32-14.33 32-32V32c0-17.67-14.33-32-32-32H224c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h72v40H16c-8.84 0-16 7.16-16 16v16c0 8.84 7.16 16 16 16h104v40H64c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h304v40h-56c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h104c8.84 0 16-7.16 16-16zM256 128V64h128v64H256zm-64 320H96v-64h96v64zm352 0h-96v-64h96v64z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Workflow Trigger</p></div></a></div>
|
||||
<div data-v-bd58f1ae=""><a data-v-bd58f1ae="" href="/nodes/n8n-nodes-base.workflowtrigger" class="card-wrapper"><div data-v-bd58f1ae="" class="card"><div data-v-bd58f1ae="" class="image-container"><div data-v-bd58f1ae="" style="width: 100%; height: 100%; color: rgb(255, 109, 90);"><svg aria-hidden="true" focusable="false" data-prefix="fas" data-icon="network-wired" role="img" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 640 512" class="svg-inline--fa fa-network-wired fa-w-20"><path fill="currentColor" d="M640 264v-16c0-8.84-7.16-16-16-16H344v-40h72c17.67 0 32-14.33 32-32V32c0-17.67-14.33-32-32-32H224c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h72v40H16c-8.84 0-16 7.16-16 16v16c0 8.84 7.16 16 16 16h104v40H64c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h304v40h-56c-17.67 0-32 14.33-32 32v128c0 17.67 14.33 32 32 32h160c17.67 0 32-14.33 32-32V352c0-17.67-14.33-32-32-32h-56v-40h104c8.84 0 16-7.16 16-16zM256 128V64h128v64H256zm-64 320H96v-64h96v64zm352 0h-96v-64h96v64z" class=""></path></svg></div></div> <p data-v-bd58f1ae="">Workflow Trigger</p></div></a></div>
|
||||
|
||||
@ -9,7 +9,7 @@ Using the function node, you can:
|
||||
* Implement custom functionality
|
||||
|
||||
!!! note "Function node and function item node"
|
||||
Note that the Function node is different from the [Function Item](/integrations/builtin/core-nodes/n8n-nodes-base.functionItem/) node. Refer to [Data | Code](/data/code/) to learn about the difference between the two.
|
||||
Note that the Function node is different from the [Function Item](/integrations/builtin/core-nodes/n8n-nodes-base.functionitem/) node. Refer to [Data | Code](/data/code/) to learn about the difference between the two.
|
||||
|
||||
|
||||
The Function node supports:
|
||||
|
||||
@ -13,7 +13,7 @@ The first thing you need to do is get data from ABCorp's old data warehouse.
|
||||
|
||||
In the previous chapter, you used a regular node for a specific app (YCombinator). However, not all apps or services have dedicated nodes – like the legacy data warehouse from Nathan's company.
|
||||
|
||||
Though it's not possible to directly export the data, the data warehouse has a couple of API endpoints. That's all we need to access the data via the [***HTTP Request node***](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/){:target="_blank" .external} in n8n.
|
||||
Though it's not possible to directly export the data, the data warehouse has a couple of API endpoints. That's all we need to access the data via the [***HTTP Request node***](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/){:target="_blank" .external} in n8n.
|
||||
|
||||
!!! note "No node for that service?"
|
||||
The *HTTP Request node* is one of the most versatile nodes, allowing you to make HTTP requests which can be used to query data from apps and services. You can use it to access data from apps or services that don't have a dedicated node in n8n.
|
||||
|
||||
@ -28,7 +28,7 @@ Now that the table is prepared let's return to the workflow in the Editor UI.
|
||||
Add an ***Airtable node*** connected to the HTTP Request node.
|
||||
|
||||
!!! note "Spreadsheet nodes"
|
||||
You can replace the *Airtable* node with another spreadsheet app/service. For example, n8n also has nodes for [*Google Sheets*](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/){:target="_blank" .external} and [*Spreadsheet File*](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/){:target="_blank" .external}.
|
||||
You can replace the *Airtable* node with another spreadsheet app/service. For example, n8n also has nodes for [*Google Sheets*](/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/){:target="_blank" .external} and [*Spreadsheet File*](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/){:target="_blank" .external}.
|
||||
|
||||
|
||||
In the *Airtable node* window, configure the following parameters:
|
||||
|
||||
@ -11,7 +11,7 @@ You're most likely familiar with HTML and XML.
|
||||
|
||||
HTML is a markup language used to describe the structure and semantics of a web page. XML looks similar to HTML, but the tag names are different, as they describe the kind of data they hold.
|
||||
|
||||
If you need to process HTML or XML data in your n8n workflows, use the [HTML Extract node](/integrations/builtin/core-nodes/n8n-nodes-base.htmlExtract/){:target="_blank" .external} or [XML node](/integrations/builtin/core-nodes/n8n-nodes-base.xml/){:target="_blank" .external}.
|
||||
If you need to process HTML or XML data in your n8n workflows, use the [HTML Extract node](/integrations/builtin/core-nodes/n8n-nodes-base.htmlextract/){:target="_blank" .external} or [XML node](/integrations/builtin/core-nodes/n8n-nodes-base.xml/){:target="_blank" .external}.
|
||||
|
||||
The HTML Extract node allows you to extract HTML content of a webpage, by referencing CSS selectors. This is useful if you want to collect structured information from a website (web-scraping).
|
||||
|
||||
@ -80,7 +80,7 @@ Date and time data types include `DATE`, `TIME`, `DATETIME`, `TIMESTAMP`, and `Y
|
||||
- `TIMESTAMP`: 1616108400 (Unix timestamp), 1616108400000 (Unix ms timestamp)
|
||||
- `YEAR`: 2022, 22
|
||||
|
||||
If you need to convert date and time data to different formats, and calculate dates, use the [Date & Time node](/integrations/builtin/core-nodes/n8n-nodes-base.dateTime/){:target="_blank" .external}.
|
||||
If you need to convert date and time data to different formats, and calculate dates, use the [Date & Time node](/integrations/builtin/core-nodes/n8n-nodes-base.datetime/){:target="_blank" .external}.
|
||||
|
||||
You can also schedule workflows to run at a specific time, interval, or duration, using the two trigger nodes:
|
||||
|
||||
@ -264,11 +264,11 @@ So far, you have mainly worked with text data. But what if you want to process d
|
||||
|
||||
In n8n, you can process binary data with the following nodes:
|
||||
|
||||
- [Move Binary Data node](/integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData/){:target="_blank" .external} to move data between binary and JSON properties.
|
||||
- [Read Binary File node](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/){:target="_blank" .external} to read a file from the host machine that runs n8n.
|
||||
- [Read Binary Files](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles/){:target="_blank" .external} to read multiple files from the host machine that runs n8n.
|
||||
- [Write Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/){:target="_blank" .external} to write a file to the host machine that runs n8n.
|
||||
- [Spreadsheet File node](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/){:target="_blank" .external} to read from or write to spreadsheet files of different formats (for example, CSV, XLSX).
|
||||
- [Move Binary Data node](/integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/){:target="_blank" .external} to move data between binary and JSON properties.
|
||||
- [Read Binary File node](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/){:target="_blank" .external} to read a file from the host machine that runs n8n.
|
||||
- [Read Binary Files](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/){:target="_blank" .external} to read multiple files from the host machine that runs n8n.
|
||||
- [Write Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/){:target="_blank" .external} to write a file to the host machine that runs n8n.
|
||||
- [Spreadsheet File node](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/){:target="_blank" .external} to read from or write to spreadsheet files of different formats (for example, CSV, XLSX).
|
||||
|
||||
To read or write a binary file, you need to write the path (location) of the file in the node's `File Name` parameter.
|
||||
|
||||
|
||||
@ -75,7 +75,7 @@ To [create a loop in an n8n workflow](/flow-logic/looping/#using-loops-in-n8n){:
|
||||
|
||||
## Splitting data in batches
|
||||
|
||||
If you need to process large incoming data, execute the Function node multiple times, or avoid API rate limits, it's best to split the data into batches (groups) and process these batches. You can do this with the [Split in Batches node](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/){:target="_blank" .external}. This node splits input data into a specified batch size and, with each iteration, returns a predefined amount of data.
|
||||
If you need to process large incoming data, execute the Function node multiple times, or avoid API rate limits, it's best to split the data into batches (groups) and process these batches. You can do this with the [Split in Batches node](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/){:target="_blank" .external}. This node splits input data into a specified batch size and, with each iteration, returns a predefined amount of data.
|
||||
|
||||
!!! warning "Execution of Split in Batches node"
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@ This will open the workflow in read-only mode, where you can see the execution o
|
||||
|
||||
## Catching erroring workflows
|
||||
|
||||
To catch failed workflows, create a separate [Error Workflow](/workflows/workflows/#failed-workflows){:target="_blank" .external} with the [Error Trigger node](/integrations/builtin/core-nodes/n8n-nodes-base.errorTrigger/){:target="_blank" .external}, which gets executed if the main execution fails.
|
||||
To catch failed workflows, create a separate [Error Workflow](/workflows/workflows/#failed-workflows){:target="_blank" .external} with the [Error Trigger node](/integrations/builtin/core-nodes/n8n-nodes-base.errortrigger/){:target="_blank" .external}, which gets executed if the main execution fails.
|
||||
|
||||
Then, you can take further actions by connecting other nodes, for example sending notifications via email or Slack about the failed workflow and its errors. To receive error messages for a failed workflow, you need to select the option `Error Workflow` in the [Workflow Settings](/courses/level-one/chapter-5/chapter-5.8/){:target="_blank" .external} of the respective workflow.
|
||||
|
||||
@ -101,7 +101,7 @@ In the previous chapters, you've built several small workflows. Now, pick one of
|
||||
|
||||
## Throwing exceptions in workflows
|
||||
|
||||
Another way of troubleshooting workflows is to include a [Stop and Error node](/integrations/builtin/core-nodes/n8n-nodes-base.stopAndError/){:target="_blank" .external} in your workflow. This node throws an error, which can be set to one of two error types: an error message or an error object. The error message returns a custom message about the error, while the error object returns the type of error.
|
||||
Another way of troubleshooting workflows is to include a [Stop and Error node](/integrations/builtin/core-nodes/n8n-nodes-base.stopanderror/){:target="_blank" .external} in your workflow. This node throws an error, which can be set to one of two error types: an error message or an error object. The error message returns a custom message about the error, while the error object returns the type of error.
|
||||
|
||||
The Stop and Error node can only be added as the last node in a workflow.
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ To accomplish this task, you first need to make a copy of this table in your Air
|
||||
Next, you have to build a small workflow that merges data from Airtable and a REST API.
|
||||
|
||||
1. Use the [Airtable node](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/){:target="_blank" .external} to list the data in the Airtable table named `customers`.
|
||||
2. use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/){:target="_blank" .external} to get data from the REST Countries API: `https://restcountries.com/v3.1/all`. This will return data about world countries. Note that the incoming data needs to be split into items.
|
||||
2. use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/){:target="_blank" .external} to get data from the REST Countries API: `https://restcountries.com/v3.1/all`. This will return data about world countries. Note that the incoming data needs to be split into items.
|
||||
3. Use the [Merge node](/integrations/builtin/core-nodes/n8n-nodes-base.merge/){:target="_blank" .external} to merge data from Airtable and the Countries API by country name (the common key), represented as `customerCountry` in Airtable and `name.common` in the Countries API, respectively.
|
||||
4. Use the Airtable node to update the fields `region` and `subregion` in Airtable with the data from the Countries API.
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ The first part of the workflow consists of five nodes:
|
||||
|
||||
<figure><img src="/_images/courses/level-two/chapter-five/workflow2_1.png" alt="" style="width:100%"><figcaption align = "center"><i>Workflow 1 – Getting data from different sources</i></figcaption></figure>
|
||||
|
||||
1. Use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/){:target="_blank" .external} to get data from the API endpoint that stores company data. Configure the following node parameters:
|
||||
1. Use the [HTTP Request node](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/){:target="_blank" .external} to get data from the API endpoint that stores company data. Configure the following node parameters:
|
||||
|
||||
* **Authentication**: Header Auth
|
||||
* **Credentials for Header Auth**: The Header Auth name and Header Auth value you received in the email when you signed up for this course.
|
||||
@ -24,7 +24,7 @@ The first part of the workflow consists of five nodes:
|
||||
|
||||
2. Use the [Airtable node](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/){:target="_blank" .external} to list data from the `customers` table (where you updated the fields `region` and `subregion`).
|
||||
3. Use the [Merge node](/integrations/builtin/core-nodes/n8n-nodes-base.merge/){:target="_blank" .external} to merge data from the Airtable and HTTP Request node, based on the common key `customer ID`.
|
||||
4. Use the [Item Lists node](/integrations/builtin/core-nodes/n8n-nodes-base.itemLists/){:target="_blank" .external} to sort data by orderPrice in descending order.
|
||||
4. Use the [Item Lists node](/integrations/builtin/core-nodes/n8n-nodes-base.itemlists/){:target="_blank" .external} to sort data by orderPrice in descending order.
|
||||
|
||||
!!! question "Quiz questions"
|
||||
|
||||
@ -39,8 +39,8 @@ The second part of the workflow consists of five nodes:
|
||||
<figure><img src="/_images/courses/level-two/chapter-five/workflow2_2.png" alt="" style="width:100%"><figcaption align = "center"><i>Workflow 2 – Generating file for regional sales</i></figcaption></figure>
|
||||
|
||||
1. Use the [IF node](/integrations/builtin/core-nodes/n8n-nodes-base.if/){:target="_blank" .external} to filter order from the region Americas.
|
||||
2. Use the [Move Binary Data node](/integrations/builtin/core-nodes/n8n-nodes-base.moveBinaryData/){:target="_blank" .external} to transform the incoming data from JSON to binary format. Note that you need to convert all data.
|
||||
3. Use the [Write Binary File node](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/){:target="_blank" .external} to create and store files with the orders information. In the File Name field, use an expression to include the oder id in the file name, like this: `report_orderID{oder_id}.json` (you need to replace the `{order id}` with the reference the Move Binary Data node).
|
||||
2. Use the [Move Binary Data node](/integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/){:target="_blank" .external} to transform the incoming data from JSON to binary format. Note that you need to convert all data.
|
||||
3. Use the [Write Binary File node](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/){:target="_blank" .external} to create and store files with the orders information. In the File Name field, use an expression to include the oder id in the file name, like this: `report_orderID{oder_id}.json` (you need to replace the `{order id}` with the reference the Move Binary Data node).
|
||||
4. Use the [Gmail node](/integrations/builtin/app-nodes/n8n-nodes-base.gmail/){:target="_blank" .external} (or another email node) to send the files via email to an address you have access to. Note that you need to add an attachment with the data property.
|
||||
5. Use the [Discord node](/integrations/builtin/app-nodes/n8n-nodes-base.discord/){:target="_blank" .external} to send a message in the n8n Discord channel `#course-level-two`. In the node, configure the following parameters:
|
||||
* Webhook URL: The webhook URL you received in the email when you signed up for this course.
|
||||
@ -58,10 +58,10 @@ The third part of the workflow consists of seven nodes:
|
||||
|
||||
<figure><img src="/_images/courses/level-two/chapter-five/workflow2_3.png" alt="" style="width:100%"><figcaption align = "center"><i>Workflow 3 – Generating files for total sales</i></figcaption></figure>
|
||||
|
||||
1. Use the [Split In Batches node](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/){:target="_blank" .external} to split data from the Item Lists node into batches of 5.
|
||||
1. Use the [Split In Batches node](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/){:target="_blank" .external} to split data from the Item Lists node into batches of 5.
|
||||
2. Use the [Set node](/integrations/builtin/core-nodes/n8n-nodes-base.set/){:target="_blank" .external} to set four values, referenced with expressions from the previous node: `customerEmail`, `customerRegion`, `customerSince`, and `orderPrice`.
|
||||
3. Use the [Date & Time node](/integrations/builtin/core-nodes/n8n-nodes-base.dateTime/){:target="_blank" .external} to change the date format of the field `customerSince` to the format MM/DD/YYYY.
|
||||
4. Use the [Spreadsheet File node](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/){:target="_blank" .external} to create a CSV spreadsheet with the file name set as the expression: `{{$runIndex > 0 ? 'file_low_orders':'file_high_orders'}}`.
|
||||
3. Use the [Date & Time node](/integrations/builtin/core-nodes/n8n-nodes-base.datetime/){:target="_blank" .external} to change the date format of the field `customerSince` to the format MM/DD/YYYY.
|
||||
4. Use the [Spreadsheet File node](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/){:target="_blank" .external} to create a CSV spreadsheet with the file name set as the expression: `{{$runIndex > 0 ? 'file_low_orders':'file_high_orders'}}`.
|
||||
5. Use the [Discord node](/integrations/builtin/app-nodes/n8n-nodes-base.discord/){:target="_blank" .external} to send a message in the n8n Discord channel `#course-level-two`. In the node, configure the following parameters:
|
||||
* Webhook URL: The webhook URL you received in the email when you signed up for this course.
|
||||
* Text: "I created the spreadsheet `{file name}`. My ID:" followed by your ID. <br/> The `{file name}` should be an expression that references data from the Spreadsheet File node.<br/>
|
||||
|
||||
@ -4,7 +4,7 @@
|
||||
|
||||
A function is a block of code designed to perform a certain task. In n8n, you can write custom JavaScript code snippets to add, remove, and update the data you receive from a node.
|
||||
|
||||
The [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) and [Function Item](/integrations/builtin/core-nodes/n8n-nodes-base.functionItem/) nodes are the most powerful in n8n. Both nodes work similarly: they give you access to the incoming data and you can manipulate it. With these nodes you can implement any function you want using JavaScript code.
|
||||
The [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) and [Function Item](/integrations/builtin/core-nodes/n8n-nodes-base.functionitem/) nodes are the most powerful in n8n. Both nodes work similarly: they give you access to the incoming data and you can manipulate it. With these nodes you can implement any function you want using JavaScript code.
|
||||
|
||||
The code of the **Function node** gets executed once. The node receives the full items (JSON and binary data) as an array and expects an array of items as a return value. The items returned can be totally different from the incoming ones. It's possible to remove and edit existing items, and also to add or return totally new ones.
|
||||
|
||||
|
||||
@ -4,5 +4,5 @@ Data mapping means referencing data from previous nodes.
|
||||
|
||||
This section contains guidance on:
|
||||
|
||||
* Mapping data in most scenarios: [Data mapping](/data/data-mapping/data-mapping/)
|
||||
* Mapping data in most scenarios: [Data mapping](/data/data-mapping/data-mapping-ui/)
|
||||
* How to handle [item linking](/data/data-mapping/data-item-linking/) when using the Function node or building your own nodes.
|
||||
|
||||
@ -12,4 +12,4 @@ This section covers:
|
||||
* [Transforming data](/data/transforming-data/)
|
||||
* [Process data using code](/data/code/)
|
||||
* [Pinning](/data/data-pinning/) and [editing](/data/data-editing/) data during workflow development.
|
||||
* [Data mapping](/data/data-mapping/data-mapping/) and [Item linking](/data/data-mapping/data-item-linking/): how data items link to each other.
|
||||
* [Data mapping](/data/data-mapping/data-mapping-ui/) and [Item linking](/data/data-mapping/data-item-linking/): how data items link to each other.
|
||||
|
||||
@ -4,11 +4,11 @@ n8n uses a predefined [data structure](/data/data-structure/) that allows all no
|
||||
|
||||
Your incoming data may have a different data structure, in which case you will need to transform it to allow each item to be processed individually.
|
||||
|
||||
For example, the image below shows the output of an [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node that returns data incompatible with n8n's data structure. The node returns the data and displays that only one item was returned.
|
||||
For example, the image below shows the output of an [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node that returns data incompatible with n8n's data structure. The node returns the data and displays that only one item was returned.
|
||||
|
||||
|
||||
|
||||
To transform this kind of structure into the n8n data structure you can use the [Item Lists](/integrations/builtin/core-nodes/n8n-nodes-base.itemLists/) node.
|
||||
To transform this kind of structure into the n8n data structure you can use the [Item Lists](/integrations/builtin/core-nodes/n8n-nodes-base.itemlists/) node.
|
||||
|
||||
!!! note
|
||||
If you're using the HTTP Request node, you should use the Split Into items option to transform the data. You don't have to use a Function node in that case.
|
||||
|
||||
@ -60,7 +60,7 @@ Here is an [example workflow](https://n8n.io/workflows/1130) that implements a l
|
||||
|
||||
|
||||
|
||||
You should use the [Split In Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/) node when you want to batch the data in groups and process these batches. This approach is useful for avoiding API rate limits when processing large incoming data or when you only want to process a specific group of returned items.
|
||||
You should use the [Split In Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node when you want to batch the data in groups and process these batches. This approach is useful for avoiding API rate limits when processing large incoming data or when you only want to process a specific group of returned items.
|
||||
|
||||
**Note**: The Split In Batches node stops executing after all the incoming items get divided into batches and passed on to the next node in the workflow so it is not necessary to add an IF node to stop the loop.
|
||||
|
||||
@ -72,24 +72,24 @@ There are a limited number of nodes and operations where you need to design a lo
|
||||
* **List**: This operation executes only once, not for each incoming item.
|
||||
* [**Coda**](/integrations/builtin/app-nodes/n8n-nodes-base.coda/) node:
|
||||
* **Get All**: For the Table and View resources, this operation executes only once.
|
||||
* [**CrateDB**](/integrations/builtin/app-nodes/n8n-nodes-base.crateDb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**Execute Workflow**](/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow/) node executes only once by default.
|
||||
* [**Function**](/integrations/builtin/core-nodes/n8n-nodes-base.function/) node processes all the items based on the entered code snippet, but it gets executed only once. If you need to execute the Function node multiple times you have to create a loop using the [Split In Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/) node.
|
||||
* [**Google Cloud Firestore**](/integrations/builtin/app-nodes/n8n-nodes-base.googleCloudFirestore/) node:
|
||||
* [**CrateDB**](/integrations/builtin/app-nodes/n8n-nodes-base.cratedb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**Execute Workflow**](/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node executes only once by default.
|
||||
* [**Function**](/integrations/builtin/core-nodes/n8n-nodes-base.function/) node processes all the items based on the entered code snippet, but it gets executed only once. If you need to execute the Function node multiple times you have to create a loop using the [Split In Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node.
|
||||
* [**Google Cloud Firestore**](/integrations/builtin/app-nodes/n8n-nodes-base.googlecloudfirestore/) node:
|
||||
* **Get All**: For the Collection and Document resources, this operation executes only once.
|
||||
* [**Google Drive**](/integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/) node:
|
||||
* [**Google Drive**](/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/) node:
|
||||
* **List**: This operation executes only once, not for each incoming item.
|
||||
* [**Google Sheets**](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/) node:
|
||||
* [**Google Sheets**](/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/) node:
|
||||
* **Read**: This operation executes only once for the `Sheet` resource.
|
||||
* **Update**: This operation updates multiple rows if they are in the same range. It does not iterate through additional ranges.
|
||||
* [**HTTP Request**](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node: You must handle pagination yourself. If your API call returns paginated results you must create a loop to fetch one page at a time.
|
||||
* [**Microsoft SQL**](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftSql/) node does not natively handle looping, so if you want the node to process all incoming items you must create a loop.
|
||||
* [**MongoDB**](/integrations/builtin/app-nodes/n8n-nodes-base.mongoDb/) executes `Find` once, regardless of the number of incoming items.
|
||||
* [**HTTP Request**](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node: You must handle pagination yourself. If your API call returns paginated results you must create a loop to fetch one page at a time.
|
||||
* [**Microsoft SQL**](/integrations/builtin/app-nodes/n8n-nodes-base.microsoftsql/) node does not natively handle looping, so if you want the node to process all incoming items you must create a loop.
|
||||
* [**MongoDB**](/integrations/builtin/app-nodes/n8n-nodes-base.mongodb/) executes `Find` once, regardless of the number of incoming items.
|
||||
* [**Postgres**](/integrations/builtin/app-nodes/n8n-nodes-base.postgres/) node will execute and iterate over all incoming items only for Postgres related functions (for example, `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**QuestDB**](/integrations/builtin/app-nodes/n8n-nodes-base.questDb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**Read Binary Files**](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFiles/) node will fetch the files from the specified path only once. This node doesn't execute multiple times based on the incoming data. However, if the path is referenced from the incoming data, the node will fetch the files for all the valid paths.
|
||||
* [**QuestDB**](/integrations/builtin/app-nodes/n8n-nodes-base.questdb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**Read Binary Files**](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/) node will fetch the files from the specified path only once. This node doesn't execute multiple times based on the incoming data. However, if the path is referenced from the incoming data, the node will fetch the files for all the valid paths.
|
||||
* [**Redis**](/integrations/builtin/app-nodes/n8n-nodes-base.redis/) node:
|
||||
* **Info**: This operation executes only once, regardless of the number of items in the incoming data.
|
||||
* [**RSS**](/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead/) nodes executes only once regardless of the number of items in the incoming data.
|
||||
* [**Spreadsheet**](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/) node processes all the incoming data and creates a single file with all the incoming data. If you want to create individual files for each incoming item, you have to create a loop.
|
||||
* [**TimescaleDB**](/integrations/builtin/app-nodes/n8n-nodes-base.timescaleDb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
* [**RSS**](/integrations/builtin/core-nodes/n8n-nodes-base.rssfeedread/) nodes executes only once regardless of the number of items in the incoming data.
|
||||
* [**Spreadsheet**](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/) node processes all the incoming data and creates a single file with all the incoming data. If you want to create individual files for each incoming item, you have to create a loop.
|
||||
* [**TimescaleDB**](/integrations/builtin/app-nodes/n8n-nodes-base.timescaledb/) node will execute and iterate over all incoming items only for Postgres related functions (e.g. `pgInsert`, `pgUpdate`, `pqQuery`).
|
||||
|
||||
@ -162,7 +162,7 @@ Refer to [User management](/hosting/user-management/) for more information on se
|
||||
| `NODES_EXCLUDE` | String | - | Specify which nodes not to load. |
|
||||
| `NODE_FUNCTION_ALLOW_BUILTIN` | String | - | Permit users to import specific built-in modules in the Code node. Use * to allow all. n8n disables importing modules by default. |
|
||||
| `NODE_FUNCTION_ALLOW_EXTERNAL` | String | - | Permit users to import specific external modules (from `n8n/node_modules`) in the Code node. n8n disables importing modules by default. |
|
||||
| `NODES_ERROR_TRIGGER_TYPE` | String | `n8n-nodes-base.errorTrigger` | Specify which Node Type to use as Error Trigger. |
|
||||
| `NODES_ERROR_TRIGGER_TYPE` | String | `n8n-nodes-base.errorTrigger` | Specify which node type to use as Error Trigger. |
|
||||
| `N8N_CUSTOM_EXTENSIONS` | String | - | Specify the path to additional directories containing your custom nodes. |
|
||||
|
||||
## Queues
|
||||
|
||||
@ -118,7 +118,7 @@ services:
|
||||
- ${DATA_FOLDER}/.n8n:/home/node/.n8n
|
||||
```
|
||||
|
||||
If you are planning on reading/writing local files with n8n (for example, by using the [*Write Binary File* node](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/), you will need to configure a data directory for those files here. If you are running n8n as a root user, add this under `volumes` for the n8n service:
|
||||
If you are planning on reading/writing local files with n8n (for example, by using the [*Write Binary File* node](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/), you will need to configure a data directory for those files here. If you are running n8n as a root user, add this under `volumes` for the n8n service:
|
||||
|
||||
```yaml
|
||||
- /local-files:/files
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send updates about the position of the ISS every minute to an [ActiveMQ](https://activemq.apache.org/) queue using the AMQP Sender node. You can also find the [workflow](https://n8n.io/workflows/762) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [AMQP Sender]()
|
||||
|
||||
|
||||
@ -26,7 +26,7 @@
|
||||
|
||||
## Example Usage
|
||||
|
||||
This workflow allows you to create a new list, add a new contact to that list, update the contact, and get all contacts in the list using the Autopilot node. You can also find the [workflow](https://n8n.io/workflows/990) on n8n.io. This example usage workflow uses the following nodes.
|
||||
This workflow allows you to create a new list, add a new contact to that list, update the contact, and get all contacts in the list using the Autopilot node. You can also find the [workflow](https://n8n.io/workflows/990-manage-contacts-via-autopilot/) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Autopilot]()
|
||||
|
||||
|
||||
@ -21,7 +21,7 @@ This workflow allows you to analyze the sentiment of feedback received via a Typ
|
||||
- [AWS Comprehend]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
|
||||
This workflow allows you to detect a face from an image using the AWS Rekognition node. You can also find the [workflow](https://n8n.io/workflows/694) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [AWS Rekognition]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
@ -31,7 +31,7 @@ The Start node exists by default when you create a new workflow.
|
||||
|
||||
### 2. HTTP Request node (GET)
|
||||
|
||||
This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read an image file from the path you specify.
|
||||
This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node to read an image file from the path you specify.
|
||||
|
||||
1. Enter the URL of the image in the ***URL*** field. For example, `https://n8n.io/_nuxt/img/04c67e5.png`.
|
||||
2. Select 'File' from the ***Response Format*** dropdown list.
|
||||
|
||||
@ -14,7 +14,7 @@
|
||||
|
||||
This workflow allows you to send position updates of the ISS every minute to a queue using the AWS SQS node. You can also find the [workflow](https://n8n.io/workflows/1047) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [AWS SQS]()
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ This workflow allows you to get the price of BTC in EUR using the CoinGecko node
|
||||
- [CoinGecko]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to translate cocktail instructions to French. You can also find the [workflow](https://n8n.io/workflows/998) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [DeepL]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -28,7 +28,7 @@
|
||||
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.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Dropbox]()
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ This workflow allows you to find email and enrich your contact from a Google She
|
||||
|
||||
This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Google Sheets node](/integrations/builtin/app-nodes/n8n-nodes-base.googleSheets/)
|
||||
- [Google Sheets node](/integrations/builtin/app-nodes/n8n-nodes-base.googlesheets/)
|
||||
- [Dropcontact node]()
|
||||
- [Lemlist node](/integrations/builtin/app-nodes/n8n-nodes-base.lemlist/)
|
||||
|
||||
|
||||
@ -22,7 +22,7 @@ This workflow allows you to get all the contacts from GetResponse and check if t
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [GetResponse]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -42,8 +42,8 @@
|
||||
|
||||
Refer to Google's [Gmail API documentation](https://developers.google.com/gmail/api) for detailed information about the API that this node integrates with.
|
||||
|
||||
n8n provides a trigger node for Gmail. You can find the trigger node docs [here](/integrations/builtin/trigger-nodes/gmailTrigger/).
|
||||
n8n provides a trigger node for Gmail. You can find the trigger node docs [here](/integrations/builtin/trigger-nodes/gmailtrigger/).
|
||||
|
||||
View [example workflows and related content](https://n8n.io/integrations/356-gmail/){:target=_blank .external-link} on our website.
|
||||
View [example workflows and related content](https://n8n.io/integrations/gmail/){:target=_blank .external-link} on our website.
|
||||
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
|
||||
This workflow allows you to send position updates of the ISS every minute to a table in Google BigQuery. You can also find the [workflow](https://n8n.io/workflows/1049) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [Google BigQuery]()
|
||||
|
||||
|
||||
@ -18,7 +18,7 @@ This workflow allows you to analyze the sentiment of feedback received via a Typ
|
||||
- [Google Cloud Natural Language]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [Mattermost](/integrations/builtin/app-nodes/n8n-nodes-base.mattermost/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
This workflow allows you to receive updates of the position of the ISS every minute and push it to a database using the Google Cloud Realtime Database node. You can also find the [workflow](https://n8n.io/workflows/787) on n8n.io. This example usage workflow uses the following nodes.
|
||||
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [Google Cloud Realtime Database]()
|
||||
|
||||
|
||||
@ -32,7 +32,7 @@
|
||||
This workflow allows you to download a file from Google Drive. You can also find the [workflow](https://n8n.io/workflows/515) on the website. This example usage workflow uses the following two nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Google Drive]()
|
||||
- [Write Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/)
|
||||
- [Write Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ The Start node exists by default when you create a new workflow.
|
||||
|
||||
### 2. Set node
|
||||
|
||||
This example workflow uses the Set node to generate data that we want to add to Google Sheets. You can also use other nodes, for example, the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node, to get the data you want to add to the Google Sheets.
|
||||
This example workflow uses the Set node to generate data that we want to add to Google Sheets. You can also use other nodes, for example, the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node, to get the data you want to add to the Google Sheets.
|
||||
|
||||
1. Click on the ***Add Value*** button and select 'String' from the dropdown list.
|
||||
2. Enter `Name` in the ***Name*** field.
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a message using the Gotify node. You can also find the [workflow](https://n8n.io/workflows/774) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Gotify]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -17,7 +17,7 @@
|
||||
|
||||
This workflow allows you to create, update, and get a profile using the Humantic AI node. You can also find the [workflow](https://n8n.io/workflows/784) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Humantic AI]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -14,7 +14,7 @@
|
||||
|
||||
This workflow allows you to send updates about the position of the ISS every minute to a topic in Kafka using the Kafka node. You can also find the [workflow](https://n8n.io/workflows/750) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [Kafka]()
|
||||
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a notification using the Line node. You can also find the [workflow](https://n8n.io/workflows/773) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Line]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -14,7 +14,7 @@
|
||||
|
||||
This workflow allows you to translate cocktail instructions to Italian. You can also find the [workflow](https://n8n.io/workflows/797) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [LingvaNex]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
|
||||
This workflow allows you to get an image from a URL and post it on LinkedIn. You can also find the [workflow](https://n8n.io/workflows/681) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [LinkedIn]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -32,7 +32,7 @@ This workflow allows you to create a room, invite members from a different room,
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Matrix]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -42,7 +42,7 @@
|
||||
This workflow allows you to create, add an attachment, and send a draft using the Microsoft Outlook node. You can also find the [workflow](https://n8n.io/workflows/867) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Microsoft Outlook]()
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -20,7 +20,7 @@
|
||||
|
||||
This workflow allows you to extract information from an image of a receipt using the Mindee node. You can also find the [workflow](https://n8n.io/workflows/702) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Mindee]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
|
||||
This workflow allows you to send position updates of the ISS every minute to a topic in MQTT using the MQTT node. You can also find the [workflow](https://n8n.io/workflows/1069) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [MQTT]()
|
||||
|
||||
|
||||
@ -34,7 +34,7 @@
|
||||
This workflow allows you to create a folder in Nextcloud, upload a file into that folder, and list the contents of the folder. You can also find the [workflow](https://n8n.io/workflows/620) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Nextcloud]()
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ This workflow allows you to check if preview for a link is available and return
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Peekalink]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@
|
||||
|
||||
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](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Plivo]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -18,7 +18,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a push notification using the Pushbullet node. You can also find the [workflow](https://n8n.io/workflows/740) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Pushbullet]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a push notification using the Pushcut node. You can also find the [workflow](https://n8n.io/workflows/843) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Pushcut]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a push notification using the Pushover node. You can also find the [workflow](https://n8n.io/workflows/740) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Pushover]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -10,7 +10,7 @@
|
||||
|
||||
This workflow allows you to send updates about the position of the ISS every minute to a queue using the RabbitMQ node. You can also find the [workflow](https://n8n.io/workflows/844) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [RabbitMQ]()
|
||||
|
||||
|
||||
@ -24,13 +24,13 @@ S3 is an object storage service that allows you to block public access to all of
|
||||
* Delete a folder
|
||||
* Get all folders
|
||||
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property.
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the file as a data property.
|
||||
|
||||
## Example Usage
|
||||
|
||||
This workflow allows you to upload a file to an S3 compatible server and get a list of all the files in a bucket using the S3 node. You can also find the [workflow](https://n8n.io/workflows/674) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [S3]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -63,7 +63,7 @@
|
||||
This workflow allows you to create a channel, invite users to the channel, post a message, and upload a file to the channel. You can also find the [workflow](https://n8n.io/workflows/811) on n8n.io This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Slack]()
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -127,7 +127,7 @@ In the screenshot below, you will notice that node sends a message with an attac
|
||||
|
||||
### 5. HTTP Request node (GET)
|
||||
|
||||
This node will fetch a file from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify.
|
||||
This node will fetch a file from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node to read a file from the path you specify.
|
||||
|
||||
1. Enter the URL of a file in the ***URL*** field.
|
||||
2. Select 'File' from the ***Response Format*** dropdown list.
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via a push notification using the Spontit node. You can also find the [workflow](https://n8n.io/workflows/796) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Spontit]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -39,7 +39,7 @@
|
||||
|
||||
This workflow allows you to send a cocktail recipe to a specified chat ID every day via a Telegram bot. You can also find the [workflow](https://n8n.io/workflows/781) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Telegram]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
@ -96,7 +96,7 @@ In the screenshot below, you will notice that the node sends a message on Telegr
|
||||
### How can I send more than 30 messages per second?
|
||||
|
||||
The Telegram API has a [limitation](https://core.telegram.org/bots/faq#broadcasting-to-users) of sending only 30 messages per second. Follow the steps mentioned below to send more than 30 messages:
|
||||
1. Split In Batches node: Use the [Split in Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitInBatches/) node to get at most 30 chat IDs from your database.
|
||||
1. Split In Batches node: Use the [Split in Batches](/integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node to get at most 30 chat IDs from your database.
|
||||
2. Telegram node: Connect the Telegram node with the Split In Batches node. Use the ***Expression Editor*** to select the Chat IDs from the Split in Batches node.
|
||||
3. Function node: Connect the [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/) node with the Telegram node. Use the Function node to wait for a few seconds before fetching the next batch of chat IDs. Connect this node with the Split In Batches node.
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@
|
||||
|
||||
This workflow allows you to receive updates of the position of the ISS every minute and insert it to a table using the TimscaleDB node. You can also find the [workflow](https://n8n.io/workflows/917) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [TimescaleDB]()
|
||||
|
||||
|
||||
@ -24,4 +24,4 @@ View [example workflows and related content](https://n8n.io/integrations/venafi-
|
||||
n8n also provides:
|
||||
|
||||
* A [trigger node](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectdatacentertrigger/) for Venafi TLS Protect Datacenter.
|
||||
* A [node](/integrations/builtin/app-nodes/n8n-nodes-base.venafiTlsProtectCloud/) and [trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger/) node for Venafi TLS Protect Cloud.
|
||||
* A [node](/integrations/builtin/app-nodes/n8n-nodes-base.venafitlsprotectcloud/) and [trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.venafitlsprotectcloudtrigger/) node for Venafi TLS Protect Cloud.
|
||||
|
||||
@ -15,7 +15,7 @@
|
||||
|
||||
This workflow allows you to send daily weather updates via an SMS message using the Vonage node. You can also find the [workflow](https://n8n.io/workflows/723) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Cron](/integrations/builtin/core-nodes/n8n-nodes-base.cron/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Vonage]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -38,7 +38,7 @@
|
||||
|
||||
This workflow allows you to upload a video, create a playlist, and add the video to the playlist in YouTube. You can also find the [workflow](https://n8n.io/workflows/638) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/)
|
||||
- [YouTube]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
The Activation Trigger node gets triggered when an event gets fired by n8n or a workflow.
|
||||
|
||||
!!! warning
|
||||
The Activation Trigger node has been deprecated. It has been replaced by two new nodes - the [n8n Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.n8nTrigger/) and the [Workflow Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.workflowTrigger/) node. For more details, check out the entry in the [breaking changes](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01170) page.
|
||||
The Activation Trigger node has been deprecated. It has been replaced by two new nodes - the [n8n Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.n8ntrigger/) and the [Workflow Trigger](/integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/) node. For more details, check out the entry in the [breaking changes](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01170) page.
|
||||
|
||||
|
||||
!!! note "Keep in mind"
|
||||
|
||||
@ -21,7 +21,7 @@ The Compression node is useful to compress and decompress files. You can either
|
||||
|
||||
This workflow allows you to compress binary files to zip format and upload them to Dropbox. You can also find the [workflow](https://n8n.io/workflows/908) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Dropbox](/integrations/builtin/app-nodes/n8n-nodes-base.dropbox/)
|
||||
|
||||
|
||||
@ -36,7 +36,7 @@ The start node exists by default when you create a new workflow.
|
||||
|
||||
### 2. HTTP Request node (GET)
|
||||
|
||||
This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify.
|
||||
This example workflow uses the HTTP Request node to fetch an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node to read a file from the path you specify.
|
||||
|
||||
1. Enter the URL of the image in the ***URL*** field. For example, `https://docs.n8n.io/assets/img/final-workflow.f380b957.png`.
|
||||
2. Select 'File' from the ***Response Format*** dropdown list.
|
||||
@ -49,7 +49,7 @@ In the screenshot below, you will notice that the HTTP Request node fetches the
|
||||
|
||||
### 3. HTTP Request1 node (GET)
|
||||
|
||||
This node fetches an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node to read a file from the path you specify.
|
||||
This node fetches an image from a URL. You can also use the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node to read a file from the path you specify.
|
||||
|
||||
1. Enter the URL of the image in the ***URL*** field. For example, `https://n8n.io/n8n-logo.png`.
|
||||
2. Select 'File' from the ***Response Format*** dropdown list.
|
||||
|
||||
@ -4,7 +4,7 @@ The Edit Image node is used to manipulate and edit images.
|
||||
|
||||
!!! note "Keep in mind"
|
||||
1. If you are not running n8n on Docker, you'll need to install [GraphicsMagick](http://www.graphicsmagick.org/README.html).
|
||||
2. You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Edit Image node.
|
||||
2. You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the image file as a data property to the Edit Image node.
|
||||
|
||||
|
||||
## Node Reference
|
||||
@ -38,7 +38,7 @@ You can also specify a file format using the *Format* field in the *Add Option*
|
||||
|
||||
This workflow allows you to add text to an image downloaded from the internet using the Edit Image node. You can also find the [workflow](https://n8n.io/workflows/591) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Edit Image]()
|
||||
|
||||
|
||||
|
||||
@ -27,7 +27,7 @@ This workflow allows you to execute a command that returns the percentage of the
|
||||
- [Execute Command]()
|
||||
- [IF](/integrations/builtin/core-nodes/n8n-nodes-base.if/)
|
||||
- [Twilio](/integrations/builtin/app-nodes/n8n-nodes-base.twilio/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [No Operation, do nothing](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
|
||||
The final workflow should look like the following image.
|
||||
@ -124,7 +124,7 @@ ls
|
||||
|
||||
### How to run the curl command in the Execute Command node?
|
||||
|
||||
You can also use the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to make a cURL request.
|
||||
You can also use the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) 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.
|
||||
|
||||
|
||||
@ -7,4 +7,4 @@ n8n allows you to call workflows from other workflows. This is useful if you wan
|
||||
* Reuse a workflow: for example, you could have multiple workflows pulling and processing data from different sources, then have all those workflows call a single workflow that generates a report.
|
||||
* Break large workflows into smaller components.
|
||||
|
||||
This node runs in response to a call from the [Execute Workflow](/integrations/builtin/core-nodes/n8n-nodes-base.executeWorkflow/) node.
|
||||
This node runs in response to a call from the [Execute Workflow](/integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node.
|
||||
|
||||
@ -14,7 +14,7 @@ The FTP node is useful to access and upload files to an FTP server.
|
||||
- Rename/move content from old path to new path
|
||||
- Upload a file
|
||||
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property.
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the file as a data property.
|
||||
|
||||
## Node Reference
|
||||
|
||||
@ -26,7 +26,7 @@ The FTP node is useful to access and upload files to an FTP server.
|
||||
|
||||
This workflow allows you to upload a file to an FTP server and get a list of all files using the FTP node. You can also find the [workflow](https://n8n.io/workflows/663) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [FTP]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -28,7 +28,7 @@ The property can either contain a string or an array of strings.
|
||||
|
||||
This workflow allows you to extract titles and URLs of all the articles from the [Hackernoon](https://hackernoon.com/) homepage using the HTML Extract node. You can also find the [workflow](https://n8n.io/workflows/434) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [HTML Extract]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -102,7 +102,7 @@ Select **Execute node**. n8n calls the `users` endpoint of the Reqres API, and o
|
||||
|
||||
### Send a binary file to an API endpoint
|
||||
|
||||
1. Connect the HTTP Request node with a node that has previously fetched the binary file. For example, this could be an HTTP Request node, [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node, [Google Drive](/integrations/builtin/app-nodes/n8n-nodes-base.googleDrive/) node, and so on.
|
||||
1. Connect the HTTP Request node with a node that has previously fetched the binary file. For example, this could be an HTTP Request node, [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node, [Google Drive](/integrations/builtin/app-nodes/n8n-nodes-base.googledrive/) node, and so on.
|
||||
2. Select **POST** in the **Method** dropdown. Check the API documentation of your API to make sure that you have selected the correct HTTP request method.
|
||||
3. Enter the URL you want to send the binary file to in the **URL** field.
|
||||
4. Enable **Send Body**.
|
||||
|
||||
@ -10,7 +10,7 @@ The iCalendar node allows you to create event files that can be shared as an att
|
||||
|
||||
This workflow allows you to create an event file and send it as an attachment via email. You can also find the [workflow](https://n8n.io/workflows/1083) on n8n.io. This example usage workflow would use the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/)
|
||||
- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendemail/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -194,4 +194,4 @@ Output in table view:
|
||||
|
||||
n8n provides an example workflow that demonstrates key Merge node concepts.
|
||||
|
||||
Go to [Joining different datasets](https://n8n.io/workflows/1747/){:target=_blank .external-link} and select **Use workflow** to copy the example workflow. You can then paste it into your n8n instance.
|
||||
Go to [Joining different datasets](https://n8n.io/workflows/1747-joining-different-datasets/){:target=_blank .external-link} and select **Use workflow** to copy the example workflow. You can then paste it into your n8n instance.
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
The Move Binary Data node is useful to move data between binary and JSON properties.
|
||||
|
||||
!!! note "Hint"
|
||||
If you need to convert an entire CSV file to JSON, use the [Spreadsheet File](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetFile/) node.
|
||||
If you need to convert an entire CSV file to JSON, use the [Spreadsheet File](/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/) node.
|
||||
|
||||
|
||||
## Node Reference
|
||||
@ -36,8 +36,8 @@ The Move Binary Data node is useful to move data between binary and JSON propert
|
||||
|
||||
This workflow allows you to store the JSON data received from the [CocktailDB API](https://www.thecocktaildb.com/) to your machine. You can also find the [workflow](https://n8n.io/workflows/652) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [Write Binary Data](/integrations/builtin/core-nodes/n8n-nodes-base.writeBinaryFile/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Write Binary Data](/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
The Read PDF node is used to read data from PDF documents and extract its content as text.
|
||||
|
||||
!!! note "Keep in mind"
|
||||
You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Read PDF node.
|
||||
You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the image file as a data property to the Read PDF node.
|
||||
|
||||
|
||||
## Node Reference
|
||||
@ -16,7 +16,7 @@ The Read PDF node has one property:
|
||||
|
||||
This workflow allows you to read a PDF file using the Read PDF node. You can also find the [workflow](https://n8n.io/workflows/585) on the website. This example usage workflow would use the following three nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/)
|
||||
- [PDF Read]()
|
||||
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ The Send Email node is used to send an email via an SMTP email server.
|
||||
!!! note "Keep in mind"
|
||||
1. Before sending, ensure that you have already created email addresses that are approved for sending on your SMTP service.
|
||||
2. The Send Email node merely sends an email via your SMTP server and plays no part in email deliverability.
|
||||
3. To attach a file, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass a file as a data property.
|
||||
3. To attach a file, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass a file as a data property.
|
||||
|
||||
|
||||
## Basic Operations
|
||||
|
||||
@ -18,7 +18,7 @@ This workflow allows you to read RSS feed from two different sources using the S
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/)
|
||||
- [Split In Batches]()
|
||||
- [RSS Feed Read](/integrations/builtin/core-nodes/n8n-nodes-base.rssFeedRead/)
|
||||
- [RSS Feed Read](/integrations/builtin/core-nodes/n8n-nodes-base.rssfeedread/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
The Spreadsheet File node is used to access data from spreadsheet files.
|
||||
|
||||
!!! note "Keep in mind"
|
||||
You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the image file as a data property to the Spreadsheet File node.
|
||||
You will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the image file as a data property to the Spreadsheet File node.
|
||||
|
||||
|
||||
## Basic Operations
|
||||
@ -35,7 +35,7 @@ When writing to a spreadsheet file, the *File Format* field can be used to speci
|
||||
|
||||
This workflow allows you to read a spreadsheet file using the Spreadsheet File node. You can also find the [workflow](https://n8n.io/workflows/586) on the website. This example usage workflow would use the following three nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/)
|
||||
- [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/)
|
||||
- [Spreadsheet File]()
|
||||
|
||||
|
||||
|
||||
@ -12,7 +12,7 @@ The SSH node is useful for executing commands via the Secure Shell Protocol.
|
||||
- Download a file
|
||||
- Upload a file
|
||||
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readBinaryFile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node to pass the file as a data property.
|
||||
**Note:** To attach a file for upload, you will need to use an additional node such as the [Read Binary File](/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/) node or the [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node to pass the file as a data property.
|
||||
|
||||
## Node Reference
|
||||
|
||||
|
||||
@ -35,7 +35,7 @@ This workflow executes four different Set nodes based on the output given by a S
|
||||
- [Function](/integrations/builtin/core-nodes/n8n-nodes-base.function/)
|
||||
- [Switch]()
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [NoOp](/integrations/builtin/core-nodes/n8n-nodes-base.noOp/)
|
||||
- [NoOp](/integrations/builtin/core-nodes/n8n-nodes-base.noop/)
|
||||
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -68,7 +68,7 @@ This example workflow uses the following nodes.
|
||||
- [Wait]()
|
||||
- [Webhook](/integrations/builtin/core-nodes/n8n-nodes-base.webhook/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendEmail/)
|
||||
- [Send Email](/integrations/builtin/core-nodes/n8n-nodes-base.sendemail/)
|
||||
- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -63,7 +63,7 @@ First of all, in the parameters section, we have the Webhook URLs. Clicking on t
|
||||
|
||||
This workflow allows you to receive the weather information of a city using the Webhook and the OpenWeatherMap nodes. You can also find the [workflow](https://n8n.io/workflows/807) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Webhook]()
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openWeatherMap/)
|
||||
- [OpenWeatherMap](/integrations/builtin/app-nodes/n8n-nodes-base.openweathermap/)
|
||||
- [Set](/integrations/builtin/core-nodes/n8n-nodes-base.set/)
|
||||
|
||||
The final workflow should look like the following image.
|
||||
@ -143,7 +143,7 @@ Here is a GIF demonstrating how to retrieve the test and production webhook URLs
|
||||
|
||||
### How to use the HTTP Request node to trigger the Webhook node?
|
||||
|
||||
The [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/) node is used to make HTTP requests to the URL you specify. To use the HTTP Request node to trigger the Webhook node, follow the steps mentioned below.
|
||||
The [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) node is used to make HTTP requests to the URL you specify. To use the HTTP Request node to trigger the Webhook node, follow the steps mentioned below.
|
||||
1. Create a new workflow.
|
||||
2. Add the HTTP Request node to the workflow.
|
||||
3. Select the appropriate method from the ***Request Method*** dropdown list. For example, if you have selected GET as the HTTP method in your Webhook node, select GET as the request method in the HTTP Request node.
|
||||
|
||||
@ -16,7 +16,7 @@ The Write Binary File node is used to write a file to the host machine that runs
|
||||
|
||||
This workflow allows you to write a file to the host machine using the Write Binary File node. You can also find the [workflow](https://n8n.io/workflows/590) on the website. This example usage workflow would use the following three nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [Write Binary File]()
|
||||
|
||||
|
||||
|
||||
@ -28,7 +28,7 @@ The XML node is useful to convert data from and to XML.
|
||||
|
||||
This workflow allows you to convert the JSON data received from the [CocktailDB API](https://www.thecocktaildb.com/) to XML. You can also find the [workflow](https://n8n.io/workflows/661) on n8n.io. This example usage workflow uses the following nodes.
|
||||
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/)
|
||||
- [HTTP Request](/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/)
|
||||
- [XML]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes:
|
||||
|
||||
- [Action Network](/integrations/builtin/app-nodes/n8n-nodes-base.actionNetwork/)
|
||||
- [Action Network](/integrations/builtin/app-nodes/n8n-nodes-base.actionnetwork/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,8 +2,8 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with ActiveCampaign.
|
||||
|
||||
- [ActiveCampaign](/integrations/builtin/app-nodes/n8n-nodes-base.activeCampaign/)
|
||||
- [Active Campaign Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.activeCampaignTrigger/)
|
||||
- [ActiveCampaign](/integrations/builtin/app-nodes/n8n-nodes-base.activecampaign/)
|
||||
- [Active Campaign Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.activecampaigntrigger/)
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Acuity Scheduling.
|
||||
|
||||
- [Acuity Scheduling Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.acuitySchedulingTrigger/)
|
||||
- [Acuity Scheduling Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.acuityschedulingtrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with Affinity.
|
||||
|
||||
- [Affinity](/integrations/builtin/app-nodes/n8n-nodes-base.affinity/)
|
||||
- [Affinity Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.affinityTrigger/)
|
||||
- [Affinity Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.affinitytrigger/)
|
||||
|
||||
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Agile CRM.
|
||||
|
||||
- [Agile CRM](/integrations/builtin/app-nodes/n8n-nodes-base.agileCrm/)
|
||||
- [Agile CRM](/integrations/builtin/app-nodes/n8n-nodes-base.agilecrm/)
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with Airtable.
|
||||
|
||||
- [Airtable](/integrations/builtin/app-nodes/n8n-nodes-base.airtable/)
|
||||
- [Airtable Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.airtableTrigger/)
|
||||
- [Airtable Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.airtabletrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with AMQP.
|
||||
|
||||
- [AMQP Sender](/integrations/builtin/app-nodes/n8n-nodes-base.amqp/)
|
||||
- [AMQP Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.amqpTrigger/)
|
||||
- [AMQP Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.amqptrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with APITemplate.io.
|
||||
|
||||
- [APITemplate.io](/integrations/builtin/app-nodes/n8n-nodes-base.apiTemplateIo/)
|
||||
- [APITemplate.io](/integrations/builtin/app-nodes/n8n-nodes-base.apitemplateio/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with Asana.
|
||||
|
||||
- [Asana](/integrations/builtin/app-nodes/n8n-nodes-base.asana/)
|
||||
- [Asana Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.asanaTrigger/)
|
||||
- [Asana Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.asanatrigger/)
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with Autopilot.
|
||||
|
||||
- [Autopilot](/integrations/builtin/app-nodes/n8n-nodes-base.autopilot/)
|
||||
- [Autopilot Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilotTrigger/)
|
||||
- [Autopilot Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.autopilottrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,18 +2,18 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with AWS.
|
||||
|
||||
- [AWS Certificate Manager](/integrations/builtin/app-nodes/n8n-nodes-base.awsCertificateManager/)
|
||||
- [AWS DynamoDB](/integrations/builtin/app-nodes/n8n-nodes-base.awsDynamoDb/)
|
||||
- [AWS Elastic Load Balancing](/integrations/builtin/app-nodes/n8n-nodes-base.awsElb/)
|
||||
- [AWS Lambda](/integrations/builtin/app-nodes/n8n-nodes-base.awsLambda/)
|
||||
- [AWS Rekognition](/integrations/builtin/app-nodes/n8n-nodes-base.awsRekognition/)
|
||||
- [AWS Certificate Manager](/integrations/builtin/app-nodes/n8n-nodes-base.awscertificatemanager/)
|
||||
- [AWS DynamoDB](/integrations/builtin/app-nodes/n8n-nodes-base.awsdynamodb/)
|
||||
- [AWS Elastic Load Balancing](/integrations/builtin/app-nodes/n8n-nodes-base.awselb/)
|
||||
- [AWS Lambda](/integrations/builtin/app-nodes/n8n-nodes-base.awslambda/)
|
||||
- [AWS Rekognition](/integrations/builtin/app-nodes/n8n-nodes-base.awsrekognition/)
|
||||
- [AWS S3](/integrations/builtin/app-nodes/n8n-nodes-base.awsS3/)
|
||||
- [AWS SES](/integrations/builtin/app-nodes/n8n-nodes-base.awsSes/)
|
||||
- [AWS SNS](/integrations/builtin/app-nodes/n8n-nodes-base.awsSns/)
|
||||
- [AWS SNS Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.awsSnsTrigger/)
|
||||
- [AWS SQS](/integrations/builtin/app-nodes/n8n-nodes-base.awsSqs/)
|
||||
- [AWS Textract](/integrations/builtin/app-nodes/n8n-nodes-base.awsTextract/)
|
||||
- [AWS Transcribe](/integrations/builtin/app-nodes/n8n-nodes-base.awsTranscribe/)
|
||||
- [AWS SES](/integrations/builtin/app-nodes/n8n-nodes-base.awsses/)
|
||||
- [AWS SNS](/integrations/builtin/app-nodes/n8n-nodes-base.awssns/)
|
||||
- [AWS SNS Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.awssnstrigger/)
|
||||
- [AWS SQS](/integrations/builtin/app-nodes/n8n-nodes-base.awssqs/)
|
||||
- [AWS Textract](/integrations/builtin/app-nodes/n8n-nodes-base.awstextract/)
|
||||
- [AWS Transcribe](/integrations/builtin/app-nodes/n8n-nodes-base.awstranscribe/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with BambooHR.
|
||||
|
||||
- [BambooHR](/integrations/builtin/app-nodes/n8n-nodes-base.bambooHr/)
|
||||
- [BambooHR](/integrations/builtin/app-nodes/n8n-nodes-base.bamboohr/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Bitbucket.
|
||||
|
||||
- [Bitbucket Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbucketTrigger/)
|
||||
- [Bitbucket Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.bitbuckettrigger/)
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
You can use these credentials to authenticate the following nodes with Box.
|
||||
|
||||
- [Box](/integrations/builtin/app-nodes/n8n-nodes-base.box/)
|
||||
- [Box Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.boxTrigger/)
|
||||
- [Box Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.boxtrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Brandfetch.
|
||||
|
||||
- [Brandfetch](/integrations/builtin/app-nodes/n8n-nodes-base.Brandfetch/)
|
||||
- [Brandfetch](/integrations/builtin/app-nodes/n8n-nodes-base.brandfetch/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Cal.
|
||||
|
||||
- [Cal Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calTrigger/)
|
||||
- [Cal Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.caltrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@ -2,7 +2,7 @@
|
||||
|
||||
You can use these credentials to authenticate the following nodes with Calendly.
|
||||
|
||||
- [Calendly Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlyTrigger/)
|
||||
- [Calendly Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.calendlytrigger/)
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user