Send skin scan leads straight to your CRM
A lead is only useful if it reaches the system your team already works in. ScanSkinAI delivers every consenting scan lead into GoHighLevel or through Zapier, with the scan summary attached, so follow-up happens where your pipelines, tags and automations already live.
- Destinations: GoHighLevel and Zapier, together or alone
- 2Destinations: GoHighLevel and Zapier, together or alone
- Apps reachable once a lead is routed through Zapier
- 6k+Apps reachable once a lead is routed through Zapier
- Background retries with backoff on failed deliveries
- AutoBackground retries with backoff on failed deliveries
- Non-consenting leads ever sent to a CRM
- 0Non-consenting leads ever sent to a CRM
Connecting GoHighLevel
Open CRM & Automations in your dashboard
Expand the Send leads to GoHighLevel card. Each destination is collapsed by default to keep the panel tidy.
Paste your inbound webhook URL
Create an inbound webhook trigger in GoHighLevel and paste the URL. It is stored encrypted, and validated before it is saved.
Finish the workflow on the GHL side
Map the incoming fields to your contact, add the tags and pipeline stage you want, and turn the workflow on. ScanSkinAI can deliver the lead, but only your workflow can decide what happens next.
Send a test lead
Run a scan on your own page with consent ticked and confirm the contact appears. Recent deliveries in the panel will show the result either way.
Connecting Zapier
Zapier is useful when your stack is not GoHighLevel — or when one lead needs to go several places at once.
Create a Zap with a Catch Hook trigger, copy the webhook URL into the Send leads to Zapier card, and run a scan to give Zapier a sample payload. From there you can route the lead into Mailchimp, HubSpot, Google Sheets, Slack, your booking platform, or anything else Zapier supports.
What gets sent
- Name, email and phone number, normalised to international format where the dial code can be determined
- Marketing consent flag, captured separately from the scan itself
- Source channel and campaign from the tracked link the visitor used
- Scan summary — the key facial skin metrics — attached as a note on the contact
- A reference to the lead so you can find it again in your ScanSkinAI dashboard
Reliability and troubleshooting
- Deliveries are queued and processed by a background worker, so a slow CRM never blocks a client's scan result
- Failed deliveries are retried with backoff; persistent failures are surfaced with the error in Recent deliveries
- Recent deliveries is paginated and collapsed by default, with a total count in the header
- Connecting a CRM is not retroactive — leads captured before the connection stay in the dashboard only
Consent and data handling
Marketing consent is a separate, unbundled checkbox. A visitor can complete a scan and see their result without agreeing to be contacted, and non-consenting leads are never sent to any CRM.
Webhook URLs are encrypted at rest. Treat the destination CRM as the system of record for your marketing preferences and honour unsubscribes there.
Field reference
Both destinations receive the same payload, so a Zap and a GoHighLevel workflow can be built from one mapping.
Swipe the table sideways to see all columns
| Field | Example | Use it for |
|---|---|---|
| name | Amelia Grant | Contact record and personalised follow-up |
| amelia@example.com | Primary contact key and nurture sequences | |
| phone | +64 21 555 0134 | Normalised to international format where the dial code is known |
| marketing_consent | true | Proof of opt-in; only true values are ever delivered |
| channel | Attribution — which sharing method produced the lead | |
| campaign | spring-glow | Budget and performance reporting per campaign |
| scan_summary | Key facial skin metrics | Attached as a note on the contact for the follow-up call |
| lead_reference | Internal lead ID | Cross-referencing back to your ScanSkinAI dashboard |
Automations worth building first
- Instant thank-you email with the client's weakest metric and a booking link
- Task for the front desk to call any lead that has not booked within 24 hours
- Tag by channel so paid-social leads enter a different sequence to reception walk-ins
- Push a row to Google Sheets for weekly reporting alongside your booking data
- Slack alert to the clinic channel when a high-intent lead comes in outside opening hours
Keep one system of record
Once a CRM is connected, treat it as the source of truth for marketing preferences. Honour unsubscribes there, and your ScanSkinAI lead list stays a capture log rather than a second, competing contact database.
GoHighLevel or Zapier — which to connect
Swipe the table sideways to see all columns
| GoHighLevel | Zapier | |
|---|---|---|
| Best when | GHL is already your CRM and pipeline | Your stack is mixed, or one lead needs several destinations |
| Setup | Inbound webhook trigger, then map fields in a workflow | Catch Hook trigger, then any action Zapier supports |
| Contact created | Directly in GoHighLevel | Wherever your Zap routes it |
| Extra cost | None beyond your GHL plan | Depends on your Zapier task volume |
Frequently asked questions
Related business support
Medical spa lead generation
How a med spa turns walk-ins, social traffic and website visitors into booked consultations using AI facial skin analysis.
Hosted scan page for clinics
Your own branded scan page — launch in a day, share by link, QR code, poster or one-time invite, and budget scans by campaign.
Embed the scan on your website
Drop the scan into WordPress, Squarespace, Wix, Shopify or any site with one script tag. Clients never leave your domain.
Ready to turn scans into booked consults?
The medical spa page covers pricing, credit packs and what your clients see during a scan.