Chart Mogul and JupiterOne Data Ingestion integrations and automations

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

Actions

Do this…

Chart Mogul
  • Cancel customer subscription
    Cancel a Subscription in ChartMogul
  • Create customer
    Create Customer in ChartMogul
  • Create invoice
    Create Invoice with line items in ChartMogul
  • Create plan
    Create Plan in ChartMogul
  • Create transaction
    Create Transaction in ChartMogul
  • Get MRR
    Get MRR in ChartMogul
  • Get customer
    Get Customer in ChartMogul
  • Get customer churn count
    Get number of customer churns in ChartMogul
  • Get customer count
    Get number of customers in ChartMogul
  • Get invoices by customer
    Get Invoices by customer in ChartMogul
  • Get subscription by customer
    Get Subscription by customer in ChartMogul
  • Search plan
    Search Plan in ChartMogul
  • Update customer
    Update Customer in ChartMogul

    • 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