Prerequisites: Whop products and Make code · 2 onboarding steps
Two things must be right before onboarding can run. The Whop product name must say "onboarding". The three Make automations must stay as they are.
▸ The full walkthrough: 5 minutes, the Make automations first, then the Whop products
What this does
This page covers the set-up that the other two pages need. In Whop, the product for the first payment needs the word "onboarding" in its name. In Make, three automations make the Google Drive folders, share them and post Fidel's welcome. Leave those automations alone.
The one thing to remember: put "onboarding" in the name of the first payment's product, and only there. Do not put it on the retainer. Without the word, a payment never starts onboarding.
Where it sits
Step 0 · HerePrerequisitesSet these up first
pays
Step 1 · Code + MakePayment to onboarding startedRecord, channel, folder, email
How it works
There are two halves: the product names in Whop, and the automations in Make.
- In Whop, make one product for the first payment. Sheni's example is a one-time onboarding fee.
- Put the word "onboarding" in that product's name. Capital letters do not matter. The word can be anywhere in the name.
- Do not put the word on the retainer or on the monthly subscription.
- The server reads the product name, then the price name. If either one has the word, the payment counts.
- For a new price, duplicate the product and change the price. Keep "onboarding" in the name.
- Send the client the payment link of that product.
- Only a successful payment counts. A failed payment changes nothing.
- For a client that the server knows already, only a first payment starts onboarding:
- A one-time payment or a new subscription counts as a first payment.
- A renewal never starts onboarding.
- A client at 100 - Onboarded never starts again, whatever the product name.
- In Make, leave these three automations alone. The server sends them work and waits for their answer:
- Create Drive Folder → make the client folder inside Clients, in Fidel's Drive.
- Make 5 folders in it: Raw Footage, Edited, Lead Sheet, Contract and Brief.
- Set Raw Footage so that anyone with the link can edit it. Then send the folder ids to the server.
- Give Edit Access → share the folders the way the server asks. The table below shows who gets what.
- Fidel Welcome Message → post the welcome in the client channel as Fidel, with his own Slack connection.
- Make does this work because Google Drive and Fidel's own Slack user connect easily there.
Who gets what in Google Drive
| Who | Client folder | Raw Footage and Lead Sheet | Edited, Contract and Brief |
|---|---|---|---|
| Every Icarus Growth address | Edit | Edit | Edit |
| Every Active team member | Edit | Edit | Edit |
| The client's paying email and form email | View | Edit | View |
Anyone with the Raw Footage link can also edit that folder. Google emails the client one time, for the client folder. If the client could edit the client folder before, Make sets them back to view.
The moving parts
The rule about the product name is in the code on LeadLift's server. The Drive work and the welcome run in Make, in Fidel's account.
Starts from
The product name on each Whop payment
Runs on
LeadLift's server on Modal, and Make in Fidel's account
Make plan
Core: 10,000 operations a month. The count starts again on the 25th.
Make logins
Fidel's Google Drive, which needs a new sign-in before 11 Apr 2027. Fidel's own Slack user.
Keeps its data in
The client record keeps the product name and each folder id.
Reports to
The client's #onboarding thread, through the server · #sentry, when Make cannot report back or a share fails
Good to know (as of 12 Oct)
• None of the Whop products from real payments has "onboarding" in its name yet.
• Rename a product, or make a new one, before the first real client pays.
• In the video, Sheni could not open LeadLift's own products in Whop. Fidel is the Whop admin, so he sets up the product.
• A product with more than one price also works, if its name has the word.
• Make also runs the footage automations of the Editing Pipeline. Leave those alone too.
• Make's run log shows the password that the server sends to Make. Make keeps each run for 30 days.
• None of the Whop products from real payments has "onboarding" in its name yet.
• Rename a product, or make a new one, before the first real client pays.
• In the video, Sheni could not open LeadLift's own products in Whop. Fidel is the Whop admin, so he sets up the product.
• A product with more than one price also works, if its name has the word.
• Make also runs the footage automations of the Editing Pipeline. Leave those alone too.
• Make's run log shows the password that the server sends to Make. Make keeps each run for 30 days.
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.
| Green | Who is on the team. On the Team page, set a person to Active. Make then shares each new client folder with them. |
| Amber | The word "onboarding". Sheni set this rule on 10 Oct. Claude changes the rule and its test together. Then send one test payment. |
| Amber | Which payment counts as a first payment. Today it is a one-time payment or a new subscription. Sheni set this on 10 Oct. |
| Amber | Who gets which access in Drive. Sheni set this on 11 Oct. Claude changes the rule and its test together. Then check the Share box of a test folder. |
| Red | The three Make automations. Leave them alone. If one changes, new clients get no folders, no shares or no welcome from Fidel. |
| Red | The Raw Footage link setting. It lets clients upload with no Google account. If you make it view only, clients cannot upload. |
| Red | The Make web addresses that the server calls. The server keeps them as settings. If one changes in Make, that step shows ✗ in each new client's thread. |
| Red | The Clients folder in Fidel's Drive. Make puts each client folder in it. If it moves or goes, Make makes no folder. |
| Red | Make's Google Drive and Slack connections. They are Fidel's logins. Sign in to Drive again before 11 Apr 2027. |
| Red | Whop's signing secret and the web address that Whop sends to. Change them only together with the server. |
What connects to this
This set-up comes before everything else in onboarding.
◀ Comes in from
- Whop
Fidel's products and their prices. - Make
Fidel's account, with his Google Drive and Slack connections.
Goes out to ▶
- Payment to onboarding started The product name decides if a payment starts it. The three automations do its Drive work and Fidel's welcome.
- Editing Pipeline Its footage automations also run in Make.
No step comes before this page. The contract is not part of this set-up yet.
If something looks wrong
| #payments shows the payment, but no launch message came in #onboarding. The product name has no "onboarding". Fix the name in Whop. Then tell us: the server keeps each Whop event, so the payment is not lost. |
| A retainer payment started onboarding. The retainer's name has the word. Take it out. Then check the new client record: it can be a duplicate. |
| The thread shows ✗ on "Drive folder copied". Make's Google Drive connection may need a new sign-in. Or Make reached its monthly limit. |
| The thread shows ✗ on "Fidel welcome message". Check Fidel's Slack connection in Make. Post the welcome in the channel by hand. |
| #sentry says that a share failed. The email may have no Google account. Share the folder by hand. The post gives the steps. |
| Every Make automation stopped. Make reached 10,000 operations this month. Fidel gets an email from Make. The count starts again on the 25th. |
You cannot break this for good. We keep a full copy of each of the three Make automations with these pages. If a setting goes wrong, we put the automation back from that copy. Each change to the code is a saved version too.
Call us if new clients get no Drive folder, or a real onboarding payment does not start onboarding.
Call us if new clients get no Drive folder, or a real onboarding payment does not start onboarding.
Jargon buster
- Product
- A thing that a client can buy in Whop. It has one or more prices.
- Retainer
- The monthly payment that comes after the first payment.
- Make automation
- A scenario in LeadLift's Make account. Each one does one job.
- Operation
- One step that Make runs. The plan allows 10,000 each month.
- Connection
- A login that Make keeps for one tool, for example Fidel's Google Drive.