Skip to content

PostgreSQL List Tables

Lists all tables available in a specified PostgreSQL schema. It uses a database URI to connect through the configured data connector service and returns a human-readable table list along with the raw JSON response.
Preview

Usage

Use this node when you need to discover or enumerate tables within a specific PostgreSQL schema prior to querying data or building visual queries. Typical workflows include schema exploration, building dropdowns for table selection, and pre-validating table names before composing queries.

Inputs

FieldRequiredTypeDescriptionExample
credentials_pathTrueSTRINGDatabase connection URI for PostgreSQL. Must be a valid URI specifying host, port, database, and credentials. Optionally include query parameters (e.g., schema, sslmode).postgresql://postgres:@db.example.com:5432/mydb?sslmode=require
timeoutTrueINTMaximum time in seconds to wait for the service request to complete.60
schemaTrueSTRINGPostgreSQL schema name to list tables from.public

Outputs

FieldTypeDescriptionExample
resultSTRINGHuman-readable summary listing the tables found in the specified schema.Tables in schema 'public' (3 tables): - users - orders - products
json_resultSTRINGJSON string of the raw service response containing the tables.{"tables": ["users", "orders", "products"]}
html_tableSTRINGHTML output (not used by this node; returns empty string).
xlsx_dataSTRINGBase64-encoded XLSX export (not used by this node; returns empty string).
pdf_dataSTRINGBase64-encoded PDF export (not used by this node; returns empty string).

Important Notes

  • Credentials URI required: The credentials_path must be a valid PostgreSQL URI (e.g., postgresql://user:@host:port/db).
  • Service configuration: The node depends on the PostgreSQL data connector service being configured and reachable via the platform’s ENDPOINTS settings.
  • Schema scope: Only tables within the provided schema are returned. If the schema is empty or incorrect, the result may be an empty list.
  • Output formats: This node returns only text and JSON; HTML, XLSX, and PDF outputs are intentionally empty strings.
  • Security: Never embed real credentials in shared workflows. Use secured secrets or environment-managed values.

Troubleshooting

  • Invalid credentials URI: If you see an error about the credentials URI, ensure it starts with postgresql:// and includes host, port, database, and proper encoding for special characters in username/password.
  • Service URL not configured: Errors indicating missing service URL mean the PostgreSQL connector endpoint is not set in ENDPOINTS. Contact an administrator to configure it.
  • Timeouts: Increase the timeout input if listing large schemas or when the connector service is under load.
  • Empty result: If no tables are returned, verify the schema name, user permissions on that schema, and that you’re connecting to the intended database.
  • Authentication/SSL issues: For SSL-required environments, include sslmode in the URI (e.g., sslmode=require). Verify that username/password are correct.