Once you connected to your Salesforce instance using the credentials button inside the overview of the Salesforce connector, you can start pushing data out to Salesforce.
Hull gives you that granular control over the Users that you want to push out.
So first, select the Segments of Users that you want to sync as Leads inside Salesforce. To do so, use the Lead filter
dropdown inside the Users - Sending Leads to Salesforce
section.
Hull also gives you the flexibility of sending any type of attributes inside Salesforce. That is what you can do by mapping attributes on the User inside Hull with fields on the Lead inside Salesforce. You can do so by using the attribute mapper inside the Lead Outgoing Fields
section.
Then, you can use the dropdown called Overwrite
on the right to define if you want the attribute from Hull to take precedence over the field inside Salesforce.
If you select no
, it means that if some value is already set inside of Salesforce, Hull won't overwrite it. As a result, a manual change from one of your salespeople will take precedence over the mapped Hull attribute inside the Salesforce connector.
You can choose to send a concatenated list of the segments a given User belongs to inside the field of the corresponding Lead inside Salesforce.
Like above, you can choose to send a concatenated list of the Account Segments a given User belongs to inside the field of the corresponding Lead inside Salesforce.
In the Salesforce connector, Hull can retrieve the list of assignment rules created by your sales team inside Salesforce. You can choose to apply one of these assignment rules to leads when either creating or updating them
the lead assignment rule when creating a lead
the lead assignment rule when updating a lead
Hull gives you that granular control over the Users that you want to push.
So first, select the Segments of Users that you want to sync as Contacts inside Salesforce. To do so, use the Contact filter
dropdown inside the Users - Sending Contacts to Salesforce
section.
☝️ If a given user is in both Lead and Contact segments, it will be treated as a contact.
Hull also gives you the flexibility of sending any type of attributes inside Salesforce. That is what you can do by mapping attributes on the User inside Hull with fields on the Contact inside Salesforce. You can do so by using the attribute mapper inside the Contact Outgoing Fields
section.
Then, you can use the dropdown called Overwrite
on the right to define if you want the attribute from Hull to take precedence over the field inside Salesforce.
If you select no
, it means that if some value is already set inside of Salesforce, Hull won't overwrite it. As a result, a manual change from one of your salespeople will take precedence over the mapped Hull attribute inside the Salesforce connector.
You can choose to send a concatenated list of the segments a given user belongs to inside the field of the corresponding Contact inside Salesforce.
Like above, you can choose to send a concatenated list of the Account Segments a given User belongs to inside the field of the corresponding Contact inside Salesforce.
Hull gives you that granular control over the Accounts that you want to push out.
So first, select the Segments of Accounts that you want to sync as Accounts inside Salesforce. To do so, use the Account filter
dropdown inside the Accounts - Sending to Salesforce
section.
Hull also gives you the flexibility of sending any type of attributes inside Salesforce. That is what you can do by mapping attributes on the Account inside Hull with fields on the Account inside Salesforce. You can do so by using the attribute mapper inside the Account Outgoing Fields
section.
Then, you can use the dropdown called Overwrite
on the right to define if you want the attribute from Hull to take precedence over the field inside Salesforce.
If you select no
, it means that a manual change from one of your salespeople will take precedence over the mapped Hull attribute inside the Salesforce connector.
You can choose to send a concatenated list of the segments a given account belongs to inside the field of the corresponding Account inside Salesforce.
Hull's Salesforce connector gives you the ability to transform any kind of events captured by Hull into a Task inside Salesforce. These can be any events like email opened
, user signed-up
or opened a conversation
that you can convert into Tasks to ping your salespeople directly inside Salesforce.
To do so, go to the section of the Salesforce connector called Events - Sending Events as Tasks to Salesforce
.
First, you need to select 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. If that field is ever removed or updated after a Task has been exported to Salesforce, the Task will be imported back into Hull as a separate and new event, given that `Fetch Tasks’ is turned on
In your Salesforce connector settings, select your newly created unique, external id field as the Salesforce External ID
. Usually, the event_id
which is auto-generated by Hull will be a good identifier.
3. Specify which events you would like to send to Salesforce and the type of Task to create. The type of Task must be a valid type, given your Task Type field configuration.