Integration & Metadata

Automate integrates with Veeva via API and can be triggered regardless of how documents enter the system.

The automation process is ingestion-agnostic. Whether documents are manually uploaded, submitted through an integration, received via an inbox, or sent by email, Automate can trigger the appropriate API workflow once the document is loaded.

This design ensures flexibility in deployment and allows automation to operate consistently across all document intake channels.

Processing is ingestion-agnostic and does not require a separate repository.

Regardless of how documents enter the system, whether uploaded manually, received through an integration, submitted via the Veeva Inbox, or sent by email, the automation workflow can be triggered from any intake method. Once the document is available within the environment, the API can initiate processing without requiring relocation to another platform.

This is entirely customizable based on your preferences. While Automate can extract 35+ pieces of metadata from each document, most organizations typically expect to fill only 5-6 different metadata fields in their front end (such as process zone, section, artifact, document type, site, country, study, document dates, ICF type, and protocol number).

Common Approach: Automate returns only the fields that are currently enabled in your Veeva system, while all other extracted data is sent back and can be stored for reporting purposes. However, an emerging trend shows that customers are now expanding the data displayed in their front end since automation eliminates the workload concern.

Usually we only return fields that are enabled in your configuration; everything else is returned as JSON you can store/pull as a report. Some are expanding optional front-end fields since it doesn’t add workload.