JupiterOne Data Ingestion and Veeva Vault integrations and automations

Seamlessly connect JupiterOne Data Ingestion and Veeva Vault. Automate workflows, and boost efficiency with Workato.

Rating

4.9

Pre-built

150+

integrations

Total

100+

active users

avg

2 min

to connect

Custom Connections

Available

via HTTP connector

Market leaders run on Workato

  • monday.svg
  • box.svg
  • hp-2.svg
  • atlassian.svg
  • cisco.png

Build Powerful Workflows, fast

Triggers

When this happens…

Veeva Vault
  • New/updated document
    New/updated document in Veeva Vault
  • New/updated record (scheduled VQL)
    New/updated record in Veeva Vault

    • Any other trigger you can think up

Actions

Do this…

JupiterOne Data Ingestion
  • Abort Sync Job
    Aborts an active sync job, discarding all uploaded data. Use this to cancel a job that should not be finalized.
  • Bulk Delete Entities
    Sends a bulk delete request for entities within an active sync job. Provide an array of objects containing entity _id values to delete.
  • Create Integration Instance
    Creates a new custom integration instance for use with the Sync API. Returns the instance ID needed for starting sync jobs.
  • Finalize Sync Job
    Finalizes a sync job, triggering the JupiterOne backend to process and apply all uploaded entities and relationships to the graph. Call this after all upload actions are complete.
  • Start Sync Job
    Starts a new synchronization job. Use source "integration-external" with an integration instance ID (scope is derived from the instance). Use source "api" with an explicit scope value (no integration instance). Returns the job ID needed for uploading data and finalizing.
  • Upload Combined Batch
    Uploads a batch of entities and/or relationships to an active sync job in a single API call. At least one of entities or relationships must be provided.
  • Upload Entities Batch
    Uploads a batch of entities to an active sync job. Recommended batch size: 250-500 entities per call. Each entity requires _key, _type, _class, and displayName at minimum.
  • Upload Relationships Batch
    Uploads a batch of relationships to an active sync job. Recommended batch size: 250-500 per call. IMPORTANT: Only works with DIFF sync mode, not PATCH. Each relationship requires _key, _type, _class, _fromEntityKey, and _toEntityKey.

    • Any other action you can think up

Veeva Vault
  • Custom action
    Custom action in Veeva Vault (Custom)
  • Bulk delete records Batch
    Bulk delete records in Veeva Vault
  • Bulk upsert records Batch
    Bulk upsert records in Veeva Vault
  • Create document relationship
    Create document relationship in Veeva Vault
  • Create document version
    Create document version in Veeva Vault
  • Create record
    Create record in Veeva Vault
  • Delete record
    Delete record in Veeva Vault
  • Download document rendition
    Download document rendition in Veeva Vault
  • Get document
    Get document in Veeva Vault
  • Get record
    Get record in Veeva Vault
  • Run VQL query
    Run VQL query in Veeva Vault
  • Search audit trail
    Search audit trail in Veeva Vault
  • Search records
    Search records in Veeva Vault
  • Update record
    Update record in Veeva Vault
  • Upload document
    Upload document in Veeva Vault
  • Upsert record
    Upsert record in Veeva Vault

    • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation