flagsmith icon indicating copy to clipboard operation
flagsmith copied to clipboard

Add newly created accounts on SaaS into Pipedrive

Open dabeeeenster opened this issue 2 years ago • 1 comments

Add Name and email as a new Lead in pipedrive. Similar to https://github.com/Flagsmith/flagsmith-website/blob/main/api/contact-us.js

dabeeeenster avatar Sep 09 '22 09:09 dabeeeenster

Whoever takes this on, please sync with me before you do this. I just want to make sure we get this done correctly. Thanks!!

malthauser avatar Sep 09 '22 10:09 malthauser

@malthauser I think the key thing we'd need to know here is when do we count a user as a new lead? Do we only want to count users that sign up and create an organisation or do we want to include users that, for example, sign up to an organisation via an invite?

matthewelwell avatar Oct 27 '22 10:10 matthewelwell

to add to this - Pipedrive has an entity that maps well to our Organisation I believe - should we use that?

dabeeeenster avatar Oct 27 '22 10:10 dabeeeenster

Ideal structure:

  • Create Organization that is connected to the domain name (ex: Disney.com = Disney)
  • New leads should be checked against a similar Organization to their domain

As for when we want to create a lead, we should create ALL emails that are added to the system, but include HOW they were added as a property. This will allow us to track how many new leads we are getting vs how the growth of invites is trending (also very important). I have a guy that I'm meeting with tomorrow that has a ton of Pipedrive experience. Let me check with him and circle back on this stuff.

malthauser avatar Oct 27 '22 10:10 malthauser

Having discussed with @malthauser, my understanding of the requirements is as follows:

  • When a new user signs up, we create a new lead in Pipedrive
  • New users should include context as to how they signed up (clean sign up, via invite, via SSO)
  • (perhaps a future requirement) Users should be added to an organisation based on the domain in their email address

matthewelwell avatar Nov 02 '22 11:11 matthewelwell

looks great. thanks!

malthauser avatar Nov 02 '22 16:11 malthauser

@kyle-ssg as discussed, I think we'll need to add a parameter (POST) to the sign up endpoints (email / password, github, google) to know whether the page was reached via an invite or not. As a starter, I'm suggesting:

"sign_up_type": "NO_INVITE|INVITE_EMAIL|INVITE_LINK"

I'll also need to look into how LDAP works, although that's less important as it's currently enterprise on premise only.

matthewelwell avatar Nov 08 '22 16:11 matthewelwell

Frontend is live

kyle-ssg avatar Dec 06 '22 14:12 kyle-ssg

@matthewelwell I think this can be closed?

kyle-ssg avatar Dec 06 '22 14:12 kyle-ssg