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…
PostgreSQL
- New rowNew row in a table in PostgreSQL
- New rows BatchNew batch of rows in a table in PostgreSQL
- New/updated rowNew/updated row in a table in PostgreSQL
- New/updated rows BatchNew/updated batch of rows in a table in PostgreSQL
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
PostgreSQL
- Delete rows BatchDelete rows in a table in PostgreSQL
- Export query resultExport query result as a CSV file in PostgreSQL
- Insert rowInsert row in a table in PostgreSQL
- Run custom SQL BatchRun custom SQL in PostgreSQL
- Run long query using custom SQLRun long query using custom SQL in PostgreSQL
- Select rows BatchSelect rows in a table in PostgreSQL
- Select rows using custom SQL BatchSelect rows using custom SQL in PostgreSQL
- Get table schemaGet table schema for PostgreSQL
- Update rowsUpdate rows in a table in PostgreSQL
- Upsert rows BatchUpsert batch of rows in a table in PostgreSQL
Any other action you can think up
One platform
- Power
- Agility
- Speed
- Innovation
