JupiterOne Data Ingestion and Microsoft Dynamics 365 integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Microsoft Dynamics 365

Export new records
Export new records in Microsoft Dynamics 365
Export new/updated records
Export new/updated records in Microsoft Dynamics 365
Deleted object
Deleted object in Microsoft Dynamics 365
Monitor changes in entities
Monitor all changes in entities in Microsoft Dynamics 365
Monitor changes in entities Batch
Monitor all changes in entities in Microsoft Dynamics 365
New object
New object in Microsoft Dynamics 365
New or updated object (batch) Batch
New or updated object (batch) in Microsoft Dynamics 365
New or updated object
New or updated object in Microsoft Dynamics 365
New object Real-time
New object in Microsoft Dynamics 365
Scheduled object search Batch
Scheduled object search in Microsoft Dynamics 365
New/updated object Real-time
New/updated object in Microsoft Dynamics 365

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

Microsoft Dynamics 365

Custom action
Custom action in Microsoft Dynamics 365 (Custom)
Close case
Close case in Microsoft Dynamics 365
Create object
Create object in Microsoft Dynamics 365
Create object Batch
Create object in Microsoft Dynamics 365
Get object by ID
Get object by ID in Microsoft Dynamics 365
Get object schema
Get object schema from Microsoft Dynamics 365
Search objects Batch
Search objects in Microsoft Dynamics 365
Update object
Update object in Microsoft Dynamics 365
Update object Batch
Update object in Microsoft Dynamics 365

Any other action you can think up

One platform

Power
Agility
Speed
Innovation