video1.0<iframe src="https://www.loom.com/embed/abb7f81c8ca44a7799003606c02585e7" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/abb7f81c8ca44a7799003606c02585e7-ee0015bbe0956e4a.gif290.274This Loom explains key prerequisites to ensure onboarding runs correctly for clients. It emphasizes leaving the Make.com automations and related backend code alone because they manage Google Drive folder creation, client access, email sending, and Slack onboarding steps. A main requirement is that the first WAP payment product must include the word onboarding, using a one-time startup onboarding link rather than placing onboarding on the retainer or subscription payments. The video also notes you may need to duplicate onboarding products for different prices, ensuring the product name contains onboarding so the onboarding process triggers properly.