Integrations

Publish from n8n

Publish pages, files and whole sites from any n8n workflow.

The Droply Host node for n8n (package n8n-nodes-droply) creates and updates sites, publishes new versions, saves drafts, rolls back and sets passwords and expiry, all from a workflow. It runs on the same public API as every other integration.

Before you start

API access is included on Pro and higher plans.
An n8n instance, self-hosted or on n8n Cloud.

Install

In n8n, open Settings > Community Nodes and choose Install.
Enter n8n-nodes-droply and confirm.

On n8n Cloud, search for Droply Host in the nodes panel. The node is rolling out there: if you don't see it yet, write to [email protected].

Connect

Create a token under API tokens. Tokens made there have Full access, which settings, deleting, drafts and rollback need. Copy it now: it is shown only once.
In n8n, add a Droply API credential and paste the token. Leave the Base URL as it is: we will never ask you to change it. n8n checks the token straight away.

What you can do

Sites: create a site, or create or update the one with a given subdomain (served at <subdomain>.droply.id), publish a new version, change its name, password or expiry, check a subdomain, list, get and delete sites. A site in a space protected against accidental deletion is deleted from the dashboard only.
Versions: save a version as a draft, publish a draft, roll back to the previous version, retry a failed one, and list a site's versions.
Waiting: by default the node waits until the version is live and returns its address and status, so the next step can use a link that already works.

Publishing several files

Choose Multiple Files as the source to publish several files as one site: the node packs them into a ZIP and sends that. It publishes every file on the item, or only the fields you list. To gather files from several items first, put an Aggregate node with Include Binaries in front of it. Name the home page index.html. A single file is published as it is, and its extension decides how it is served: a .zip becomes a whole site, .html a page, .pdf a document.

Use it as an AI agent tool

Attach the node to an n8n AI Agent as a tool, with HTML as the source, and let the model write the page with $fromAI(). Choose the site yourself in the node: a chat can carry instructions written by someone else, and a model free to pick the subdomain could be talked into publishing over any site in your account. If the model must pick the name, use Create, which never touches an existing site. On self-hosted n8n, set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true first. Don't hand an agent the delete operation.

Example workflows

An AI-written page, live in one step: an AI Agent writes the HTML, the node publishes it to a fixed subdomain with Create or Update, and an email sends the link.
Publish when a ZIP lands in Google Drive: the Google Drive trigger fires, the file is downloaded, and the node publishes it to the same site.
Review before it goes live: the node saves a draft, Slack asks for approval, and the node publishes that exact draft, by the deployment ID the first step returned, once someone approves.

Limits

One upload can be at most 100 MB. HTML sent as text can be at most 12 MB; the node sends a larger page as a file by itself.
Each token can make 60 requests a minute, and 5 versions can be processing at once. Publishing drafts and rolling back are limited to 30 an hour. When Droply asks it to slow down, the node waits and tries again.
Your plan's storage and number of sites apply as they do in the dashboard.

Notes

Passwords come first. When you set a password while creating a site, it is in place before anything is uploaded, so the content is never public without it.
Keep your token secret. Anyone with it can publish to your account. Revoke it any time under API tokens.