Actions15
Overview
This node integrates with the DatoCMS API to manage file uploads. Specifically, the "Upload" resource with the "Get" operation retrieves details about a single upload by its unique ID. This is useful when you want to fetch metadata or information about a previously uploaded file in your DatoCMS project.
Common scenarios include:
- Retrieving file details for use in subsequent workflow steps.
- Verifying upload existence or properties before processing.
- Integrating DatoCMS media assets into other systems by fetching their metadata.
Example: You have an upload ID from a previous step or external source and want to get its filename, URL, size, or other metadata to display or process further.
Properties
| Name | Meaning |
|---|---|
| Upload ID | The unique identifier of the upload to retrieve. This is required to specify which upload's details to fetch. |
Output
The output JSON contains the full details of the requested upload as returned by the DatoCMS API. This typically includes fields such as:
id: The upload's unique ID.filename: The name of the uploaded file.url: The publicly accessible URL of the file.size: File size in bytes.mime_type: The MIME type of the file.upload_collection: (optional) Information about the collection the upload belongs to.- Other metadata related to the upload.
No binary data is output for this operation; it only returns JSON metadata describing the upload.
Dependencies
- Requires an API authentication token credential for DatoCMS.
- The node uses the official DatoCMS Node.js client library internally.
- No additional environment variables are needed beyond the configured API key credential.
Troubleshooting
- Error: "Upload ID is required" — Ensure that the "Upload ID" property is set and not empty.
- Error: "Failed to find upload" or similar API errors — Verify that the provided Upload ID exists in your DatoCMS project and that the API token has sufficient permissions to access uploads.
- Permission issues — If the API token lacks rights to read uploads, the node will fail. Check your DatoCMS API token scopes.
- Network or connectivity errors — Confirm that n8n can reach the DatoCMS API endpoint without firewall or proxy issues.