Aircall and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Actions

Do this…

Aircall

Custom action
Custom action in Aircall (Custom)
Add a User in a Team
Add a User in a Team in Aircall
Create a Tag
Create a Tag in Aircall
Create a Team
Create a Team in Aircall
Create a User
Create a User in Aircall
Delete a Tag
Delete a Tag in Aircall
Delete a Team
Delete a Team in Aircall
Delete a User
Delete a User in Aircall
Remove a User from a Team
Remove a User from a Team in Aircall
Retrieve Company information
Retrieve Company information in Aircall
Find User
Find User in Aircall
List all Tags
List all Tags in Aircall
List all Teams
List all Teams in Aircall
List all Users
List all Users in Aircall
Retrieve a Tag.
Retrieve a Tag. in Aircall
Retrieve details of a specific Team.
Retrieve details of a specific Team. in Aircall
Retrieve a User Detail with ID
Retrieve a User Detail with ID in Aircall

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