wiki/knowledge/salesforce/finwellu-ria-subscription-webhook.md · 516 words · 2026-04-05
FinwellU RIA Subscription Webhook Integration
Overview
As part of the [1] FinwellU subscription model launch, a Salesforce webhook integration is required to capture user registration data when RIA employees sign up for financial wellness workshops. The primary purpose is to track user origin (which employer company they came through) and enable accurate revenue splits between NextLevel and its RIA partners.
Business Context
NextLevel is launching a paid subscription service for Registered Investment Advisors (RIAs). Each RIA subscribes on behalf of their employer clients, and those employer clients' employees then register for individual workshops. Because multiple RIA partners may be involved, NextLevel needs to know which registrant came through which RIA in order to calculate revenue splits correctly.
The subscription fee is paid in advance by the RIA — the webhook is not for payment processing, but for attribution and tracking of individual registrants back to their originating company and RIA relationship.
Login & Registration Flow
The site uses a two-tier authentication model:
- Company-level login: Each employer client (e.g., Marquette University) receives a single shared login credential. The RIA distributes this link/login to their employees.
- Individual registration: Once inside the company-specific page, individual employees register for a specific workshop by entering their personal information (name, email, etc.).
This means the company identity is established at the login stage, and the individual identity is captured at the workshop registration stage.
Webhook Data Requirements
When a user completes workshop registration, the following data should be pushed to Salesforce via webhook:
| Field |
Source |
| Registrant name |
User-entered at registration |
| Company name |
Derived from company login page |
| Workshop name |
Selected workshop |
| Workshop date |
Selected workshop |
Additional status fields (e.g., registration status, amount) may be included if relevant to the Salesforce record structure.
Implementation Notes
- Trigger point: Webhook fires on individual workshop registration, not on company login.
- Company attribution: Because each company has its own password-protected page, the company identity is implicit in the page context at registration time — no additional user input is required to capture it.
- Salesforce record: The webhook payload should create or update a record in Salesforce that reflects origin company, registrant details, and workshop enrolled. This enables downstream revenue split calculations.
- RIA CEO technical capacity: Peter noted that NextLevel's CEO (James) holds a master's in technology and may be able to assist with Salesforce-side configuration, reducing the integration burden on AAG.
- Individual logins per employee are not part of the current scope. Employees register for events but do not receive persistent personal accounts. This was confirmed during the [2].
- A certificate of completion feature (Phase 3) may eventually require tracking individual attendance through a QR code scan at the end of workshops. This would be a separate integration from the registration webhook and is not in scope for the current launch.
Related Articles