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.

Screenshot_2019-10-21_at_15.14.22.png

  • 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.

Screenshot_2019-10-21_at_15.14.51.png

  • 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:

Screenshot_2019-10-29_at_17.09.04.png

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:

ignore_deleted_contact.png

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:

Screenshot_2019-09-16_at_12.20.19.png

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

Screenshot_2019-09-16_at_12.20.38.png

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

New use cases page on the website

Hey there,

We are very proud to announce that we have released a new page to our website, called the use cases page.

Many of you pointed out that you wanted to be shown more use cases that you could implement in Hull. Many of you come with a specific use case in mind when they start using Hull. But some of you may miss on several other use cases that may be a great fit with their current stack. Or perhaps we've grown a bit since you joined us. Either way, we want you to be able to see all of the hard problems that we can help you solve.

On the use cases page, you will find a list of use cases that you can filter by type: notifications, onboarding, marketing, and more! On this page, use cases are described from a high-level standpoint; showing the connectors involved and the business impact.

Screenshot 2019-09-27 at 13.04.33.png

When you click on one of these use cases, you will find more details about the contexts in which you can apply that use case, how to start implementing the use case, what connectors are used, and what roles in your company they may serve. See an example below:

Screenshot 2019-09-27 at 13.04.57.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.png

New settings section for Hubspot, Salesforce, Segment, Intercom and Mailchimp

Hey there,

We have updated the settings sections of some of our connectors, including Hubspot, Salesforce, Segment, Intercom and Mailchimp.

You can see an example here with a side by side comparison of the settings of the Intercom connector:

Below screenshots showing before and after the updates on the settings design:

Screenshot_2019-07-16_at_11.12.56.pngScreenshot_2019-07-16_at_11.10.59.png

The reasons for these changes are the following:

  • The related settings fields are now grouped together in sections in grey to emphasize their logical relationships.
  • Each setting section now has a description to embed documentation and other helpful tips.
  • The settings sections are now arranged in the order that the connector should be configured.
  • The navigation bar on the left helps you jump to a particular section of the settings page.
  • With these settings, we introduce better designed, bigger and more robust form components.