Run transaction

postgres.transaction executes 1–100 statements on one connection between BEGIN and COMMIT. PostgreSQL rolls the complete transaction back after the first failure.

Example

automations/create-order.automation.ts

import { automation, onHttpRequest } from "automate.ax"
import { postgres } from "automate.ax/postgres"
import { z } from "zod"

export default automation("Create order", () => {
  const request = onHttpRequest({
    body: z.object({
      customerId: z.string(),
      orderId: z.string(),
      quantity: z.number().int().positive(),
      sku: z.string(),
    }),
    scope: "automation",
  })

  postgres.transaction({
    statements: [
      {
        sql: "insert into orders (id, customer_id) values ($1, $2)",
        parameters: [request.body.orderId, request.body.customerId],
      },
      {
        sql: "update inventory set available = available - $1 where sku = $2",
        parameters: [request.body.quantity, request.body.sku],
      },
    ],
  })
})

Inputs

Input	Type	Required	Default	Description
`statements`	`PostgresStatement[]`	Yes	None	1–100 statements executed in order.
Second argument: `{ account }`	`string \| IntegrationAccountReference<"postgres">`	No	Project default	Connected PostgreSQL database.

Each statement contains one non-empty sql string and optional (JsonValue | bigint | Date | Uint8Array)[] parameters. Transaction-control statements such as BEGIN, COMMIT, ROLLBACK, and SAVEPOINT are rejected because the action owns the transaction boundary.

Output

Returns { results }. results contains one command, rowCount, rows, and fields envelope per statement in input order.

Permissions, failures, and retries

The connected role needs the union of the exact database privileges required by every statement. The first PostgreSQL failure stops execution and rolls back earlier changes. If rollback itself fails, the action reports both failures. This action is not replay-safe. A connection loss during COMMIT can leave transaction resolution unknown, so Automate.ax does not repeat the transaction automatically. Use durable business keys and constraints when a caller may retry the automation.

Built-in triggers

Built-in actions

Runtime utilities

Integrations

Example

Inputs

Output

Permissions, failures, and retries

​Example

​Inputs

​Output

​Permissions, failures, and retries

Example

Inputs

Output

Permissions, failures, and retries