Complete EDI Solutions and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Actions

Do this…

Complete EDI Solutions

Parse EDI Document
Parse EDI Document into container for EDI Data in Complete EDI
Create EDI Document from JSON
Create EDI document from JSON in Complete EDI
Create EDI Document from JSON (Streaming)
Create EDI document from JSON in Complete EDI
Create EDI Document From XML
Create EDI Document From XML in Complete EDI
Create JSON Document From EDI
Create JSON formatted EDI Document from raw EDI data in Complete EDI
Process EDI File
Send Raw EDI File to Complete EDI for processing into JSON
Download Processed EDI File
Download JSON formatted EDI Document from Complete EDI server
Create EDI Acknowledgement
Create an EDI acknowledgment from EDI input in Complete EDI
Split Raw EDI Document
Split Raw EDI Document into individual EDI transactions in Complete EDI
Send JSON File Via SFTP
Translate a JSON File to Raw EDI and send via SFTP in Complete EDI

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