Node reference
File storage & doc generation
5 nodes in the File storage & doc generation category - what each one does and which credential it needs.
5 nodes in this category. Every entry below is generated straight from the node catalog and wiring manifests, so it never drifts from what the node panel actually ships. See Credentials for how per-node credentials work.
| Node | Description | Credential |
|---|---|---|
| AWS S3 | Calls the Amazon S3 REST API with an IAM access key across 47 operations, signed with SigV4. Objects: upload from text or base64 (with content type, cache headers, storage class, encryption, custom metadata and tags), download as text or base64 with byte ranges and conditional requests, head, get attributes, server-side copy, delete one key or one version, delete up to 1000 in a single batch, list a prefix with delimiters and continuation tokens, list every version, and restore from Glacier. Presigned URLs perform GET, PUT, HEAD or DELETE - so a workflow can hand someone an UPLOAD link, not only a download link - capped at SigV4's seven-day ceiling. Also object tags, ACLs, Object Lock retention and legal holds, the four S3 Annotations operations that attach model output to an object, the full multipart family for large files, bucket create/delete/list/head/location/versioning/tagging, and bucket CORS, lifecycle and default-encryption configuration. An object key containing a . or .. segment is refused rather than silently normalized onto a different object, and every XML request body escapes the values it carries. A custom endpoint on the credential points the same node at S3-compatible storage such as MinIO, Wasabi, DigitalOcean Spaces or Backblaze B2. No trigger node: S3 event notifications can only be delivered to SNS, SQS, Lambda or EventBridge, never to an arbitrary HTTPS callback. 47 operations - see the full reference. | AWS IAM access key (accessKeyId, secretAccessKey, region, bucket) |
| Cloudflare R2 | Calls Cloudflare R2 through its S3-compatible API at ACCOUNT_ID.r2.cloudflarestorage.com with an R2 API token, across 26 operations signed with SigV4 against the auto region and addressed path-style. Runs on the same engine as the AWS S3 node, so the object surface matches: upload from text or base64 with content type, cache headers, storage class and custom metadata; download as text or base64 with byte ranges and conditional requests; server-side copy, including Cloudflare's MERGE metadata directive, which keeps the source's metadata while adding new keys and has no S3 equivalent; delete one key or up to 1000 in a single batch; list a prefix with delimiters and continuation tokens; the full multipart family for large files; and bucket create/delete/list/head/location plus CORS, lifecycle and default-encryption configuration. Presigned URLs perform GET, PUT, HEAD or DELETE for 1 second to 7 days, so a workflow can hand someone an UPLOAD link, not only a download link - and Set CORS rules is the other half of that, because a browser cannot use a presigned PUT until a rule allows its origin. An object key containing a . or .. segment is refused rather than silently normalized: because R2 is addressed path-style, such a key reached a DIFFERENT BUCKET under the same credential, not merely a different prefix. R2 implements a subset of S3 - no ACLs, no object tagging, no versioning, no Object Lock, no SSE-KMS and no archive tier - so those operations are declined by name rather than offered and left to fail at run time. No trigger node: R2 event notifications are delivered to a queue or a Worker, not to an arbitrary HTTPS callback. 26 operations - see the full reference. | Cloudflare R2 API token (accountId, accessKeyId, secretAccessKey, bucket) |
| Cloudinary | Cloudinary integration (Files & docs). 149 operations across the Upload API (upload, rename, destroy, explicit, explode, archives, animations, text images, tags, context and structured metadata), the Admin API (browse, search and visual search, asset detail and update, restore and bulk delete, derived assets, related assets, folders and folder access, transformations, upload presets and mappings, streaming profiles, structured metadata fields and rules, AI people, notification triggers, usage, config and last-access reports), the Analyze API, live streaming, video player profiles and analytics, video canvas, image generation and creative approval. 149 operations - see the full reference. | Cloudinary API credentials |
| PDFMonkey | createAndPollDocument. Operations: createAndPollDocument. | PDFMonkey API key |
| PDFShift | convertToPdf. Operations: convertToPdf. | PDFShift API key |