LeafprintWebhooks
Send records where your team already works
A portal is useful only if people open it. Webhooks let Leafprint pass records to a system you control, so the information can reach your team's existing workflow.
What a webhook does
A webhook is an automatic message from one system to another. When there is a record to share, Leafprint can send it to a web address you provide. Your system receives it and decides what happens next, such as creating a task for review.
The example here is illustrative. Your portal shows the actual setup and the fields available to your account.
A simple example
This illustrative payload shows the idea. Your portal shows the actual fields available to your account.
POST https://your-system.example/leafprint
{
"event": "visitor.identified",
"profile": "sample-profile-id",
"email": "sample@example.com",
"pages": ["/menu", "/deals"]
}What teams build with webhooks
- A review queue. Send new profiles to a spreadsheet or internal tool, where someone checks them before any action is taken.
- Sales alerts. Notify a rep when a company they care about shows up on the site.
- Your data warehouse. Store records beside your other marketing data for reporting.
- An automation tool. Route records through a workflow tool you already pay for, if it accepts incoming webhooks.
Safeguards to build in
Webhooks move personal information automatically, so set them up with some care. Point them only at systems your business controls or has vetted. Use a secure HTTPS address. Limit who can see the incoming data, and keep records only as long as you have a reason to.
Most importantly, do not wire a webhook directly to your text or email sending tool. That is the fastest way to contact people who never gave you permission. Put a consent check between identification and outreach. For texts, that check should confirm written consent you collected yourself, as explained in our article on SMS consent.
Remember to carry opt-outs across too. If someone asks you to stop using their data or delete it, that request has to reach every system you sent the record to. Plan for this at setup, while the list of destinations is still short.
What you will need
You need a destination that can accept an incoming web request, plus someone comfortable testing it. That may be a developer, or a marketer who is familiar with an automation tool. Send a test record first, confirm the fields look right, and only then rely on the connection.
Do you need webhooks at all?
Not always. A small retail team may do fine by checking the portal each week. Webhooks start to pay off when more than one person needs the information, or when you want records in one place alongside other data. Start simple and add them when the manual routine begins to feel like a bottleneck. See what to do with identified visitors for ideas.
Common questions
Do I need a developer to use webhooks?
Not always. An automation tool that accepts incoming webhooks can often do the job. Either way, someone should test the connection with a sample record before you rely on it.
Can I connect webhooks to my SMS platform?
We advise against a direct connection. A matched number is not consent, so add a step that checks for written consent you collected yourself before anything is sent.
What happens to data after it leaves Leafprint?
It becomes your responsibility inside your own systems. Limit access, set a retention period, and make sure opt-out and deletion requests reach every destination.
See it on your own traffic
We will walk through the portal, the pixel, and how consent works, then answer questions about your stores and systems.