JupiterOne Data Ingestion and Pipefy integrations and automations

Seamlessly connect JupiterOne Data Ingestion and Pipefy. 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…

Pipefy
  • New card Real-time
    New card in Pipefy
  • Deleted card Real-time
    Deleted card in Pipefy
  • Card done Real-time
    Card done in Pipefy
  • Card expired Real-time
    Card expired in Pipefy
  • Updated card Real-time
    Updated card in Pipefy
  • Card late Real-time
    Card late in Pipefy
  • Moved card Real-time
    Moved card in Pipefy
  • Card overdue Real-time
    Card overdue in Pipefy
  • New record Real-time
    New record in Pipefy
  • Record done Real-time
    Record done in Pipefy
  • Updated record Real-time
    Updated record in Pipefy
  • Record overdue Real-time
    Record overdue in Pipefy

    • 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

Pipefy
  • Custom action
    Custom action in Pipefy (Custom)
  • Create card
    Create Card in Pipefy
  • Create record
    Create a Database record in Pipefy
  • Delete card
    Delete card in Pipefy
  • Delete record
    Delete record in Pipefy
  • Get a card by ID
    Get a card by ID in Pipefy
  • Get cards by field
    Get cards by field in Pipefy
  • Get cards by phase
    Get cards by phase in Pipefy
  • Get cards by title
    Get cards by title in Pipefy
  • Get a record by ID
    Get a record by ID in Pipefy
  • Get records
    Get records in Pipefy
  • Get records by field
    Get records by field in Pipefy
  • Move card
    Move card in Pipefy
  • Update card
    Update card in Pipefy
  • Update record
    Update record in Pipefy

    • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation