Exact Online and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Actions

Do this…

Exact Online

Create customer
Create customer
Create logistics item
Create logistic item
Create project
Create project
Create time transaction
Create a project time transaction
Create time transaction basic
Create time transaction (basic: alle GUIDs handmatig, geen picklists)
Delete customer
Delete customer
Delete logistics item
Delete logistic item
Delete sales invoice
Delete sales invoice
Get customers
Get customers
Get financial transactions
Get financial transactions
Get gl accounts
Get GL Accounts
Get logistics items
Get logistics items
Get project wbs
Get project WBS
Get projects
Get projects
Get sales invoice lines
Get sales invoice lines
Get sales invoices
Get sales invoices
Get time transactions
Get project time transactions
List employees
List employees (active) – let op: endpoint kan ontbreken in sommige tenants
List employees for project basic
List employees allowed on a project (basic)
List project members
List project members allowed to book time
List projects basic
List projects (basic: ID, Code, Description)
List time items
List time items
List time items basic
List time items (basic: ID, Code, Description)
Make api request
Make API request to Exact Online
Update customer
Update customer
Update logistics item
Update logistic item
Update project
Update project
Update time transaction
Update a project time transaction

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