Nextcloud + Ziggu

Nextcloud and Ziggu are connected by Ziggu. We build the connection and we run it. You keep working the way you already work, dropping files into folders, and the ones that belong to a client appear in that client's portal under the right category. Nextcloud stays your drive. Ziggu is the client portal, and no client ever gets a login to your storage.

Key takeaways

• Ziggu builds and runs this connection. There is no Nextcloud app to install and no script to maintain.
• The folder structure is the configuration. A folder per project, subfolders that match your document categories in Ziggu.
• Uploading the file is the whole action. Nothing else has to happen for the client to receive it.
• You choose how often it syncs. Near real time or batched, whichever suits how your team works.
• Clients are notified when a document arrives, and see only the documents that belong to them.

Why connect when you can just send a link

A share link works once. It works badly for two years.

Internal folders are organised for the people who made them: working versions, superseded drawings, files that concern a different client, notes that were never meant to leave the office. Sending a link means either tidying a folder for every send, or trusting that nobody clicks one level up.

Neither is a system. The point of the connection is that the folder stays yours, messy and internal, and only what belongs to a client crosses the line, into a place where it is filed by category and stays findable years later.

Project, unit, and why the difference matters here

Ziggu organises work as projects, and a project can hold one unit or hundreds. A unit is the smallest thing a single client has: one apartment in a development, one house, one fit-out, one order. Between project and unit sit optional levels, phases and lots and buildings, which large projects use and small ones never see.

If you run one job per client, your project and your unit are the same record and those levels stay invisible. Your Nextcloud structure mirrors whichever of the two you actually work with, which is why the folder conversation is worth having before you start.

What data moves between Nextcloud and Ziggu

The first column is the name your team knows from the app. The second is the endpoint a developer would call if you ever wanted to extend this on Ziggu's public API.

‍

How do you connect Nextcloud to Ziggu?

1. Ask Ziggu for the Nextcloud connection. Because we build and run it, this starts as a conversation rather than an install.
2. Create a folder per project in Nextcloud.
3. Inside it, create subfolders that match the document categories you use in Ziggu.
4. Decide how often the sync should run, from near real time to a daily batch.
5. Upload one file, look at what the client sees, then let your team carry on uploading as usual.

If you would rather build or extend it yourself, the same endpoints are available on Ziggu's public REST API. Endpoint reference: Ziggu API documentation.

Why the folder structure is the whole design

Most document integrations fail on adoption, not on technology. If sharing a file with a client requires opening a second tool, someone will skip it on a busy Thursday and the portal quietly goes stale.

Here the action a person has to remember is one they already do. Put the file in the right folder. The category is the folder name, the project is the parent, and the client is notified without anybody deciding to notify them. That is why the structure is worth ten minutes of thought at setup: it is the interface.

Where teams use it

Keeping internal folders internal

Your drive holds working versions, other clients and things nobody outside should see. Only what sits in a synced subfolder ever crosses.

Documents clients keep asking for

The file a client wants at the end of a project is the one they were sent fourteen months ago. In their portal it is still there, under the category it belongs to.

Running it across a portfolio

Once documents attach to projects and units, so does everything else: decisions, reports, payment schedules. See how property developers use Ziggu.

What Nextcloud and Ziggu do not do

• This is a document connection. It does not create projects or clients in Ziggu; those come from your CRM or from Ziggu itself. If you want deals to become projects, see HubSpot and Ziggu or Salesforce and Ziggu.
• Clients never get access to Nextcloud. They see documents in Ziggu, not folders in your drive.
• Documents flow from Nextcloud into Ziggu. If you need files to travel the other way, that is a build on the public API rather than part of this connection.
• Ziggu's public API has no webhooks, so anything you build yourself polls on a schedule rather than listening for events.
• The API is rate limited to 60 requests per minute across all endpoints, which is what shapes a first load of an existing archive.

Questions about the Nextcloud integration

Do clients get a Nextcloud login?

No, and that is the point. They only ever see their own documents in Ziggu.

How does a file end up in the right category?

By the subfolder it sits in. The subfolder names match your document categories in Ziggu.

How often does it sync?

As often as you want it to. You set the frequency during setup, from near real time to a daily batch.

What happens if someone uploads to the wrong folder?

It arrives under the wrong category, exactly as it would in your own drive. The structure is the control, so it is worth agreeing on before you start.

Does the client get notified?

Yes, by email or in the app when a new document is available.

Can we sync only part of a project folder?

Yes. Only the subfolders you map are synced. Anything outside them stays internal.

Last verified: 28 August 2026.