Rating
4.9
Pre-built
150+
integrations
Total
100+
active users
avg
2 min
to connect
Custom Connections
Available
via HTTP connector
Build Powerful Workflows, fast
Triggers
When this happens…
BuildXact
- New Event Recieved from BuildXact Real-timeNew Event in BuildXact
Any other trigger you can think up
Actions
Do this…
BuildXact
- Custom actionCustom action in BuildXact (Custom)
- Accept Incoming Integration ConnectionAccept Incoming Integration Connection in Build xact
- Add Access Control to CatalogueAdd Access Control to Catalogue in Build xact
- Create New CatalogueCreate New Catalogue in Build xact
- Delete CatalogueDelete Catalogue in Build xact
- Fetch Catalogue DetailsFetch Catalogue Details in Build xact
- Get Incoming Integration ConnectionGet Incoming Integration Connection in Build xact
- List Catalogues BatchList Catalogues in Build xact
- Reject Incoming Integration ConnectionReject Incoming Integration Connection in Build xact
- Import Catalogue Items BatchImport Catalogue Items in Build xact
- Start Catalogue ImportStart Catalogue Import in Build xact
Any other action you can think up
JupiterOne Data Ingestion
- Abort Sync JobAborts an active sync job, discarding all uploaded data. Use this to cancel a job that should not be finalized.
- Bulk Delete EntitiesSends a bulk delete request for entities within an active sync job. Provide an array of objects containing entity _id values to delete.
- Create Integration InstanceCreates a new custom integration instance for use with the Sync API. Returns the instance ID needed for starting sync jobs.
- Finalize Sync JobFinalizes 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 JobStarts 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 BatchUploads 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 BatchUploads 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 BatchUploads 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
