Integration · Webhooks

Carelu + webhooks: every record, delivered to any system you run.

Not every system has a logo on an integrations page, and it shouldn't have to. Carelu sends every lead, stage change, or completed intake as JSON to any HTTPS endpoint you give it — a custom EHR, an internal database, a data warehouse, or a vendor with an API. The payload is mapped to the fields your system expects, every delivery is logged, and protected health information goes directly from Carelu to you.

What Webhooks does

A webhook is an HTTPS endpoint your system exposes to receive data as events happen. Most modern platforms, in-house tools, and integration layers can accept one.

What Carelu adds

Carelu adds the event stream and the mapping: choose which events to send, map intake fields to your payload with placeholders, and review a delivery history with the response your system returned. It is built for HIPAA — PHI travels directly to your endpoint under a BAA, with no consumer automation tool in between.

How it works together

1

Choose the events

New lead, stage change, completed intake, or all of them — per campaign or across the practice.

2

Map the payload

Intake fields — family, child, insurance, documents, consents, source, stage — placed into the JSON shape your system expects.

3

Carelu delivers

Each event is posted to your endpoint as it happens, with a full record of the request and the response.

4

You see every delivery

A delivery history shows what was sent, when, and what your system answered — so integration issues are visible, not silent.

One funnel, clear lanes

Answering, qualifying, verifying & collecting documentsCarelu
Mapping fields and delivering each event with historyCarelu
Keeping PHI on a direct, BAA-covered pathCarelu
Receiving the record and acting on itYour system

Third-party capabilities summarized at category level from public information — verify specifics with the vendor.

Common questions

Why not Zapier or Make?

Consumer automation tools sit in the middle of the data path and are rarely covered by a BAA, which makes them a poor place for protected health information. Carelu posts directly to your endpoint instead. Read more on our Zapier and Make HIPAA risk page.

What does the payload contain?

Whatever you map: family and child details, insurance and verification results, uploaded documents, consent records, lead source and campaign, and intake stage. Placeholders put each field where your system expects it.

What if our system rejects a delivery?

The response is recorded in the delivery history — status and body — so your team or ours can see exactly what the receiving system said and fix the mapping.

Your platform, plus a front office that never sleeps.

Tell us what your system expects and see a completed intake arrive in it.

Get a Demo