Supply Lens

How do I connect my CRM, HubSpot or Pipedrive, to Supply Lens?

Add HubSpot or Pipedrive

Turn won HubSpot deals into orders for your back office, or create and update Pipedrive deals from the orders in your back office.

About 6 min

At the end of this guide your CRM will be connected to Supply Lens and tested on one deal. HubSpot and Pipedrive work in opposite directions, so pick the one you use:

HubSpotPipedrive
DirectionHubSpot → Supply LensSupply Lens → Pipedrive
What travelsA deal becomes an orderAn order (or quote) creates or updates a deal
Use it whenSales close deals in the CRM and the back office fulfils themThe back office creates orders and sales want to see them, and their outcome, in the CRM

Before you start

  • Admin access to the CRM, and the details its connection form asks for.
  • Admin access to Supply Lens, to reach Settings → Integration setup.
  • Your back office already connected, for example Unleashed. See Add an Integration.
  • For HubSpot: the IDs (not the names) of the pipelines and stages whose deals should become orders, usually the closed-won stage or a later one such as "Paid". Get them from HubSpot's pipeline settings or your HubSpot admin.
  • For Pipedrive: the pipeline and stage IDs new deals should land in, the API keys of any custom fields you'll fill, and your list of lost reasons if Pipedrive keeps a fixed list. Clean up duplicate organisations first.

Steps

Create and connect

  1. Go to Settings → Integration setup → Integrations.
  2. Click + ADD INTEGRATION, search for HubSpot or Pipedrive and click ADD.
  3. Complete the form and click CONNECT. Leave Activation disabled for now.

Add Configurations

  1. Expand the tile, click Configurations, then + Add.
  2. HubSpot: add Order with Receive and click Create Default JSON. Set pipelineStages to your pipeline IDs, each with its list of stage IDs, for example "pipelineStages": { "12345678": ["98765432"] }. Click Save.
  3. Pipedrive: add Order with Send and click Create Default JSON. Set defaults in tagToPipelineIdMap and tagToStageIdMap so every deal lands somewhere, and customerFieldIdentifiers so deals link to the right organisation or person. Optionally turn on includeProductsOnDeal, customFieldMapping and the lifecycle settings (completedOrderStatus, markCancelledAsLost). Click Save. Quotes have matching settings of their own.

Add Mappings

  1. Go to Settings → Integration setup → Mappings and click + ADD.
  2. HubSpot: create Order from HubSpot to your back office.
  3. Pipedrive: create Order from your back office (for example Unleashed) to Pipedrive.
  4. Set As to Target Data, tick Enabled, leave Automatic off while testing, and click SAVE.

Test

  1. Set Activation to Enabled, with no schedule.
  2. HubSpot: move a test deal into one of your listed stages, then click Run Receive under Manual Operation.
  3. Pipedrive: create a test order in your back office, let it reach Supply Lens, then click Run Send on the Pipedrive tile.

Check it worked

  • HubSpot: the deal appears as an order under Sales → Orders in Supply Lens, then in your back office. Deals in other stages don't arrive.
  • Pipedrive: a deal appears in the right pipeline and stage, linked to the right organisation, with the fields you mapped.
  • Then set a Schedule and turn Automatic on for your Mappings.

If something goes wrong

  • HubSpot deals don't arrive. Check you used stage IDs, not names, and that the deal was created on or after setupDate.
  • A Pipedrive deal fails on duplicate organisations. Merge the duplicates in Pipedrive, or turn on useNewestMatchingOrganisation and work through its warnings.
  • Marking a deal lost fails. Every reason in lostReasonTagMap, including the default, must be on Pipedrive's fixed list of lost reasons.
  • For every setting, see the HubSpot settings and Pipedrive settings.