Rating
4.9
Pre-built
150+
integrations
Total
100+
active users
avg
2 min
to connect
Custom Connections
Available
via HTTP connector
Build Powerful Workflows, fast
Triggers
When this happens…
NetSuite REST
- New classification recordNew classification record in NetSuite
- New custom recordNew custom record in NetSuite
- New standard recordNew record in NetSuite
- New or updated custom recordNew or updated custom record in NetSuite
- New or updated standard recordNew or updated standard record in NetSuite
Any other trigger you can think up
Actions
Do this…
JupiterOne Data Ingestion
- Abort Sync JobAborts an active sync job, discarding all uploaded data. Use this to cancel a job that should not be finalized.
- Bulk Delete EntitiesSends a bulk delete request for entities within an active sync job. Provide an array of objects containing entity _id values to delete.
- Create Integration InstanceCreates a new custom integration instance for use with the Sync API. Returns the instance ID needed for starting sync jobs.
- Finalize Sync JobFinalizes 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 JobStarts 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 BatchUploads 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 BatchUploads 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 BatchUploads 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
NetSuite REST
- Custom actionCustom action in NetSuite REST (Custom)
- Attach contact to a recordAttach contact to a record in NetSuite
- Attach file to a recordAttach file to a record in NetSuite
- Create a recordCreate a record in NetSuite
- Create records (async) BatchCreate multiple records records in NetSuite asynchronously
- Delete a recordDelete a record in NetSuite
- Delete records (async) BatchDelete multiple records records in NetSuite asynchronously
- Detach contact from a recordDetach contact from a record in NetSuite
- Detach file from a recordDetach file from a record in NetSuite
- Execute RESTlet scriptExecute RESTlet script in NetSuite
- Execute SuiteQL query BatchExecute SuiteQL query in NetSuite
- Get async job resultGet the status and result of an asynchronous job in NetSuite
- Get a record by IDGet a record by ID in NetSuite
- Initialize recordInitialize Record by referencing Record in NetSuite
- Search records BatchSearch records in NetSuite
- Transform recordTransform Record to Record in NetSuite
- Update a recordUpdate a record in NetSuite
- Update records (async) BatchUpdate multiple records records in NetSuite asynchronously
- Upsert a recordUpsert a record in NetSuite
- Upsert records (async) BatchUpsert multiple records records in NetSuite asynchronously
Any other action you can think up
One platform
- Power
- Agility
- Speed
- Innovation
