Appbricx
Docs
FeaturesPricingStart free

Get started

OverviewWhat Appbricx isQuickstart with a coding agentQuickstart with the builderCore concepts

Guides

Data and tablesAccess and rolesBusiness rulesSign-inCustom screensRealtime and topicsWorkflows, schedules and webhooksServer functionsAI in your appPaymentsFilesMessagesIntegrationsVerifyPublishing, domains and rollbackOperating your appExport and self-hostSelf-host install

Tutorials

Build a booking app with Claude CodeMulti-user todo listClient portalSlack on new sign-upTemplates

Reference

Reference homeFrontend SDKHTTP APIMCP toolsCLIIntegrations catalogContract formatAI key resolutionRun Appbricx locally

PostgreSQL

Run queries, insert, update, and delete rows in a PostgreSQL database.

Data and storageCredentials form1 actionAll integrations

On this page
  1. Connect
  2. Call it from a workflow
  3. Actions (1)
  4. run-query
  5. Env keys
  6. Details

Connect

Auth type: Credentials form (custom_auth). Fill in the fields the provider needs (listed below). They are stored encrypted in the vault.

FieldTypeDescription
hostrequiredtextDatabase server hostname or IP address
portrequiredtextDatabase server port (default 5432)
userrequiredtextDatabase username
passwordrequiredsecretDatabase password
databaserequiredtextDatabase name to connect to
  • In the editor: Backend panel, Integrations tab, then Connect. This connects it for the project.
  • For every project in a workspace: Workspace settings, Integrations.
  • Owners and admins choose which integrations members may connect in the admin panel (Integrations tab), and can attach their own OAuth app there.

Call it from a workflow

Pass the action name and its input. The call resolves with { success, output, error? }; a missing connection resolves with success false and the reason. See ctx.integrations.invoke and ctx.integrations.call.

Native workflow
// .workflow.js (native ctx)
export async function run(ctx) {
  const res = await ctx.integrations.invoke("postgres", "run-query", {
    "query": "<query>"
  });
  if (!res.success) throw new Error(res.error);
  ctx.log.info("PostgreSQL answered", { output: res.output });
}
defineWorkflow module
// defineWorkflow module (@app/sdk ctx)
import { defineWorkflow } from "@app/sdk";

export default defineWorkflow({
  id: "postgres-run-query",
  name: "PostgreSQL: Run Query",
  description: "Calls PostgreSQL when a row is created.",
  trigger: { type: "entity_event", entity: "tickets", event: "created" },
  async run(ctx, event) {
    const res = await ctx.integrations.call("postgres", {
      "action": "run-query",
      "query": "<query>"
    }) as { success: boolean; error?: string };
    if (!res.success) throw new Error(res.error);
  },
});
From an app (connector proxy)
curl -X POST "$APP_ORIGIN/__appbricx/connector-proxy/postgres/run-query" \
  -H "Authorization: Bearer $APP_KEY" \
  -H "content-type: application/json" \
  -d '{"props":{"query":"<query>"}}'

Actions

run-queryin catalog

Run Query. Run Query

Also accepted as run_query.

InputTypeDescription
queryrequiredtextPlease use $1, $2, etc. for parameterized queries to avoid SQL injection.
argsoptionalarrayArguments to be used in the query
query_timeoutoptionalnumberAn integer indicating the maximum number of milliseconds to wait for a query to complete before timing out.
connection_timeout_msoptionalnumberAn integer indicating the maximum number of milliseconds to wait for a connection to be established before timing out.
application_nameoptionaltextA string indicating the name of the client application connecting to the server.

Env keys

When connected, these credential fields are exposed to the project's runtime as environment variables (PostgreSQL database connection.). Server keys never reach the browser.

VariableFieldWhere
PGHOSThostserver only
PGPORTportserver only
PGDATABASEdatabaseserver only
PGUSERuserserver only
PGPASSWORDpasswordserver only

Details

Id
postgres
Category
Data and storage
Tags
database, sql, relational, open-source
Package
@activepieces/piece-postgres@0.2.3
Tier
Built in

On this page

  1. Connect
  2. Call it from a workflow
  3. Actions (1)
  4. run-query
  5. Env keys
  6. Details
Appbricx

The backend, runtime and hosting for apps your coding agent builds. On our cloud, in yours, or on your own servers.

Features

Coding agents and MCPVerify testingBuilder consolePostgres databaseData APIRealtimeRow-level securitySign-in and authPaymentsWorkflows and jobsAI in your appIntegrationsBackups and rollbackHosting and domainsSelf-host and exportAll features

Product

ShowcasePricingFor coding agentsTemplatesPrivate cloudBring your own AI keyFAQ

Compare

Appbricx vs SupabaseLovable alternativeBolt alternativeFor freelancersFor agencies

Resources

DocumentationReferenceBlogSupportContact

© 2026 Appbricx. All rights reserved.

TermsPrivacyCookiesAcceptable Use