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
- AdMeta Ads
- Pagelanding + payment
- PaymentRazorpay
- n8nverify, match by phone
- CRMstage moves itself
- 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.
- Razorpay webhook
- If this workflow crashes
- Verify signature and parse
- Slack: workflow crashed
- Process, reject or ignore
- Already handled?
- Send second payment to program workflow
- New payment?
- Captured or failed?
- Wait for thank-you page data
- Prepare failed contact
- Synamate: find failed payer by phone
- Find attribution
- Synamate: upsert failed contact
- Pick failed contact (phone first)
- Find checkout by phone
- Failed: phone owner found?
- Prepare paid contact
- Synamate: tag payment failed
- Synamate: update failed phone owner
- Synamate: find contact by phone
- Resolved failed contact
- Pick contact (phone first)
- Synamate: upsert paid contact
- Summarise failed run
- Phone owner found?
- Synamate: update phone owner
- Synamate: add paid tags
- Resolved contact
- Prepare Meta event
- Meta: send AssessmentPaid
- Pipeline configured?
- Synamate: find assessment opportunity
- Decide opportunity action
- Create, move or keep?
- Synamate: create opportunity
- Synamate: move opportunity to Paid
- Summarise paid run
- Slack: notify sales
- Ledger: record payment
- Any problems?
- Prepare WhatsApp confirmation
- Slack: alert tech channel
- TailorTalk: send payment_confirmed
- Primary template sent?
- TailorTalk: send fallback template
- WhatsApp sent?
Want this for your clinic?
Request a quote and we will tell you what we would change first.