Virtual Try-On Webhook: Send Every Lead to Any CRM, Securely

Most apps hand you a CSV and call it an integration. That is fine for a one-time import, but it is not how modern marketing runs. You want a shopper's try-on to reach your CRM within seconds, so your flows fire while intent is still hot. That is what a webhook is for: the instant a shopper completes a try-on and shares their email, TryOnCloud sends a signed HTTP request to your endpoint with the lead and the product they tried. No polling, no export, no delay.

What the Webhook Integration Does

TryOnCloud's outbound webhook turns every captured try-on lead into a real-time event delivered to a URL you control. You connect it once from the Leads tab inside your Shopify admin, and from then on every lead is pushed to your endpoint automatically. Because it is a plain, signed HTTP POST, it works with any system on the planet that can receive a request, which means you are never locked into one marketing tool.

Which CRMs and Tools You Can Connect

The webhook is intentionally generic. If your platform exposes an inbound webhook URL, or connects through an automation hub like Zapier or Make, TryOnCloud can deliver to it. Merchants commonly route try-on leads into these tools:

For Klaviyo specifically, TryOnCloud offers a dedicated one-click integration that sends a native "Try-On Lead" event, covered in our Klaviyo integration guide. For everything else, the webhook is the universal connector. And if you prefer a bulk import, a CSV export of every lead is always available from the Leads tab.

How It Works, End to End

What Each Webhook Contains

Every delivery carries a small, signed JSON body and a set of headers your endpoint uses to verify and process it. The headers are the important part:

The JSON body itself is deliberately minimal: the shopper's email, the product they tried (title and URL), the result context, and whether they were tagged in Shopify. No payment data, no uploaded photo, nothing sensitive beyond the email the shopper chose to share.

Webhook Security, Explained for Your Engineers

A webhook gives an external system a way to push data to you, so it has to be secured properly. This is the part a serious merchant's security team will scrutinize, and TryOnCloud is built to pass that review. Here is every control, with the plain-language reason it matters.

Guaranteed Delivery and Retries

The most common reason teams distrust webhooks is silent loss: the sender fires once, your endpoint hiccups, and the event is gone. TryOnCloud removes that failure mode entirely with a durable outbox pattern, the same approach large payment systems use.

• Persist first, deliver second. The event is written to a durable queue before any network call, so a crash or outage cannot drop it.
• Exponential backoff. If your endpoint is down or returns an error, retries are spaced out over hours: 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours, then 24 hours.
• At-least-once, with dedupe. Delivery is guaranteed at least once. If a retry overlaps a slow success, dedupe on x-tryoncloud-delivery-id so you process each lead exactly once.
• Per-event logging. Each attempt records status, count, and last error, so you can see exactly what happened.

How to Verify a Webhook (Developer Guide)

Verification is five steps and works in any language. Hand this to your developers:

A minimal Node example of the core check:

import crypto from "crypto"

// rawBody is the exact bytes of the request body
const expected = crypto
  .createHmac("sha256", YOUR_STORE_SECRET)
  .update(rawBody)
  .digest("hex")

const sent = req.headers["x-tryoncloud-signature"].replace("sha256=", "")

const ok = crypto.timingSafeEqual(
  Buffer.from(expected),
  Buffer.from(sent)
)

if (!ok) return res.status(401).end()          // forged or tampered
// also reject if x-tryoncloud-timestamp is too old, then dedupe on delivery-id

How to Connect It

That is the whole setup. No CSV juggling, no nightly sync, no lock-in. Your highest-intent shoppers reach your CRM the moment they engage, and you keep full control of where that data goes.

Frequently Asked Questions

The questions merchants and their engineering teams ask most before connecting a virtual try-on webhook to their CRM: