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…
Lightspeed Commerce
- New consignmentNew consignment in Lightspeed Commerce
- New/updated customerNew/updated customer in Lightspeed Commerce
- New inventory recordNew inventory record in Lightspeed Commerce
- New/updated productNew/updated product in Lightspeed Commerce
- New saleNew sale in Lightspeed Commerce
- New/updated consignmentNew/updated consignment in Lightspeed Commerce
- New/updated inventory recordNew/updated inventory record in Lightspeed Commerce
- New/updated saleNew/updated sale in Lightspeed Commerce
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
Lightspeed Commerce
- Custom actionCustom action in Lightspeed Commerce (Custom)
- Add payment to register saleAdd payment to register sale in Lightspeed Commerce
- Create customerCreate customer in Lightspeed Commerce
- Create productCreate product in Lightspeed Commerce
- Create register saleCreate register sale in Lightspeed Commerce
- Get customer details by IDGet customer details in Lightspeed Commerce
- Get sale details by IDGet sale details in Lightspeed Commerce
- Search customers BatchSearch customers by code or email in Lightspeed Commerce
- Search product BatchSearch product in Lightspeed Commerce
- Update customerUpdate customer in Lightspeed Commerce
- Update productUpdate product in Lightspeed Commerce
Any other action you can think up
One platform
- Power
- Agility
- Speed
- Innovation
