mirror of
https://github.com/n8n-io/n8n-docs.git
synced 2025-11-20 17:48:34 +00:00
S3 node documentation (#190)
* ⚡ Basic docs * ✨ S3 node documentation * 🐛 Minor Fixes * 🔨 Workflow Update
This commit is contained in:
parent
2f6c267fbd
commit
0afccd2afd
17
docs/nodes/credentials/S3/README.md
Normal file
17
docs/nodes/credentials/S3/README.md
Normal file
@ -0,0 +1,17 @@
|
||||
---
|
||||
permalink: /credentials/s3
|
||||
---
|
||||
|
||||
# S3
|
||||
|
||||
You can find information about the operations supported by the S3 node on the [integrations](https://n8n.io/integrations/n8n-nodes-base.se) page. You can also browse the source code of the node on [GitHub](https://github.com/n8n-io/n8n/tree/master/packages/nodes-base/nodes/S3).
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Create an account on S3 compatible server.
|
||||
|
||||
## Using Access Token
|
||||
|
||||
1. Retrieve your S3 endpoint, access key ID, and secret access key from your S3 compatible server.
|
||||
2. Use the S3 endpoint, access key ID, and the secret access key in your S3 node credentials in n8n.
|
||||
3. Click on the ***Save*** button to save your credentials.
|
||||
BIN
docs/nodes/nodes-library/nodes/S3/HTTPRequest_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/S3/HTTPRequest_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 166 KiB |
78
docs/nodes/nodes-library/nodes/S3/README.md
Normal file
78
docs/nodes/nodes-library/nodes/S3/README.md
Normal file
@ -0,0 +1,78 @@
|
||||
---
|
||||
permalink: /nodes/n8n-nodes-base.s3
|
||||
---
|
||||
|
||||
# S3
|
||||
|
||||
S3 is an object storage service that allows you to block public access to all of your objects at the bucket or the account level with S3 Block Public Access. S3 maintains compliance programs, such as PCI-DSS, HIPAA/HITECH, FedRAMP, EU Data Protection Directive, and FISMA, to help you meet regulatory requirements.
|
||||
|
||||
::: tip 🔑 Credentials
|
||||
You can find authentication information for this node [here](../../../credentials/S3/README.md).
|
||||
:::
|
||||
|
||||
## Basic Operations
|
||||
|
||||
- Bucket
|
||||
- Create a bucket
|
||||
- Get all buckets
|
||||
- Search within a bucket
|
||||
- File
|
||||
- Copy a file
|
||||
- Delete a file
|
||||
- Download a file
|
||||
- Get all files
|
||||
- Upload a file
|
||||
- Folder
|
||||
- Create a folder
|
||||
- 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](../../core-nodes/ReadBinaryFile/README.md) node or the [HTTP Request](../../core-nodes/HTTPRequest/README.md) 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](../../core-nodes/Start/README.md)
|
||||
- [HTTP Request](../../core-nodes/HTTPRequest/README.md)
|
||||
- [S3]()
|
||||
|
||||
The final workflow should look like the following image.
|
||||
|
||||

|
||||
|
||||
### 1. Start node
|
||||
|
||||
The start node exists by default when you create a new workflow.
|
||||
|
||||
|
||||
### 2. HTTP Request node (GET)
|
||||
|
||||
1. Enter the URL of the file in the ***URL*** field.
|
||||
2. Select 'File' from the ***Response Format*** field.
|
||||
3. Click on ***Execute Node*** to run the node.
|
||||
|
||||

|
||||
|
||||
|
||||
### 3. S3 node (upload: file)
|
||||
|
||||
1. First of all, you'll have to enter credentials for the S3 node. You can find out how to do that [here](../../../credentials/S3/README.md).
|
||||
2. Select 'Upload' from the ***Operation*** dropdown list.
|
||||
3. Enter the bucket name in the ***Bucket Name*** field.
|
||||
4. Click on the gears icon next to the ***File Name*** field and click on ***Add Expression***.
|
||||
::: v-pre
|
||||
5. Select the following in the ***Variable Selector*** section: Nodes > HTTP Request > Output Data > Binary > data > fileName. You can also add the following expression: `{{$node["HTTP Request"].binary.data.fileName}}`
|
||||
6. Click on ***Execute Node*** to run the node.
|
||||
:::
|
||||
|
||||

|
||||
|
||||
### 4. S node (getAll: file)
|
||||
|
||||
1. Select the credentials that you entered in the previous node.
|
||||
2. Select 'Get All' from the ***Operation*** dropdown list.
|
||||
3. Enter the bucket name in the ***Bucket Name*** field.
|
||||
4. Toggle ***Return All*** to true.
|
||||
5. Click on ***Execute Node*** to run the node.
|
||||
|
||||

|
||||
BIN
docs/nodes/nodes-library/nodes/S3/S3_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/S3/S3_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 134 KiB |
BIN
docs/nodes/nodes-library/nodes/S3/S_node.png
Normal file
BIN
docs/nodes/nodes-library/nodes/S3/S_node.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
BIN
docs/nodes/nodes-library/nodes/S3/workflow.png
Normal file
BIN
docs/nodes/nodes-library/nodes/S3/workflow.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 155 KiB |
Loading…
Reference in New Issue
Block a user