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)

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

Take retention period into account inside the segment builder

Hi there,

We wanted to announce a new enhancement to the segment query builder.

Before, when you wanted to create a segment relying on an event you often used the over all time parameter. This term was misleading because Hull offers you with a limited retention period for events (90 days with the standard plan).

We have solved that problem by changing the name from over all time to over retention period for this particular value.

If you want to know more about your retention period, please refer to the contract you signed with Hull which mentions the exact retention period to which you agreed.

Map multiple attributes at once and visualize attributes types

Hey there,

An important new feature has just been released that affects connector configurations/settings.

Before when you were setting up the attribute mappers of your connectors, you had to select an attribute from the third party service and match it to an attribute inside Hull (or the other way around if it is outgoing). You could only do one attribute at a time by clicking on the Map another attribute button.

This was cumbersome because especially in your outgoing set-up, you could have more than 50 attributes to add one by one.

We have solved that problem by allowing users to map multiple attributes at once inside the incoming and outgoing mappers.

Let's describe the flow for incoming mapping with the example of the Hubspot connector:

  • Here is the incoming attribute mapping as it looks when it is not filled in:

Screenshot_2019-09-16_at_12.19.52 (1).png

  • When you click on the Edit the mappingbutton, you get the following modal where you can select the incoming attributes which you want to add from the third party tool:


  • Then, by clicking out of the modal, you get back to the connector's settings with the auto-filled corresponding Hull attributes:


The flow is of the same kind for the outgoing mapping and we believe it is going to help you save a lot of time when you set-up your connectors.

Also, we added another element to the UI of the attribute mapper. Before, you could trigger errors by mismatching attributes types. Sometimes, you might match a string attribute with a boolean and that will trigger errors on your org. We are helping you avoid these kinds of errors by displaying the type of the attribute inside the dropdown as shown in the following screenshot:

Screenshot_2019-09-16_at_12.21.19 (1).png

Fetching Hubspot Email Events

Hey there,

We have a big announcement for Hubspot marketing users! We now enable Hull users to fetch a wide range of Hubspot marketing email events inside Hull. These events range from SENT events to CLICK events via PROCESSED events with all of their respective attached properties.

For more information on the events we are able to retrieve from your Hubspot Marketing org, please refer to the following doc of the Hubspot connectors 👉 Hubspot connector docs

This will allow you to create segments of users based on those events, or you can flatten those into attributes with the Hull Processor to be consumed by your other connectors.

Here is how it works on the Hubspot connector settings: email events.png

And how it looks like once you have ingested Hubspot marketing events inside Hull: hubspot_marketing_events_2.Png

Ingesting Salesforce Tasks as events inside Hull

Hey there,

It is now possible to ingest Salesforce tasks as events inside Hull. Tasks are native objects inside Salesforce that are used to improve the productivity of your Sales team.

By ingesting these tasks as events, you will be able to create segments of users based on whether they had a task attached to them inside Salesforce.

A standard use case with that new feature involves refining segments of users in Hull which are then sent out to marketing automation tools to trigger email campaigns.

Let's say a member of your sales team had a call with a given user 2 days ago. You want to exclude that user from a nurturing campaign because you do not want to be too pushy with your users. This call is often stored inside Salesforce as a task. By ingesting this task as an event inside Hull, you are going to be able to add a criteria to the segment that is sent out to your marketing automation tool for you nurturing campaign which will be something like did not have a task with a customer in the last 7 days. That way you can exclude these particular customers with whom you had recently contacted from your nurturing campaigns.

Here is the new section inside the connector to fetch tasks inside the Salesforce connector: Screenshot_2019-08-06_at_12.05.43 (1).png