Eletive and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Actions

Do this…

Eletive

Create User
Create a new user
Create Users (Bulk)
Create Users Bulk
Delete User
Delete user by ID
Get Schemas
Retrieve SCIM schemas
Get Service Provider Config
Retrieve SCIM service provider configuration
Get User
Get a user by ID
List all Users (Slim)
Fetch all SCIM users
List Users
Get all users with optional filters
Patch User
Partially update user
Patch Users (Bulk)
Patch Users Bulk
Update User (Replace)
Replace a user.

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