-
Notifications
You must be signed in to change notification settings - Fork 457
feat: use-create-lead-form-for-self-hosted #6117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Zaimwa9
merged 14 commits into
main
from
feat/create-self-hosted-contact-with-lead-form
Oct 13, 2025
Merged
feat: use-create-lead-form-for-self-hosted #6117
Zaimwa9
merged 14 commits into
main
from
feat/create-self-hosted-contact-with-lead-form
Oct 13, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for GitHub.
|
for more information, see https://pre-commit.ci
Docker builds report
|
…ub.com:Flagsmith/flagsmith into feat/create-self-hosted-contact-with-lead-form
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6117 +/- ##
=======================================
Coverage 97.99% 98.00%
=======================================
Files 1278 1278
Lines 44927 44983 +56
=======================================
+ Hits 44028 44084 +56
Misses 899 899 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ub.com:Flagsmith/flagsmith into feat/create-self-hosted-contact-with-lead-form
gagantrivedi
approved these changes
Oct 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for submitting a PR! Please check the boxes below:
docs/
if required so people know about the feature!Changes
This PR aims to harmonize how we capture lead between self_hosted and saas into hubspot.

These flows are valid when the consent checkbox is ticked.
Before
POST /api/v1/onboarding/request/send/
send_onboarding_request_to_saas_flagsmith_task
is dispatched, sending a request to our flagsmith SaaS instancecreate_self_hosted_onboarding_lead
contact
API directly to create user with company associationAfter
One of the goal is to entirely rely on Hubspot to deal with the company creation/association (based on user domain name)
POST /api/v1/onboarding/request/send/
includinghubspotutk
cookie for attributionsend_onboarding_request_to_saas_flagsmith_task
is dispatched, sending a request to our flagsmith SaaS instance without organisation data but with cookiecreate_self_hosted_onboarding_lead
create_lead_form
is send, along with hubspot cookie and the correct form idHow did you test this code?
Please describe.