JupiterOne Data Ingestion and Okta integrations and automations

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

Okta
  • New events
    Triggers when a new event is created in Okta
  • New events Real-time
    Triggers immediately when a new event is created in Okta
  • Scheduled event search using filter Batch
    Scheduled event search using filter in Okta

    • 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

Okta
  • Custom action
    Custom action in Okta (Custom)
  • Activate user
    Activate user in Okta
  • Add user to group
    Adds an existing user to a group in Okta
  • Create user
    Create user in Okta
  • Deactivate user
    Deactivate user in Okta
  • Delete user
    Delete user in Okta
  • Expire an existing user password
    Expire an existing user’s password in Okta
  • Get group members Batch
    Retrieves the list of members of a group in Okta
  • Get groups by name Batch
    Retrieves groups by name in Okta
  • Get user by ID
    Get user by ID in Okta
  • Get user groups Batch
    Get user groups in Okta
  • Get recent log on events by IP address Batch
    Get recent log on events by IP address in Okta
  • Get recent log on events by user Batch
    Get recent log on events by user in Okta
  • List applications assigned to user Batch
    List applications assigned to user in Okta
  • Remove user from group
    Removes an existing user from a group in Okta
  • Reset forgotten user password
    Reset an existing user’s forgotten password in Okta
  • Reset MFA factors for user
    Reset all MFA factors for an existing user in Okta
  • Reset user password
    Reset user password in Okta
  • Search Users Batch
    Search users in Okta
  • Suspend user
    Suspends an existing user in Okta
  • Unsuspend user
    Unsuspend an existing user in Okta
  • Update user
    Update user in Okta

    • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation