Skip to content

Commit

Permalink
add 3 new nodes; set up redirects
Browse files Browse the repository at this point in the history
  • Loading branch information
StarfallProjects committed Dec 11, 2023
1 parent ca59491 commit f6e6daa
Show file tree
Hide file tree
Showing 22 changed files with 175 additions and 190 deletions.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
35 changes: 20 additions & 15 deletions docs/_redirects
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@

/integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/integrations/builtin/core-nodes/n8n-nodes-base.ical/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/integrations/builtin/core-nodes/n8n-nodes-base.readpdf/ /integrations/builtin/core-nodes/n8n-nodes-base.extractfromfile/
/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/

/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.documentbinaryinputloader/ /integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/
/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.documentjsoninputloader/ /integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.documentdefaultdataloader/
Expand Down Expand Up @@ -81,7 +86,7 @@
/security-audit/ /hosting/security-audit/
/reference/data-collection/ /privacy-security/privacy/

/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/
/integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/

/reference/release-notes/ /release-notes/
/integrations/builtin/core-nodes/n8n-nodes-base.htmlextract/ /integrations/builtin/core-nodes/n8n-nodes-base.html/
Expand Down Expand Up @@ -492,7 +497,7 @@
/nodes/n8n-nodes-base.humanticAi/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticai/
/nodes/n8n-nodes-base.humanticai/ /integrations/builtin/app-nodes/n8n-nodes-base.humanticai/
/nodes/n8n-nodes-base.hunter/ /integrations/builtin/app-nodes/n8n-nodes-base.hunter/
/nodes/n8n-nodes-base.iCal/ /integrations/builtin/core-nodes/n8n-nodes-base.ical/
/nodes/n8n-nodes-base.iCal/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/nodes/n8n-nodes-base.if/ /integrations/builtin/core-nodes/n8n-nodes-base.if/
/nodes/n8n-nodes-base.intercom/ /integrations/builtin/app-nodes/n8n-nodes-base.intercom/
/nodes/n8n-nodes-base.interval/ /integrations/builtin/core-nodes/n8n-nodes-base.interval/
Expand Down Expand Up @@ -584,8 +589,8 @@
/nodes/n8n-nodes-base.mongodb/ /integrations/builtin/app-nodes/n8n-nodes-base.mongodb/
/nodes/n8n-nodes-base.monicaCrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicacrm/
/nodes/n8n-nodes-base.monicacrm/ /integrations/builtin/app-nodes/n8n-nodes-base.monicacrm/
/nodes/n8n-nodes-base.moveBinaryData/ /integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/
/nodes/n8n-nodes-base.movebinarydata/ /integrations/builtin/core-nodes/n8n-nodes-base.movebinarydata/
/nodes/n8n-nodes-base.moveBinaryData/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/nodes/n8n-nodes-base.movebinarydata/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/nodes/n8n-nodes-base.mqtt/ /integrations/builtin/app-nodes/n8n-nodes-base.mqtt/
/nodes/n8n-nodes-base.mqttTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqtttrigger/
/nodes/n8n-nodes-base.mqtttrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.mqtttrigger/
Expand Down Expand Up @@ -658,12 +663,12 @@
/nodes/n8n-nodes-base.rabbitmqTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqtrigger/
/nodes/n8n-nodes-base.rabbitmqtrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.rabbitmqtrigger/
/nodes/n8n-nodes-base.raindrop/ /integrations/builtin/app-nodes/n8n-nodes-base.raindrop/
/nodes/n8n-nodes-base.readBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/
/nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfile/
/nodes/n8n-nodes-base.readBinaryFiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/
/nodes/n8n-nodes-base.readbinaryfiles/ /integrations/builtin/core-nodes/n8n-nodes-base.readbinaryfiles/
/nodes/n8n-nodes-base.readPDF/ /integrations/builtin/core-nodes/n8n-nodes-base.readpdf/
/nodes/n8n-nodes-base.readpdf/ /integrations/builtin/core-nodes/n8n-nodes-base.readpdf/
/nodes/n8n-nodes-base.readBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.readbinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.readBinaryFiles/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.readbinaryfiles/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.readPDF/ /integrations/builtin/core-nodes/n8n-nodes-base.extractfromfile/
/nodes/n8n-nodes-base.readpdf/ /integrations/builtin/core-nodes/n8n-nodes-base.extractfromfile/
/nodes/n8n-nodes-base.reddit/ /integrations/builtin/app-nodes/n8n-nodes-base.reddit/
/nodes/n8n-nodes-base.redis/ /integrations/builtin/app-nodes/n8n-nodes-base.redis/
/nodes/n8n-nodes-base.redisTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.redistrigger/
Expand Down Expand Up @@ -710,8 +715,8 @@
/nodes/n8n-nodes-base.splunk/ /integrations/builtin/app-nodes/n8n-nodes-base.splunk/
/nodes/n8n-nodes-base.spontit/ /integrations/builtin/app-nodes/n8n-nodes-base.spontit/
/nodes/n8n-nodes-base.spotify/ /integrations/builtin/app-nodes/n8n-nodes-base.spotify/
/nodes/n8n-nodes-base.spreadsheetFile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/
/nodes/n8n-nodes-base.spreadsheetfile/ /integrations/builtin/core-nodes/n8n-nodes-base.spreadsheetfile/
/nodes/n8n-nodes-base.spreadsheetFile/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/nodes/n8n-nodes-base.spreadsheetfile/ /integrations/builtin/core-nodes/n8n-nodes-base.converttofile/
/nodes/n8n-nodes-base.sseTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.ssetrigger/
/nodes/n8n-nodes-base.ssetrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.ssetrigger/
/nodes/n8n-nodes-base.ssh/ /integrations/builtin/core-nodes/n8n-nodes-base.ssh/
Expand Down Expand Up @@ -789,8 +794,8 @@
/nodes/n8n-nodes-base.workflowTrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/
/nodes/n8n-nodes-base.workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/
/nodes/n8n-nodes-base.Workflowtrigger/ /integrations/builtin/core-nodes/n8n-nodes-base.workflowtrigger/
/nodes/n8n-nodes-base.writeBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/
/nodes/n8n-nodes-base.writebinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.writebinaryfile/
/nodes/n8n-nodes-base.writeBinaryFile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.writebinaryfile/ /integrations/builtin/core-nodes/n8n-nodes-base.filesreadwrite/
/nodes/n8n-nodes-base.wufooTrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufootrigger/
/nodes/n8n-nodes-base.wufootrigger/ /integrations/builtin/trigger-nodes/n8n-nodes-base.wufootrigger/
/nodes/n8n-nodes-base.xero/ /integrations/builtin/app-nodes/n8n-nodes-base.xero/
Expand Down
43 changes: 2 additions & 41 deletions docs/integrations/builtin/app-nodes/n8n-nodes-base.cortex.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,12 @@ On this page, you'll find a list of operations the Cortex node supports and link
/// note | Credentials
Refer to [Cortex credentials](/integrations/builtin/credentials/cortex/) for guidance on setting up authentication.
///

/// note | Examples and templates
For usage examples and templates to help you get started, take a look at n8n's [Cortex integrations](https://n8n.io/integrations/cortex/){:target="_blank" .external-link} list.
///

## Basic Operations
## Operations

* Analyzer
* Execute Analyzer
Expand All @@ -27,45 +28,5 @@ For usage examples and templates to help you get started, take a look at n8n's [
* Responder
* Execute Responder

## Example Usage

This workflow allows you to analyze a URL and get the job details using the Cortex node. You can also find the [workflow](https://n8n.io/workflows/809) on n8n.io. This example usage workflow would use the following nodes.
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
- [Cortex]()

The final workflow should look like the following image.

![A workflow with the Cortex node](/_images/integrations/builtin/app-nodes/cortex/workflow.png)

### 1. Start node

The start node exists by default when you create a new workflow.

### 2. Cortex node (analyzer: execute)

This node will analyze a URL. If you want to analyze a different observable type, select that instead.

1. First of all, you'll have to enter credentials for the Cortex node. You can find out how to do that [here](/integrations/builtin/credentials/cortex/).
2. Select 'Abuse_Finder_3_0' from the ***Analyzer Type*** dropdown list.
3. Select 'URL' from the ***Observable Type*** dropdown list.
4. Enter the URL you want to analyze in the ***Observable Value*** field.
5. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the node starts the analysis of the URL.

![Using the Cortex node to analyze a URL](/_images/integrations/builtin/app-nodes/cortex/cortex_node.png)

### 3. Cortex1 node (job: get)

This node will return the job details for the analysis that we executed in the previous node.

1. Select the credentials that you entered in the previous node.
2. Select 'Job' from the ***Resource*** dropdown list.
3. Click on the gears icon next to the ***Job ID*** field and click on ***Add Expression***.
4. Select the following in the ***Variable Selector*** section: Nodes > Cortex > Output Data > JSON > _id. You can also add the following expression: `{{$node["Cortex"].json["_id"]}}`.
5. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the node starts the analysis of the URL.

![Using the Cortex node to get job details](/_images/integrations/builtin/app-nodes/cortex/cortex1_node.png)

Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,12 @@ On this page, you'll find a list of operations the Facebook Graph API node suppo
/// note | Credentials
Refer to [Facebook Graph API credentials](/integrations/builtin/credentials/facebookgraph/) for guidance on setting up authentication.
///

/// note | Examples and templates
For usage examples and templates to help you get started, take a look at n8n's [Facebook Graph API integrations](https://n8n.io/integrations/facebook-graph-api/){:target="_blank" .external-link} list.
///

## Basic operations
## Operations

**Default**
- GET
Expand All @@ -44,29 +45,7 @@ For usage examples and templates to help you get started, take a look at n8n's [
* **Node**: The node on which to operate, for example `/<page-id>/feed`. Read more about it in the [official Facebook Developer documentation](https://developers.facebook.com/docs/graph-api/using-graph-api).
* **Edge**: Edge of the node on which to operate. Edges represent collections of objects which are attached to the node.
* **Ignore SSL Issues**: Toggle to still download the response even if SSL certificate validation is not possible.
* **Send Binary Data**: Available for `POST` operations. If enabled binary data is sent as the body. Requires setting the following:
* **Binary Property**: Name of the binary property which contains the data for the file to be uploaded.

## Example usage

This workflow allows you to retrieve the first and last name of a profile on Facebook. You can also find the [workflow](https://n8n.io/workflows/514) on the website. This example usage workflow would use the following two nodes.
- [Start](/integrations/builtin/core-nodes/n8n-nodes-base.start/)
- [Facebook Graph API]()

The final workflow should look like the following image.

![A workflow with the Facebook Graph API node](/_images/integrations/builtin/app-nodes/facebookgraphapi/workflow.png)

### 1. Start node

The start node exists by default when you create a new workflow.

### 2. Facebook Graph API node
* **Send Binary File**: Available for `POST` operations. If enabled binary data is sent as the body. Requires setting the following:
* **Input Binary Field**: Name of the binary property which contains the data for the file to be uploaded.

1. First of all, you'll have to enter credentials for the Facebook Graph API node. You can find out how to do that [here](/integrations/builtin/credentials/facebookgraph/).
2. Enter `me` in the *Node* field.
3. Click on the *Add Option* button and select 'Fields' from the dropdown list.
4. Click on the *Add Field* button and enter `first_name` in the *Name* field.
5. Click on the *Add Field* button and enter `last_name` in the *Name* field.
6. Click on *Execute Node* to run the workflow.

84 changes: 4 additions & 80 deletions docs/integrations/builtin/core-nodes/n8n-nodes-base.compression.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,83 +18,7 @@ For usage examples and templates to help you get started, refer to n8n's [Compre
- **Input Binary Field(s)**: the name of the fields in the input data that contain the binary files you want to compress. To compress more than one file, use a comma-separated list.
- **Output Format**: choose from **Zip** and **Gzip**.
- **File Name**: the name of the zip file you create.
- Options
- ***Binary Property*** field: This field allows you to specify the name of the binary property
- ***Output Prefix*** field: This field allows you to specify a prefix for the name of the file that gets generated. This field gets displayed for the 'Decompress' operation and the 'gzip' output format for the 'Compress' operation
- ***Output Format*** field: This field allows you to select an output format. This field is displayed when 'Compress' gets selected from the ***Operation*** dropdown list. The following are the available formats:
- gzip
- zip
- ***File Name*** field: This field allows you to specify a file name. This field is displayed when 'zip' gets selected from the ***Output Format*** dropdown list.
- ***Binary Property Output*** field: This field allows you to specify a name for the file that gets generated. This field is displayed when 'zip' gets selected from the ***Output Format*** dropdown list.

## Example Usage

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/)
- [Dropbox](/integrations/builtin/app-nodes/n8n-nodes-base.dropbox/)


The final workflow should look like the following image.

![A workflow with the Edit Image node](/_images/integrations/builtin/core-nodes/compression/workflow.png)

### 1. Start node

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.

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.
3. Enter `workflow_image` in the ***Binary Property*** field.
4. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the HTTP Request node fetches the image from the URL. This image gets passed on as binary data to the next node in the workflow.

![Using the HTTP Request node to fetch an image from a URL](/_images/integrations/builtin/core-nodes/compression/httprequest_node.png)

### 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.

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.
3. Enter `logo` in the ***Binary Property*** field.
4. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the HTTP Request node fetches the image from the URL. This image gets passed on as binary data to the next node in the workflow.

![Using the HTTP Request node to fetch an image from a URL](/_images/integrations/builtin/core-nodes/compression/httprequest1_node.png)


### 4. Compression node (compress)

This node compresses the binary file that we received from the HTTP Request nodes in a zip file. If you want to compress them in `gzip` format, select that option instead.

1. Select 'Compress' from the ***Operation*** dropdown list.
2. Enter `logo,workflow_image` in the ***Binary Property*** field.
3. Select 'zip' from the ***Output Format*** dropdown list.
4. Enter `images.zip` in the ***File Name*** field.
5. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the node compresses the files and generates `images.zip`.

![Using the Compression node to compress files](/_images/integrations/builtin/core-nodes/compression/compression_node.png)

### 5. Dropbox node (upload: file)

This node will upload the compressed file to your Dropbox account.

1. First of all, you'll have to enter credentials for the Dropbox node. You can find out how to do that [here](/integrations/builtin/credentials/dropbox/).
2. Enter `/images.zip` in the ***File Path*** field.
3. Toggle ***Binary Data*** to `true`. This option allows us to upload binary data from the previous node.
4. Click on ***Execute Node*** to run the node.

In the screenshot below, you will notice that the node uploads the compressed file that we generated in the previous node.

![Using the Dropbox node to upload a file](/_images/integrations/builtin/core-nodes/compression/dropbox_node.png)

- **Put Output File in Field**: set the name of the field in the output data to contain the file.
- **Operation** > **Decompress**:
- **Put Output File in Field**: set the name of the field in the output data to contain the file.
- **Output Prefix**: add a prefix to the output file name.
Loading

0 comments on commit f6e6daa

Please sign in to comment.