Cloud Sign and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Cloud Sign

契約が完了 Real-time
New completed 契約 in CloudSign
契約が却下・取り消し Real-time
New rejected/cancelled 契約 in CloudSign

Any other trigger you can think up

Actions

Do this…

Cloud Sign

書類に宛先を追加
Add participant to document in CloudSign
書類に共有先を追加
Add reportee to document in CloudSign
書類を作成
Create 書類 in CloudSign
書類にファイルを添付
Create ファイル in CloudSign
Custom action
Custom action in CloudSign
合意締結証明書をダウンロード
Download 合意締結証明書 in CloudSign
ファイルをダウンロード
Download ファイル in CloudSign
書類情報を取得
Get 書類情報 in CloudSign
書類を取得
Get 書類 in CloudSign
書類を検索
Search for 書類 in CloudSign
書類を送信またはリマインド
Send document in CloudSign
書類情報を更新
Update 書類情報 in CloudSign

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