Does this replace Sunbase?

No. Sunbase is a separate CRM card. PISA is the project system (create + sold webhook), typically next to GHL for the contact record.

What if create succeeds in PISA but Niche doesn't save the id?

We don't auto-repost. PISA may already have the project. Ops reconcilies from logs rather than duplicating.

Who can call the inbound webhook?

Callers with the shared bearer secret (or IP allowlist if that's how the PISA side prefers to auth). It's not a per-user OAuth card.

All integrations

PISA

CRM

GHL contact in. Project in PISA.

Solar ops running PISA (including SolUp) get a workflow node that creates the project on your PISA instance, plus an inbound webhook when that project sells — revenue and purchase date written back.

Book Demo Start Free Trial

What syncs, and when

No CSVs. No nightly cron.

Live, bidirectional, idempotent. Niche reads what it needs from PISA and writes back at the right moment in the conversation.

What

Direction

When

Project create (from live GHL contact) Out push_to_pisa workflow node
Sold status + revenue In PISA webhook
Purchase date In PISA webhook
GHL deal/status reflection Out After inbound sold update

What it actually does

Five things only happen when Niche talks to PISA.

Your instance URL, not a shared env

Each business stores its PISA base URL (https only) plus supplier login. No config means no post — Niche will not write into another tenant's PISA.

Create once

The create POST is treated as the exposed boundary: PISA may commit even if our follow-up write fails. The node does not blindly retry a create.

Sold comes back on a webhook

PISA POSTs project updates to Niche (sold, revenue, purchaseDate). Niche updates the project row and reflects sold + revenue onto the linked GHL contact/deal.

Email + EnergyConsultant required

PISA's create spec requires Email and EnergyConsultant. The node no-ops with a clear miss if those fields aren't on the live GHL contact yet.

Setup

Live in 30 minutes.

Step 01
Store instance + supplier creds

Per-business PISA URL and login. Self-hosted instances are fine as long as the URL is public https.
Step 02
Drop push_to_pisa on the workflow

Place it after the GHL contact has email and energy consultant. The node reads the live GHL contact, not a stale sync row.
Step 03
Point PISA at the webhook

PISA has no self-serve webhook UI — their team POSTs to Niche with a bearer secret we issue.

Popular with

Shops on PISA that run on Niche.

Solar

Solar leads don't wait — the first company to answer wins the site visit. Niche picks up in under a second, qualifies roof + bill + co-homeowner, and books the consultation in Sunbase — showroom or in-home, 2-hour window and all.

FAQ

Questions people on PISA ask.

Does this replace Sunbase?

No. Sunbase is a separate CRM card. PISA is the project system (create + sold webhook), typically next to GHL for the contact record.
What if create succeeds in PISA but Niche doesn't save the id?

We don't auto-repost. PISA may already have the project. Ops reconcilies from logs rather than duplicating.
Who can call the inbound webhook?

Callers with the shared bearer secret (or IP allowlist if that's how the PISA side prefers to auth). It's not a per-user OAuth card.