Whise + Ziggu

Whise and Ziggu are connected by Ziggu. We build the connection and we run it, so there is nothing to install in your Whise environment. When a deal is closed in Whise, the project is created in Ziggu and the buyer and the documents on that deal come with it. Inviting the buyer stays a deliberate step your team takes, so nobody sees a portal before it is ready. Whise stays where you run listings and sales. Ziggu is the client portal where everything after the signature happens.

Key takeaways

• Ziggu builds and runs this connection. No plugin in Whise, nothing for your team to maintain.
• A closed deal creates the project in Ziggu automatically.
• The contacts on the deal and the documents attached to it come across with the project.
• The invitation to the buyer is manual, on purpose. Someone checks the portal is ready before the buyer ever sees it.
• The flow runs from Whise into Ziggu. Whise stays the sales record.

Why connect when the deal is already done

Whise ends where a sale ends. For a buyer, that is where the long part starts.

Between the sales agreement and the keys there are eighteen months of choices, invoices, plans, delays and snags, and none of it belongs in a listing platform. Handled by email, it produces the same pattern every time: the buyer asks the agent, the agent asks the office, the office asks the site, and three people spend an afternoon on a question that had a written answer somewhere.

The connection removes the first gap in that chain. The project, the buyer and the paperwork are already in place when the deal closes, so the only thing left is deciding when to open the door.

Why the invitation is a manual step

Everything else here is automatic, and the invitation is not. That is a design decision rather than a gap.

A project that has just been created is empty. If the buyer walked in the moment the deal closed, they would find a portal with nothing in it, which is a worse first impression than no portal at all. Because the invitation is a separate action, somebody on your team looks at what has arrived, adds what is missing and then sends it. One click, at the moment you choose.

Project, unit, and why the difference matters here

In Ziggu a project can be subdivided into phases, lots and buildings, and those carry the units, which are the individual homes. If you sell one property per client, your project and your unit are the same record and you never see the levels in between. A developer selling ninety apartments in one development uses all of them, and each buyer only ever sees their own.

What data moves between Whise 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 Whise to Ziggu?

1. Ask Ziggu for the Whise connection. Because we build and run it, this starts as a conversation rather than an install.
2. Agree what closed means in your process, so the right deals create projects and nothing moves early.
3. Agree the mapping. Which Whise record becomes a Ziggu project, which becomes a unit, and how the buyer reaches the right one.
4. Decide which documents on the deal should reach the buyer, and under which category they appear.
5. Agree who sends the invitation and what has to be in the portal first. That is the moment the buyer's experience actually starts.

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.

Where teams use it

Developers selling through their own agency

Whise carries the listing and the sale, Ziggu carries the two years after it. The buyer meets one system for each phase instead of a series of email threads.

Cutting the questions that reach the agent

Most post-sale questions are not sales questions. When the buyer has a portal, they stop landing with the person who sold them the property.

Running it across a portfolio

Once projects and units exist in Ziggu, everything else attaches to them: documents, decisions, payment schedules, snag lists. See how property developers use Ziggu.

What Whise and Ziggu do not do

• Ziggu is not a listing platform and does not publish to marketplaces. Whise keeps doing that.
• Buyers are not invited automatically. The sync prepares everything; a person decides when the portal opens.
• Nothing is pushed back into Whise. This is a handover, not a two-way sync.
• Ziggu's public API has no webhooks, so anything you build yourself polls on a schedule rather than listening for events.
• Task management and milestones have no endpoint in the public API, so they cannot be read or written from outside Ziggu.
• The API is rate limited to 60 requests per minute across all endpoints, which is what shapes a first load of existing deals.

Questions about the Whise integration

Is there a Ziggu plugin for Whise?

No. Ziggu builds and runs this connection, so there is nothing to install on your side.

What creates the project in Ziggu?

A deal being closed in Whise. What counts as closed is agreed during setup, so it matches your process.

Do the documents on the deal come across?

Yes, together with the project, filed under the category you choose.

Does the buyer get invited automatically?

No, and that is deliberate. The connection creates the project and attaches the buyer; someone on your team sends the invitation once they have checked the portal is ready to be seen.

Does the buyer need a Whise account?

No. Buyers only ever see Ziggu.

What if a deal closes but the project should not start yet?

Then closed is the wrong trigger for you. Agree a different condition during setup rather than letting the pipeline decide.

Last verified: 28 August 2026.