Skip to content

Salesforce

With the Lasso integration for Salesforce, you can export leads and accounts from Lasso, and keep them updated automatically with data from CVR. Using Salesforce's Webhooks, you are able to create contacts directly in Salesforce, but still have Lasso enrich and update them when they are updated in CVR.

Updating items created in Salesforce

Apart from sending leads and accounts from Lasso to your Salesforce system, it may be preferable in some setups to not have to leave your Salesforce system to retrieve data. With our webhook-based integration with Salesforce, it is possible to do just that.

How it works

Lasso utilizes Outbound Messages triggered by Flows to notify Lasso about changes to the CVR field in Lasso, or the creation of a new Lead or Account. This allows us to propagate data to your Salesforce system without having to leave Salesforce to do so. It works both on the creation of new Leads and Accounts, as well as on updates of the CVR field on Lead or Account. Once we have been alerted, we will propagate the data and start monitoring the company on your behalf, sending you any updates to the data that may occur. If you change an existing CVR to a new one, you will no longer receive updates for the old CVR.

Setting it up

Setup is fairly simple. First, you must connect your Salesforce with Lasso. Then, you must create a flow with an accompanying outbound message to our servers and activate it.

Connect with Lasso

Connecting your Salesforce account with Lasso is done by simply going to the settings page and clicking integrations, choosing Salesforce from the list. Authentication is done using OAuth (Username and password). Be sure to use a system or admin account for this, as the user you pick will not be able to utilize the functionality within Salesforce due to technical limitations of Salesforce.

Make sure to set up your mappings while you're there.

Create Outbound Message

Go to your setup page in Salesforce, under Platform Tools open Process Automation, then open Workflow Actions and finally Outbound Messages

  1. Click New Outbound Message
  2. Select Account or Lead as your object, depending on your needs, then click Next.
  3. Configure the name and unique name to your liking, and set the endpoint url to:

    https://api.lassox.com/webhooks/salesforce?accessKey=YOUR_API_KEY

  4. Under Fields to send, include the fields Id and YOUR_CVR_FIELD before clicking Save.

Create Flow

Go to your setup page in Salesforce, under Platform Tools open Process Automation, and then Flows.

  1. Create a new flow, and select Record-Triggered-Flow.
  2. Select Account or Lead as your object, depending on your needs.
  3. Set Configure Trigger to "A record is created or updated"

  4. In Set Entry Conditions, switch to "Formula evaluates to True", and enter the following in the formula field:

    AND(
    OR(ISCHANGED(YOUR_CVR_FIELD), ISNEW()),
    LEN(YOUR_CVR_FIELD)==8,
    ISNUMBER(YOUR_CVR_FIELD),
    CreatedBy.Email != 'YOUR_CONNECTED_ACCOUNT_EMAIL'
)

    Replacing YOUR_CVR_FIELD and YOUR_CONNECTED_ACCOUNT_EMAIL to the correct cvr field and connected account email, respectively. In short, this flow makes sure that the flow will fire whenever a new account is created or modified, and the CVR is set to a valid, new CVR number. It also ensures that the connected account does not trigger the flow, as this would cause problems when importing from Lasso.

  5. Set When to Run the Flow for Updated Records to "Every time a record is updated and meets the condition requirements"

  6. Set Optimize the Flow for to "Actions and Related Records" and click Done
  7. A flow should have been created, now click the + icon on the graph. From here, choose Action, then select Outbound Messages and find the outbound message you just created. Give it a name and click Done.
  8. Finally save your flow and give it an appropriate name.

Don't forget to activate

Once you've created the the flow, make sure to activate it.

Limitations

There are two limitations to this integration; first, it is not allowed to use the integration with the user that is connected with Lasso, which is avoided using the formula above. This is to avoid mass import of data from Lasso triggering an unwanted amount of updates through webhooks. Second, it is not possible to use this feature in combination with mass imports. If our servers see more than five companies created or changed in a single operation, such as a mass import, they will be ignored.