Ingesting the Salesforce owner email in Hull

Hi there,

We have a new feature to announce on the Salesforce connector!

When you want to set-up assignment rules, one way to do so is to configure them inside your Salesforce instance. This creates a new field on each of your Contact and/or Lead called salesforce_owner_id. This id is useful inside Salesforce because it is linked to the Salesforce profile of the owner.

Let's say you want to propagate the assignment rule to another tool of your stack. Sending the salesforce_owner_id is not really relevant because it is not actionable by your third party tool since it does not know how to link it to an employee of your company. What you can send is the email of that salesforce owner because that email will allow the third party tool to identify the owner.

To achieve that before, you had to create some processor code to call the Salesforce API to fetch the owner email. We have now solved that by allowing that feature directly inside the Salesforce connector.

This Salesforce owner email is easily accessible from the attribute mapper picker like any other Salesforce field that you want to fetch on the Lead and the Contact as you can see in the following screenshot:


New Website connector

Hey there,

We have a new announcement for you! We have just released a new connector called "Website connector" which is a replacement of our former platform deployment feature with Hull.js.

Hull.js allows you to track website traffic and send this behaviour to Hull. This is a snippet of code that you used to be able to add to your website using our platform feature available from the overview page of the dashboard.

This implementation was a bit complex to access before and needed some guidance. That's why this feature is now available inside a new connector called "Website Connector". The connector is now directly accessible from the gallery and you will be more guided through the installation of that important feature also making your overall experience with Hull more consistent.

The "Website connector" settings are broken down into 3 main sections:

  • Installation:

Whitelist the domain that you want to track with Hull.js using the Whitelisted domains subsection and copy-paste the HTML tag that you need to add in the HEAD of your website code. website_connector_1.png

  • Tracking:

You can choose to track page views automatically by enabling the toggle button called Track page views events automatically


  • Scripts:

The Website connector allows you to add an external script to your website without having to deploy new code to the website. External scripts can call specific connectors which work client-side, for instance, Intercom (see documentation here)

You can also add an embedded snipped of js code using the Embedded script sub-section. website_connector_3.png

⚠️ Warning ⚠️:

If you had set-up your tracking system using Hull.js with the former implementation, no changes will be required on your end. You will just see new Website connectors added to your organizations (that will not count towards your current plan).

New Account Processor connector

Hi there,

We have some big news for you. Our new Account Processor is now up and running!

When you want to run ABM strategies, you want to define actions on the Account:

  • you want to score Accounts without having to add a score attribute on the User first and then link that attribute to the Account
  • you want to be able to define fallback strategies on the Account level. If for example, you have an attribute called industry_name that comes from both Datanyze and your CRM, you want to be able to define which source takes precedence over the other. To do so with the Account processor, you had to link the Account attribute to the corresponding Users and then write your fallback strategies on the Users. This was a pretty complex process.

No more pain on the Account now that we have released our new Account Processor!

This Processor will run based on changes on the Account level and has also a couple of enhancements:

  • first, you can whitelist the Accounts on which you want to apply your JS logic: account_filter (2).png

  • second, you can define custom variables that are directly accessible inside the code editor. You can do so by defining a variable name, for example api_key , give it a value like 25kt. The variable you defined as foowill be accessible it inside the processor via Note that these custom variables can only be defined as strings. Screenshot_2019-12-03_at_10.45.37 (1).png

Other than that, the code editor works the same way as for the former Processor. It is accessible from the Code editor button inside the Overview page of the Account Processor:


Outreach incoming events

Hey there,

We are happy to announce you a new enhancement to our Outreach connector: you can now ingest Outreach events to Hull.

When your salespeople hop on a call with leads, they want to have access to their full history with the company:

  • How they interacted with the company emails with events like message opened, message clicked,…

  • How they moved through the sales pipeline with events like prospect_stage_changed , emails_opt_out,…

Ingesting this data into Hull and sending it in your CRM can prove to be valuable information for sales to better convert. In the same way, you don't want your salespeople to send an email to a prospect who just received an email sent with Outreach.

The full list of events that we are able to ingest is the following:

  • bounced_message
  • emails_opt_out
  • inbound_message
  • message_clicked
  • message_opened
  • message_opened_sender
  • outbound_message
  • prospect_stage_changed

You can select the Outreach events you want to fetch inside the dropdown of the Events - Fetching from Outreach section of the Outreach connector section (see below):

Screenshot 2019-12-05 at 17.45.09.png

Deactivate connectors

Hey there,

We are happy to announce to you a new feature that will allow you to deactivate connectors you installed on your Hull organization.

Hull sits at the heart of dataflows setups which are often complex. These dataflows are defined by the connectors of the tools you want to connect to Hull. Before, connectors used to start to do their work as soon as a minimal configuration was done on the connectors. That did not allow the customer to make sure that his incoming and outgoing set-up was correct. The result of this was sometimes dumped data flying around which meant grueling work for you.

Sometimes it also happened that you wanted to put an integration on hold because you had some wrong data being piped into a 3rd party service. The only thing you could do is delete the connector with all the configuration settings. That meant having to re-install the connector and set-up again the settings which was cumbersome.

Those issues are now over by allowing you to pause whenever you like the connector of your choice. Note that you can still send outgoing data by performing manual batches while the connector is paused.

You can now put a connector on hold by clicking on the desactivate button under the name of the connector:


It will show you a commit message explaining what disabling a connector entails:


Once the connector is paused, the button under the name of the connector will turn like this:


And to enable it back, you will have an other commit message confirming you normal updates will be back:


Pushing events inside Salesforce as Tasks

Hey there,

Did you ever try to reduce the time between a lead sign-up and the moment when a sales reaches out to the lead? Did you ever complain about the lack of historical information a sales could have on a given prospect before hopping on a call with that lead?

Well, if you are a Salesforce user, we have found a solution for you: it is now possible to push events from Hull as Tasks directly inside Salesforce. This feature is an enhancement to the current Salesforce connector. This will allow you to make those events tied to the user appear on the Contact timeline inside Salesforce in the form of Tasks.

For instance, whenever you have a sign-up event tracked by Segment on the website, you can ping your sales directly via a Task called To reach out inside Salesforce so that they reach out to him fast. And you know how reaching out to a lead as fast as possible can drastically improve conversion rates.

Also, whenever a sales has a call with an opportunity, it is important that he knows that he performed x number of Email opened events inside your marketing automation tool and x number of Opened conversation inside Intercom. Because this will help him adapt the conversation depending on the history of the opportunity with the company.

Here is how it works:

1) Create a unique, external id field on the Task object in your Salesforce instance that we will use to store the id of the Hull Event. This will guarantee that the Hull Event and the Salesforce Task will remain in sync.

2) In the Salesforce External_id dropdown, select the name of the external_id you just created inside Salesforce.


3) Select the events you want to send inside the Task Type Mapping section you would like to send to Salesforce and the type of Task to create.

Screenshot_2019-11-28_at_09.55.42 (1).png

4) In the Task reference Mapping section, select the id of the Contact/Lead you want to map to the associated contact or lead of the Task.


5) In the Task fields mapping section, map the properties or context fields of the Hull Event to any modifiable field on the Task.


Do not forget to turn on the toggle “Push Tasks” to start pushing the Tasks.

Pipedrive connector

We have a huge product announcement to make: we have just released our much-anticipated Pipedrive connector!

Pipedrive is a comprehensive, lightweight CRM built around a sales pipeline management methodology. The "pipe view" displayed as an overview in the product prompts salespeople to trigger actions and remain organized throughout the sales process.

This new Pipedrive connector is a classic CRM connector that allows you to fetch and send out Persons (Users) and Organizations (Accounts):

  • Authentication and User Identity: authenticate directly from the settings section and select your identity resolution strategy.


  • Ingestion of users: capture attributes from Pipedrive and link them to attributes inside Hull. Enable automatic linking between Users and Accounts from Pipedrive and let deletion inside Pipedrive also delete users inside Hull.


  • Sending users out to Pipedrive: whitelist segments of users you want to send out to Pipedrive as Persons and match attributes from Hull with attributes inside Pipedrive. You can also propagate Linking between Users/Accounts and Deletion inside Pipedrive. Screenshot_2019-10-21_at_15.15.57.png

The ingestion and synchronisation of Users (Persons) works exactly the same way for Accounts (Organizations)

New Zapier connector

Hey there,

The number of SaaS software has not stopped increasing in the past 10 years as more and more companies are switching to cloud-based software and are becoming more vertical-specific.

As a result, it has become compulsory for BtoB SaaS companies to subscribe to products that allow tools "to speak with each other". That is the main purpose of Hull, to unify customer data across your various tools in one single place and sync them back. This also prompted Zapier to become such a successful company with its workflow tool that allows orchestrating actions in a tool based on a trigger occurring in another.

Today, we are announcing our new Zapier connector. With our new Zapier connector, you will be able to integrate Zapier workflow capabilities with the unified and historical data of your Hull instance.

You will be able to trigger workflows inside Zapier based on the following events inside Hull:

  • a User entered a Segment
  • a User left a Segment
  • an Account entered a Segment
  • an Account left a Segment
  • a User Attribute was updated
  • an Account Attribute was updated
  • a User Event was created
  • a User was created
  • an Account was created

For instance, you can think about sending a personalized Intercom message whenever a user enters in a segment called sign-up with a lead score > 60, a segment that contains all the sign-ups for which their score is higher than 60 (computed for instance inside Hull with our Processor connector).

Cool right ?! But that's not over. You can also set-up actions inside Hull based on triggers from the other tools Zapier does support.

You can perform the two following main actions inside Hull: CREATE and SEARCH.

  • CREATE: create or update a Hull Account, create or update a Hull User, create a User Event
  • SEARCH: find an account, find a user

For instance, you can think about helping CS and sales better know about their leads by updating their users timeline inside Hull with events fired inside Appcues. Appcues is a great tool to help SaaS companies easily customize the onboarding of their users.

For instance, add to the user timeline an event called Added a collaborator fired from Appcues. and that will help your sales know if that lead started collaborating on the tool with colleagues. That way you can have your users updated inside Hull and then to the tools you are connected to like Intercom or Salesforce.

Having your CS and sales know about the events they performed during the onboarding is a sure way to improve the conversation with the lead and thus improve conversation rates.

Here are the steps to follow to set up your Zapier connector and start automating workflows:

Triggering a Zap based on a Hull event:

  • Install the Zapier connector


  • Go to your Zapier account, Make a new zap! and select Hull as an app


  • Choose your trigger event among the list


  • Once you have selected your trigger, you will be asked to authenticate to your Hull organization. Add the token available in the settings of your Zapier connector.


  • If you have selected User entered a Segment, choose a segment on which you want to trigger your Zap


  • You can then go on setting-up your actions with the other tools you want to connect

Create actions in Hull based on a trigger inside Zapier

  • Choose the Action Event among the list above


  • Configure the attributes you want to update or search for on the account or user level. For instance, if you selected the Create or Update a Hull Account action, you can select in your triggering tool what corresponds to the external_id , the domain, as well as the attributes


Showing the events table

Hey there,

We have some news for you!

In Hull, events often play a big part in your use cases because events allow you to capture the behavior of your users on your website, app, or from other sources like emails and conversations.

Before, you did not really have a good way of controlling the events you tracked from your various sources. You could only guess the source of the event by its name, you could not count the number of times this given event was captured. This is problematic because high-volume events can result in a high volume of incoming requests, which may force you to upgrade your plan.

To solve that issue, we have added an events table inside the user timeline, much like the attributes tab found inside the user and account timelines. This will provide you with added clarity around the volumes of your various events.

Inside the events table, we now list the number of unique events captured in the selected time window Count, the number of unique users with that particular event Users, the number of average events per user in the selected time window Events/User and inside the Connectors column the connectors which captured that event.

Here is what it looks like:


Incoming deletion of contacts and companies in Hubspot

Hey there,

We now support the incoming deletion of contacts and companies inside Hubspot.

Before, when you deleted a list of contacts and/or accounts from Hubspot, this list would synchronize back to Hubspot because Hull would do its job of synchronization. So you had to delete them inside Hubspot and inside Hull as well.

We now have solved this problem by flagging inside Hull those contacts and companies you deleted inside Hubspot. They are flagged with a deleted_at trait.

So to make sure they are not synched back to Hubspot, you will need to select the new toggle button called Ignored Deleted Contactsinside the User - Sending to Hubspot section as shown in the following screenshot:


This feature works on the account level as well and you can access the same toggle button inside the Account - Sending to Hubspot section: ignore_deleted_accounts.png