Jira and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Jira

Deleted object Real-time
Deleted object in Jira
Export new issues in Jira
Export new issues in Jira
Export new/updated issues in Jira
Export new/updated issues in Jira
New event Real-time
New event in Jira
New issue
New issue in Jira
New issue Batch
New issue in Jira
New/updated comment Real-time
New/updated comment in Jira
Updated issue
Updated issue in Jira
Updated issue Batch
Updated issue in Jira
New/updated issue Real-time
New/updated issue in Jira
New/updated worklog Real-time
New/updated worklog in Jira

Any other trigger you can think up

Actions

Do this…

Jira

Custom action
Custom action in Jira (Custom)
Assign user to issue
Assign user to issue in Jira
Create comment
Create comment for issue in Jira
Create issue
Create issue in Jira
Create user
Create user in Jira
Get user details
Get user in Jira
Download attachment
Download attachment from issue in Jira
Get changelog of an issue
Get changelog of an issue in Jira
Get issue
Get issue details from Jira
Get issue comments Batch
Get list of issue comments for issue in Jira
Get issue schema
Get issue schema for Jira
Search assignable users Batch
Search assignable users for issue in Jira
Search issues Batch
Search issues in Jira
Search issues by JQL Batch
Search issues by JQL in Jira
Update comment
Update comment for issue in Jira
Update issue
Update issue in Jira
Update issue status
Update status of issue in Jira
Upload attachment
Upload attachment to issue in Jira

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