Google Calendar and JupiterOne Data Ingestion integrations and automations

Seamlessly connect Google Calendar 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…

Google Calendar
  • Event end
    Event end in Google Calendar
  • Event start
    Event start in Google Calendar
  • New event Real-time
    New event in Google Calendar
  • New/updated event Real-time
    New/updated event in Google Calendar

    • Any other trigger you can think up

Actions

Do this…

Google Calendar
  • Custom action
    Custom action in Google Calendar (Custom)
  • Add attendees to an event Batch
    Add list of attendees to an event in Google Calendar
  • Create all day event
    Create all day event in Google Calendar
  • Create calendar
    Create calendar in Google Calendar
  • Create event
    Create event in Google Calendar
  • Create task
    Create task in Google Calendar
  • Delete attendees from an event Batch
    Delete list of attendees from an event in Google Calendar
  • Delete event
    Delete an event in Google Calendar
  • Get calendar by ID
    Get calendar by ID in Google Calendar
  • Get event by ID
    Get event by ID in Google Calendar
  • List calendars
    List calendars in Google Calendar
  • Search events Batch
    Search events in Google Calendar
  • Update event
    Update event in Google Calendar
  • Update task
    Update task in Google Calendar

    • 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