JupiterOne Data Ingestion and Password Pusher integrations and automations

Seamlessly connect JupiterOne Data Ingestion and Password Pusher. Automate workflows, and boost efficiency with Workato.

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…

Password Pusher
  • New Push Created
    New push in PWPush
  • New Request Created
    New request in PWPush
  • Request Responded
    Request responded in PWPush

    • Any other trigger you can think up

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

Password Pusher
  • Close Request
    Close a request in PWPush
  • Create Push
    Create a push in PWPush
  • Create Request
    Create a request in PWPush
  • Expire Push
    Expire a push in PWPush
  • Get Push
    Get a push from PWPush
  • Get Push Audit Log
    Get audit log for a push in PWPush
  • Get Request
    Get a request from PWPush
  • Get API Version
    Get version info from PWPush
  • List Active Pushes
    List active pushes in PWPush
  • List Active Requests
    List active requests in PWPush
  • List Expired Pushes
    List expired pushes in PWPush
  • Preview Push
    Preview a push in PWPush
  • Respond to Request
    Respond to a request in PWPush

    • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation