Databases
PostgreSQL Database
Connect PostgreSQL to power the Object Store agent: create, query and bulk-update object instances, run aggregate queries, and save agent memory.
01 / Workflows
What you can automate.
The PostgreSQL connection stores a database URL and powers the Object Store agent. It supports instance CRUD, bulk operations, aggregates, existence checks, and conversation memory persistence.
- Create, query, update, and delete object model instances.
- Run bulk inserts, updates, deletes, and aggregate queries.
- Load and save AI agent memory by conversation ID.
02 / Capabilities
What it covers.
The full reference, with connection types, is in the PostgreSQL Database docs.
Capabilities
- Create and query instances
- Update and delete instances
- Bulk create, update, and delete
- Check existence and create-if-not-exists
- Aggregates
- Load and save memory
Data handled
- Object records
- Aggregate rows
- Conversation memory
03 / Availability
In every edition.
PostgreSQL Database is a standard integration, included in Cloud, Enterprise and the open-source engine. Compare plans
- Open-source engineAGPL-3.0, run and operate it yourself.Included
- CloudWe host and manage your instance.Included
- EnterpriseYour cloud or on-premises, supported by our team.Included
04 / Questions
Common questions.
Is PostgreSQL Database included in my plan?
Yes. PostgreSQL Database is a standard integration, included in Cloud, Enterprise and the open-source engine.
How is it set up?
A connection stores the PostgreSQL Database credentials once for your instance. Workflow steps that use it declare that connection, and the runtime denies anything else.
Can a person approve before anything is written?
Yes. A workflow holds an exception for approval and continues only after the person decides. The run keeps the source, the decision, who made it, and the response together.
Put PostgreSQL Database to work.
Start with a paid pilot of one real process. Our team builds and runs it, live in two weeks once access is in place.
All product names, logos and brands are the property of their respective owners and are used here in good faith, only to identify the systems Runtara connects to. Their use does not imply any affiliation with, or endorsement or sponsorship by, those owners.