Learn the basics how to setup connectors
This article covers the basics of setting up connectors in Hull. For specific guidance please refer to the documentation of the individual connector.
Determine which users or accounts are sent to the external service
Most connectors allow you to control which users or accounts are being sent from Hull to an external service by determining whitelisted segments. Segments are either defined as global filter, or if the connector supports multiple objects for every type:
Define which attributes and/or events are sent to the external service
You have already seen how to narrow down which objects are sent to external services, now it is time to refine what attributes or events are being sent. This additional level enables a more fine-grain control of the data flow.
Most connectors allow you to map a Hull attribute to a service attribute for the outgoing data flow:
Hull will now only send the listed attributes to the third party system; please refer to the documentation of the specific connector to verify the particular behavior.
Define what attributes Hull receives from an external system
Connectors that support a two-way sync with an external system allow you to specify which attributes or fields you want to fetch from this system. Most connectors do have a simple list of fields while some allow you to specify an explicit mapping:
All received attributes will be displayed as a group in the user profile. This allows you to easily see from which system this data has been received: