Salesforce + Ziggu

Salesforce and Ziggu are connected by an integration Ziggu builds and runs. It checks for changes every hour and performs a full sync once a day, so accounts, contacts, projects and the documents that belong to them arrive in Ziggu without anyone retyping them. Salesforce stays your single source of truth. Ziggu is where your clients see the part that concerns them, in a client portal that carries your branding rather than your CRM.

Key takeaways

• Ziggu builds and operates this connection. It is not a template you deploy or an app you install.
• There is nothing for your Salesforce administrator to install. No managed package, no app in your org.
• Incremental sync every hour, full sync once a day.
• Synced data is read-only in Ziggu by default, so nobody can quietly diverge from Salesforce. You can switch that off if you want Ziggu to be editable.
• Inviting the client stays a deliberate step your team takes, so nobody sees a portal before it is ready.
• ION and Nextensa run this connection today.

Why read-only is the default

The failure mode of any CRM integration is two systems that both look authoritative and disagree. Someone corrects an address in the portal, someone else corrects it in Salesforce, and a month later nobody knows which one the invoice went to.

So Ziggu locks the fields it receives. Salesforce is where the record is maintained, and Ziggu shows it. If that does not suit how you work, the lock comes off and Ziggu becomes editable. That is a decision you make deliberately at setup rather than one you discover later.

ION described the point of it plainly in their own story: the connection was created to avoid having to enter client information twice. See how ION works with Ziggu.

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. If you deliver many inside one project, you use all of them. This is what makes the mapping the real work of the setup: it is where your Salesforce objects have to line up with the shape of your own delivery.

What data moves between Salesforce and Ziggu

The first column is the name your team knows from the app, the second is the endpoint the integration writes to.

‍

These fields are read-only in Ziggu unless you ask for the lock to be removed.

How do you connect Salesforce to Ziggu?

Shorter than you expect, because Ziggu does the building.

1. Tell your Ziggu contact you want the Salesforce connection.
2. Agree the mapping: which Salesforce objects and fields correspond to projects, units, companies and contacts on your side. This is the only part that takes real thought, and it is where a project with many units earns its complexity.
3. Give Ziggu access to your Salesforce org.
4. Ziggu builds, tests on a single project, and turns on the hourly schedule.
5. Agree who sends the client invitations, and what has to be in a portal before it is opened.

Your Salesforce administrator installs nothing. If you would rather build against the API yourself or have your own partner do it, that route is open too: see the Ziggu API documentation.

Why the invitation is a separate step

The sync is automatic and the invitation is not, on purpose. A project that has just been created is empty, and a client who walks into an empty portal has a worse first impression than one who has not been invited yet. Because inviting is a separate action, somebody checks what arrived, adds what is missing, and then opens the door.

Where teams use it

Selling in Salesforce and delivering in Ziggu

Sales works the way it always has. The moment a client is recorded against a unit in Salesforce they exist in Ziggu, so the customer care team can invite them without copying an email address out of a CRM screen.

Running hundreds of clients without a data entry team

A development with three hundred apartments has three hundred clients, each with contact details that change, and the same is true of any business where the client list is long and never stands still. Hourly syncing means nobody maintains that list twice. See how property developers use Ziggu.

Keeping the CRM clean

Because Ziggu is read-only by default, the portal cannot become a second version of the truth. Your Salesforce data stays the record, which is usually the reason a company with a mature CRM was hesitant about a portal in the first place.

What Salesforce and Ziggu do not do

• The sync is hourly, not instant. A change made in Salesforce at ten past the hour reaches Ziggu on the next run.
• Clients are not invited automatically. The connection prepares everything; a person decides when the portal opens.
• Data flows from Salesforce to Ziggu. This connection does not write client activity back into Salesforce.
• Synced fields are read-only in Ziggu by default. If your team expects to edit them in the portal, say so at setup.
• The mapping is agreed per customer. Two Salesforce orgs are never laid out the same way, so the table above is the shape of the connection rather than a fixed field list.
• Ziggu's API is rate limited to 60 requests per minute across all endpoints, which is what shapes the first full load.

Questions about the Salesforce integration

Do we have to install anything in Salesforce?

No. No managed package, nothing in your org. Ziggu builds and runs the connection.

How often does it sync?

Incrementally every hour, with a full sync once a day.

Does the client get invited automatically?

No, and that is deliberate. The sync creates the project and attaches the client; someone on your team sends the invitation once the portal is ready to be seen.

Can our team edit synced data in Ziggu?

Not by default. Synced fields are read-only so Salesforce stays the single source of truth. That lock can be removed if you want it.

Does anything flow back into Salesforce?

Not in this connection. It moves data from Salesforce into Ziggu.

Who is running this today?

ION and Nextensa, both property developers running projects with many units.

We use a different CRM.

The same approach applies to HubSpot, Dynamics 365, Teamleader Focus and Zoho, on their own routes.

Last verified: 28 August 2026.