Tracking new leads in Salesforce, augmenting user profile with RapLeaf

Upon a signup of a new user to a website with any social credential, we want to:

  1. Augment the user profile with additional public information through RapLeaf.
  2. Record the new signup as a New Lead on Salesforce for follow-up.

Implementing this with Auth0 is very easy. You just need 2 Rules in your pipeline:

1. Augment User Profile with RapLeaf

The 1st step is to obtain more information about this user using their email address. RapLeaf provides an API to retrieve public information about a user using the email as input that is extremely easy to use.

Once the call to RapLeaf completes, we store this additional information in a property called rapLeafData:

We are ignoring certain conditions that exist in the API and only doing this when there's a successful call (statusCode=200). The entire rule is ignored if the user has already signed up (signaled by the user.signedUp property setup after recording a new lead in step 2 below).

function (user, context, callback) {

  if(user.signedUp) return callback(null,user,callback);

  var rapLeafAPIKey = 'YOUR RAPLEAF API KEY';

    request('' +
            encodeURIComponent( +
            '&api_key=' + rapLeafAPIKey,
              if(e) return callback(e);

               user.rapLeafData = JSON.parse(b);

              return callback(null,user,context);
  else {
    return callback(null,user,context);

2. Create a New Lead in Salesforce

In this second step we record the information as a New Lead in Salesforce, so the sales department can followup. This Rule has some interesting things:

  1. The Salesforce REST API uses an OAuth Access Token. We are using the OAuth2 Resource Owner Password Credential Grant to obtain such Access Token. This is the getToken function that uses credentials as input as opposed to an API-KEY as the previous rule.
  2. We are just recording the user name and a fixed company name. We could of course use anything available in the enriched user profile we obtained in step 1, to record more information, and have better context for the sales representative.
  3. If everything went well, we use a persistent property: user.signedUp and set it to true. So next time this same users logs in, these rules will be skipped.
function (user, context, callback) {

  if(user.signedUp) return callback(null, user, callback);

            function(err, response){
                    if(err) return callback(err);

                    createLead(response.instance_url, response.access_token, function(err, result){
                        if(err) return callback(err);
                        //Everyhting worked fine. We signal this signup was successful.
                        user.persistent.signedUp = true;
                        return callback(null, user, context);

  function createLead(url, access_token, callback){

    //Just a few fields. The Lead object is much richer.
    var data = {
        Company: 'Web channel signups'
        url: url + "/services/data/v20.0/sobjects/Lead/",
        headers: {
            "Authorization": "OAuth " + access_token,
            "Content-type": "application/json"
        body: JSON.stringify(data)
        }, function(err, response, body){
            if(err) return callback(err);
            return callback(null,body);

  //Helper function to get an Access Token from Salesforce
  function getAccessToken(client_id, client_secret, username, password, callback){{
        url: '',
        form: {
            grant_type: 'password',
            client_id: client_id,
            client_secret: client_secret,
            username: username,
            password: password
        }}, function(e,r,b){
            if(e) return callback(e);
            return callback(null,JSON.parse(b));

That's it!

Check out our repository of Auth0 Rules for more great examples:

  • Rules for access control
  • Integration with other services: Firebase