Ashby and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Ashby

Application changed stage Real-time
Application state changed in Ashby
Application submitted Real-time
Application submitted in Ashby
Candidate hired Real-time
Candidate hired in Ashby
New/Updated interview schedule Real-time
New/Updated interview schedule in Ashby
New/Updated offer Real-time
An offer in Ashby
Offer deleted Real-time
Deleted offer in Ashby
Published/Unpublished job posting Real-time
A job posting in Ashby
Survey submitted Real-time
Survey submitted in Ashby

Any other trigger you can think up

Actions

Do this…

Ashby

Custom action
Custom action in Ahsby (Custom)
Change application stage
Change application stage in Ahsby
Create application
Consider candidate for a job in Ahsby
New candidate
Create new candidate in Ahsby
New candidate note
Create new candidate note in Ahsby
Search candidates
Search candidates in Ahsby
Search job
Search job in Ahsby
Search user
Search user in Ahsby
Transfer application
Transfer application in Ahsby
Update candidate
Update candidate in Ahsby

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