JupiterOne Data Ingestion and ServiceM8 integrations and automations

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

ServiceM8
  • Contact created
    Contact created in ServiceM8
  • Job activity created
    Job activity created in ServiceM8
  • Material created
    Material created in ServiceM8
  • Staff created
    Staff created in ServiceM8
  • Job quoted
    Job quoted in ServiceM8
  • Client updated
    Client updated in ServiceM8
  • Job updated
    Job updated in ServiceM8

    • 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

ServiceM8
  • Add job
    Add job in ServiceM8
  • Add job material
    Add job material to a job in ServiceM8
  • Create material
    Create material in ServiceM8
  • Add staff
    Add new staff in ServiceM8
  • Create client
    Create client in ServiceM8
  • Create contact
    Create contact in ServiceM8
  • Get client details by UUID
    Get client details in ServiceM8
  • Get job by UUID
    Get job in ServiceM8
  • Get job materials by job/UUID Batch
    Get job materials in ServiceM8
  • Get staff by UUID
    Get staff in ServiceM8
  • Search client
    Search client in ServiceM8
  • Search contact Batch
    Search contact in ServiceM8
  • Search job activities Batch
    Search job activities in ServiceM8
  • Search materials
    Search materials in ServiceM8
  • Search staff Batch
    Search staff in ServiceM8
  • Update client
    Update client in ServiceM8
  • Update contact
    Update contact in ServiceM8
  • Update job
    Update job in ServiceM8
  • Update material
    Update material in ServiceM8

    • Any other action you can think up

One platform

  • Power
  • Agility
  • Speed
  • Innovation