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…
Actions
Do this…
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
Thriva
- Custom actionCustom action in (Custom)
- Acknowledge an escalationThis endpoint is used to acknowledge that you have received an escalation for a Result Set. You will need the Escalation ID. It is very important that you only acknowledge an Escalation once the result set has been manually acknowledged by a member of your team.
- Create an OrderCreate an Order
- Fetch a TestFetch a Test by ID
- Fetch an OrderFetch an Order by ID
- Fetch a Fulfillment OrderFetch a Fulfillment Order by it's ID
- Fetch OrdersLists all of your orders
- Fetch a ResultFetch Result By ID
- Fetch ResultsLists all of your results
- Fetch a Test for an OrderFetch a Test for an Order
- Biomarker APIFetch Test in Zuora
- Fetch TestsLists all of your tests
Any other action you can think up
One platform
- Power
- Agility
- Speed
- Innovation
