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…
SafetyCulture
- Action events Real-timeTrigger for Action events
- Inspection events (Deprecated) Real-timeTrigger for Inspection events (Deprecated)
- Inspection events Real-timeTrigger for Inspection events
- Issue events Real-timeTrigger for Issue events
- Media events Real-timeTrigger for Media events
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
SafetyCulture
- ActionsInteract with Actions in SafetyCulture
- AppsInteract with Apps in SafetyCulture
- AssetsInteract with Assets in SafetyCulture
- Bulk user operationsInteract with Bulk user operations in SafetyCulture
- CompaniesInteract with Companies in SafetyCulture
- CredentialsInteract with Credentials in SafetyCulture
- Data FeedsInteract with Data Feeds in SafetyCulture
- Directory (Sites)Interact with Directory (Sites) in SafetyCulture
- DocumentsInteract with Documents in SafetyCulture
- Heads UpInteract with Heads Up in SafetyCulture
- InspectionsInteract with Inspections in SafetyCulture
- IntegrationsInteract with Integrations in SafetyCulture
- InvestigationsInteract with Investigations in SafetyCulture
- IssuesInteract with Issues in SafetyCulture
- Lone WorkerInteract with Lone Worker in SafetyCulture
- MediaInteract with Media in SafetyCulture
- OSHAInteract with OSHA in SafetyCulture
- Response SetsInteract with Response Sets in SafetyCulture
- SchedulesInteract with Schedules in SafetyCulture
- Schedules (legacy)Interact with Schedules (legacy) in SafetyCulture
- SensorsInteract with Sensors in SafetyCulture
- StructuresInteract with Structures in SafetyCulture
- Template DefinitionInteract with Template Definition in SafetyCulture
- TemplatesInteract with Templates in SafetyCulture
- TrainingInteract with Training in SafetyCulture
- UsersInteract with Users in SafetyCulture
- GroupsInteract with Groups in SafetyCulture
- Custom ActionCustom action in SafetyCulture
Any other action you can think up
One platform
- Power
- Agility
- Speed
- Innovation
