Payment to onboarding started code · 12 onboarding steps

How it works

The server answers Whop at once. The slow work then runs in the background. Each part writes its result in the client's thread.

1. A client pays on Whop. Whop sends the payment to LeadLift's server.
2. The server checks Whop's signature and keeps a copy of the event. It refuses a payment with a wrong signature.
3. The server posts one line in #payments for each successful payment.
4. The server reads the product name and the price name. If neither has the word "onboarding", it stops here.
5. The server finds the client, in this order:
   1. The same payment, the same membership or the same Whop user.
   2. Exactly one client with the same email. The server looks at the paying email and the form email.
   3. No match → make a new client at 0 - Paid. The contract starts today, on a 3-month window.
   4. A new client → check for a duplicate: the same phone, the same name, or a close spelling.
   5. A possible duplicate → add one ✗ line to the thread for a person. The server never merges two clients.
   6. Already onboarded → record the payment only. A renewal never starts onboarding either.
6. The client shows in the app at once, on the Clients page and the Onboarding queue.
7. The server lays out the 17 onboarding steps. It posts the launch message in #onboarding.
8. The thread under that message is the client's run log.
9. The server starts three jobs. Each runs on its own, so one failure does not stop the others:
   1. Slack: make a private channel with the client's name. Invite each Active team member who has a Slack id.
   2. Then invite the onboarding alerts person and Viktor. Set the topic. Send the client a Slack Connect invite.
   3. Drive: after the Slack job, Make makes the client folder with 5 folders in it.
   4. Skool and email: add the client's email to the Skool group. Then send the welcome email.
10. The welcome email has three buttons: the client's own form link, the call booking link and Skool.
11. When Make reports the folder, the bot bookmarks Raw Footage in the client channel.
12. Then Make posts Fidel's welcome message in the channel, as Fidel himself.
13. Make also shares the client folder with the team, Icarus Growth and the client.
14. Each step adds one ✓ or ✗ line to the thread. A ✗ line tells a person what to do by hand.

The moving parts

These are the parts that this step uses. The code runs on LeadLift's server. The Drive work and Fidel's welcome run in Make.

What you can safely change

Green: change it in the app. Amber: ask Claude in the LeadLift code folder, then check the result. Red: do not change it. Call us.

What connects to this

This tab shows what starts this step and what uses its results.

If something looks wrong