Contentstack and JupiterOne Data Ingestion との統合と自動化

Contentstack and JupiterOne Data Ingestionを他のツールとシームレスに接続。 ワークフローを自動化し、業務効率を向上させます。

評価

4.9

事前構築済み

150+

統合

合計

100+

アクティブユーザー

平均

2分

接続まで

カスタム接続

利用可能

HTTPコネクター経由で利用可能

主要企業が Workato を活用

  • monday.svg
  • box.svg
  • hp-2.svg
  • atlassian.svg
  • cisco.png

強力なワークフローを迅速に構築

Triggers

When this happens…

Contentstack
  • New record
    New record in Contentstack
  • New record in batch
    New record in batch in Contentstack
  • New/updated record
    New/updated record in Contentstack
  • New/updated record in batch
    New/updated record in batch in Contentstack

    • Any other trigger you can think up

Actions

Do this…

Contentstack
  • Search records using custom query
    Search records using custom query in Contentstack
  • Custom action
    Custom action in Contentstack
  • Get record details by ID
    Get record in Contentstack
  • Publish entries (Bulk)
    Publish an Entries (Bulk) in Contentstack
  • Publish entry
    Publish an Entry in Contentstack
  • Search records
    Search records in Contentstack

    • 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

単一のプラットフォーム

  • 強力
  • 俊敏性
  • スピード
  • 革新