Veeva
Veeva connections give you access to your company’s pharmaceutical and life science applications data.
Source Setup
To set up a connection, you need a Vault domain name, username, and password to allow Etleap to authenticate with Veeva. You need to setup a unique connection in ETleap for separate Vault Objects. Check out the What Data is Available? section below for a list of supported Vault objects.
- The Vault Domain Name is the same domain that you use to access the Veeva application (e.g., etleap-vault.veevavault.com in the screenshot below).

-
The Veeva Vault Type is the kind of Veeva product that your instance uses, see the Vault Type section below for supported types.
-
The username and password are the same that you use to log into your Veeva application.
Prefer using an API? Go here and select Veeva under the Body header to start creating a connection via API.
Vault Types
During connection setup, specify the Veeva Vault type that you will use for the connection. Each Vault type contains entities unique to that type. Etleap currently supports the following Vault types:
What Data is Available?
Update-Mode Deletes Support
Deletes are supported for update-mode entities with this connector.
You can create Veeva pipelines from all queryable Vault Objects available in your account. Etleap ensures only valid entity resources are listed based on your Vault Type.
Etleap determines the pipeline mode for an entity based on whether the modified_date__v
field is present in the object. If the object includes this field, the pipeline will operate in Update Mode. In the absence of this field, the pipeline will default to Replace Mode.
The sole exception to this rule is the Workflows entity. It uses Append Mode by default. There is a variation of Workflows, called Workflow Tasks, which operates in Update Mode. This mode utilizes the task_last_modified_date__v
column to track updates.
Key Considerations
- Veeva has a field type called “Picklist” which is returned as an array from the API. Picklist fields are automatically parsed as subtables and will be loaded as separate tables in your destination. Etleap automatically assigns the default primary key to each subtable to map it to the main parent table.
- Audit Trails entities can only return data from 30 days ago. To avoid extraction errors Etleap will start querying data from 29 days and 23 hours ago.