Adeona PIM and JupiterOne Data Ingestion integrations and automations

Seamlessly connect Adeona PIM and JupiterOne Data Ingestion. 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…

Adeona PIM
  • New deleted product
    New deleted product in Adeona PIM
  • New record
    New record in Adeona PIM
  • New record Batch
    New record in Adeona PIM
  • New/updated record
    New/updated record in Adeona PIM
  • New/updated record Batch
    New/updated record in Adeona PIM

    • Any other trigger you can think up

Actions

Do this…

Adeona PIM
  • Custom action
    Custom action in Adeona PIM (Custom)
  • Search records using Scroll API
    Search records using Scroll API in Adeona PIM
  • Create records in batch Batch
    Create record (batch) in Adeona PIM
  • Delete records in batch Batch
    Delete record (batch) in Adeona PIM
  • Update records in batch Batch
    Update record (batch) in Adeona PIM
  • Create record
    Create record in Adeona PIM
  • Download file by ID
    Download file by ID in Adeona PIM
  • Finish a job
    Finish a job in Adeona PIM
  • Get record
    Get record in Adeona PIM
  • Search records
    Search records in Adeona PIM
  • Start a job
    Start a job in Adeona PIM
  • Update record
    Update record in Adeona PIM
  • Upload file contents
    Upload file contents in Adeona PIM

    • Any other action you can think up

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

One platform

  • Power
  • Agility
  • Speed
  • Innovation