Rating

4.9

Pre-built

150+

integrations

Total

100+

active users

avg

2 min

to connect

Custom Connections

Available

via HTTP connector

Market leaders run on Workato

  • monday.svg
  • box.svg
  • hp-2.svg
  • atlassian.svg
  • cisco.png

Build Powerful Workflows, fast

Triggers

When this happens…

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

Thriva
  • Custom action
    Custom action in (Custom)
  • Acknowledge an escalation
    This 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 Order
    Create an Order
  • Fetch a Test
    Fetch a Test by ID
  • Fetch an Order
    Fetch an Order by ID
  • Fetch a Fulfillment Order
    Fetch a Fulfillment Order by it's ID
  • Fetch Orders
    Lists all of your orders
  • Fetch a Result
    Fetch Result By ID
  • Fetch Results
    Lists all of your results
  • Fetch a Test for an Order
    Fetch a Test for an Order
  • Biomarker API
    Fetch Test in Zuora
  • Fetch Tests
    Lists all of your tests
  • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation