From ad click to paid booking, with no one dragging cards

Payment, CRM update, sales alert and ad-platform signal now happen within seconds of each other.

Client and context

ReDial Clinic, a doctor-led metabolic health clinic in Delhi, sells a paid assessment to cold Meta traffic. A sales team follows up every payer.

The problem

"Someone pays, and we find out hours later. Meta only learns about the sale when someone remembers to move the card in the CRM."

Payments, the CRM and Meta were disconnected. Conversion signals reached Meta late or with the wrong value, so the campaign optimised on bad data. Failed payments disappeared silently.

What we built

  1. AdMeta Ads
  2. Pagelanding + payment
  3. PaymentRazorpay
  4. n8nverify, match by phone
  5. CRMstage moves itself
  6. Metaserver-side event
  • A Meta-to-payment funnel: landing page → payment page → thank-you page with a booking calendar.
  • A payment webhook in n8n that verifies each payment, matches the payer to their CRM record by phone, tags them, and moves their opportunity to the right stage automatically.
  • Server-side conversion events sent to Meta the moment payment clears, with click IDs and UTMs carried through from the ad.
  • Instant Slack alerts to sales for every payment, and a separate alert for every failed payment so someone can recover it.
  • A ledger table so every payment can be audited and nothing is sent twice.

Stack

  • Meta Ads
  • Meta Conversions API
  • GoHighLevel (Synamate)
  • Razorpay
  • n8n
  • Slack
  • Google Calendar
  • TailorTalk

Results

  • Conversion signal reaches Meta within seconds of payment, instead of whenever a card got moved.
  • Every paid booking traces back to the campaign and ad that drove it.
  • Failed payments trigger a same-day follow-up instead of being lost.
  • Sales sees every payer instantly, with no manual checking.

The workflow, mapped

The real n8n canvas behind this system (47 nodes), redrawn without credentials or customer data. Scroll sideways to follow a lead through it.

Map of the Assessment payment: paid or failed workflow: 47 steps, left to right.
  1. Razorpay webhook
  2. If this workflow crashes
  3. Verify signature and parse
  4. Slack: workflow crashed
  5. Process, reject or ignore
  6. Already handled?
  7. Send second payment to program workflow
  8. New payment?
  9. Captured or failed?
  10. Wait for thank-you page data
  11. Prepare failed contact
  12. Synamate: find failed payer by phone
  13. Find attribution
  14. Synamate: upsert failed contact
  15. Pick failed contact (phone first)
  16. Find checkout by phone
  17. Failed: phone owner found?
  18. Prepare paid contact
  19. Synamate: tag payment failed
  20. Synamate: update failed phone owner
  21. Synamate: find contact by phone
  22. Resolved failed contact
  23. Pick contact (phone first)
  24. Synamate: upsert paid contact
  25. Summarise failed run
  26. Phone owner found?
  27. Synamate: update phone owner
  28. Synamate: add paid tags
  29. Resolved contact
  30. Prepare Meta event
  31. Meta: send AssessmentPaid
  32. Pipeline configured?
  33. Synamate: find assessment opportunity
  34. Decide opportunity action
  35. Create, move or keep?
  36. Synamate: create opportunity
  37. Synamate: move opportunity to Paid
  38. Summarise paid run
  39. Slack: notify sales
  40. Ledger: record payment
  41. Any problems?
  42. Prepare WhatsApp confirmation
  43. Slack: alert tech channel
  44. TailorTalk: send payment_confirmed
  45. Primary template sent?
  46. TailorTalk: send fallback template
  47. WhatsApp sent?

See all 20 n8n builds

Want this for your clinic?

Request a quote and we will tell you what we would change first.