Basecamp 2 and JupiterOne Data Ingestion integration | Workato

Market leaders run on Workato

Build Powerful Workflows, fast

Triggers

When this happens…

Basecamp 2

Access granted to calendar
Calendar access granted to person in Basecamp 2
New calendar event
New calendar event in Basecamp 2
New person event
New person event in Basecamp 2
New project
New project in Basecamp 2
New project calendar event
New project calendar event in Basecamp 2
New project event
New project event in Basecamp 2
New to-do
New to-do in Basecamp 2
New to-do list
New to-do list in Basecamp 2
Access granted to project
Project access granted to person in Basecamp 2

Any other trigger you can think up

Actions

Do this…

Basecamp 2

Custom action
Custom action in Basecamp 2 (Custom)
Create calendar event
Create calendar event in Basecamp 2
Create new project
Create new project in Basecamp 2
Create project calendar event
Create project calendar event in Basecamp 2
Create new todo
Create new to-do in Basecamp 2
Create new to-do list
Create new to-do list in Basecamp 2
Search calendars
Search for a calendar in Basecamp 2
Search persons
Search for a person in Basecamp 2
Search projects
Search for a project in Basecamp 2

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