GitHub and JupiterOne Data Ingestion integrations and automations

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

GitHub
  • Closed issue
    Closed issues in Github
  • New issue
    New issue in Github
  • New or updated issue Real-time
    New or updated issues in GitHub
  • New or updated milestone Real-time
    New or updated milestone in GitHub
  • New or updated pull request Real-time
    New or updated pull request in GitHub
  • New PR
    New PR in Github
  • New updated issue comment Real-time
    New/updated issue comment in GitHub

    • Any other trigger you can think up

Actions

Do this…

GitHub
  • Custom action
    Custom action in GitHub (Custom)
  • Create comment in an issue
    Create comment in an issue in GitHub
  • Create issue
    Create issue in Github
  • Get issue or PR details
    Get issue or PR details in GitHub
  • List statuses for a ref Batch
    List statuses for a Ref in GitHub
  • Search issues/pull requests Batch
    Search issues/pull requests in Github
  • Update issue
    Update issue in Github

    • Any other action you can think up

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

One platform

  • Power
  • Agility
  • Speed
  • Innovation