n8n-nodes-publitio
v0.1.0
Published
n8n community node for the Publitio media hosting & delivery API (upload, folders, conversions, watermarks, players)
Maintainers
Readme
n8n-nodes-publitio
This is an n8n community node for Publitio, a media hosting, storage and delivery API for images, videos, audio and other files. It lets you upload, transform, organize and manage media directly from your n8n workflows.
n8n is a fair-code licensed workflow automation platform.
Installation Credentials Resources and operations Usage examples Compatibility Resources License
Installation
Community Nodes (recommended)
In n8n, go to Settings → Community Nodes, click Install, and enter the package name:
n8n-nodes-publitioThis requires a self-hosted n8n instance running n8n version 1.x or later — community nodes are not available on n8n Cloud.
Manual installation
Install the package into n8n's community nodes folder (the same location the
GUI installer uses — do not use ~/.n8n/custom, which registers nodes under a
generic CUSTOM.* type name instead of the package name):
mkdir -p ~/.n8n/nodes
cd ~/.n8n/nodes
npm install n8n-nodes-publitioRestart n8n afterwards so the new node is picked up.
Credentials
Create a Publitio API credential in n8n. You will need an account at dashboard.publit.io and API access enabled under the API Keys section of the dashboard.
Two authentication methods are supported:
- Bearer Token — a personal access token generated from the Publitio Dashboard. Simplest option for a single account.
- API Key + Secret (Signature) — the API Key and API Secret pair from the dashboard. The node signs each request with a SHA-1 signature (timestamp + nonce + secret) as required by the Publitio API.
Select the authentication method on the credential and fill in the corresponding field(s). Use the Test button on the credential to verify it against the Publitio /files/list endpoint before using it in a workflow.
Resources and operations
The node supports 8 resources:
| Resource | Operations | | --- | --- | | File | Upload, Get, List, Update, Replace, Delete, Download, Apply Preset, Get Player Embed, Multi-File Download, Update Multiple Metadata | | Folder | Create, Get, List, Get Tree, Update, Delete, Get Share URL, Update Share Settings | | Version | Create, Get, List, Update, Delete, Reconvert | | Subtitle | Create, List, Update, Delete | | Watermark | Create, Get, List, Update, Delete | | Player | Create, Get, List, Update, Delete | | Ad Tag | Create, Get, List, Update, Delete | | Stat | Get for File, Get for Multiple Files |
Notes:
- Stats are video-only — Publitio returns a 403 error if you request stats for a non-video file.
- Multi-File Download is asynchronous: the initial call starts the ZIP archive job, and you need to repeat the call (poll) until the archive is ready before you get a download URL back.
- Folder-picker fields throughout the node are populated dynamically from your Publitio account via a "Folders" dropdown (including a "Root (No Folder)" option).
Usage examples
Upload a file (binary data)
- Add a node earlier in the workflow that produces binary data on the item (e.g. Read Binary File, an HTTP download, etc.).
- Add a Publitio node, set Resource to
Fileand Operation toUpload. - Set Upload Source to
Binary Dataand point Binary Property at the property containing the file (defaultdata). - Optionally set a Title, Folder (via the dynamic dropdown), Privacy, and Tags in the additional fields.
Upload a file (remote URL)
- Add a Publitio node, set Resource to
Fileand Operation toUpload. - Set Upload Source to
Remote URLand provide the public URL Publitio should fetch. - Publitio downloads and ingests the file server-side — no binary data needs to pass through n8n.
Download a file with on-the-fly transformations
- Add a Publitio node, set Resource to
Fileand Operation toDownload. - Provide the File ID (or public ID) of an existing file.
- In the transformation options, set fields such as Width, Height, Crop Mode, Quality or Grayscale. The node builds the Publitio transformation string (e.g.
w_300,h_200,c_fill) and returns the transformed file as binary data on the output item.
Compatibility
Requires a self-hosted n8n instance on n8n version 1.x or later (community nodes require self-hosted n8n and are not supported on n8n Cloud).
