Hello Sign and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Actions

Do this…

Hello Sign

Add user access to template
Add user access to template in HelloSign.
Add user to team
Invite a user to your team in HelloSign.
Cancel signature request
Cancel an incomplete signature request in HelloSign.
Create record
Create record in HelloSign
Custom action
Custom action in HelloSign
Delete record
Delete record in HelloSign
Get record details
Get specific details of record in HelloSign
Remove signature request access
Remove signature request access in HelloSign.
Remove user access to template
Remove user access to template in HelloSign.
Remove user to team
Remove a user from team in HelloSign.
Search records
Search for records in HelloSign
Send signature request
Send a signature request with the submitted documents in HelloSign.
Send signature request reminder
Send a signature request reminder in HelloSign.
Send signature request with template
Send a signature request based off a template in HelloSign.
Update record
Update record in HelloSign

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