POSTGRES n8n INTEGRATION: AUTOMATE POSTGRES WITH N8N

The Update action modifies existing records in your Postgres tables based on specified criteria. It's essential for workflows that need to maintain data accuracy by keeping database records in sync with external systems.

Key parameters:

• Credential to connect with: Required dropdown for selecting the Postgres account credentials used to connect to your database.
• Operation: Set to "Update" to modify existing records rather than creating new ones.
• Schema: Required dropdown specifying the database schema (typically "public"). Supports both list selection and expression-based dynamic configuration.
• Table: Required dropdown to identify which table contains the records you want to update.

Beyond these core parameters, you'll configure which columns to update and specify WHERE conditions to target the correct records.

Use cases:

• Update order status when shipping confirmation arrives from logistics partners
• Sync contact information changes from your CRM to your data warehouse
• Mark tasks as complete when webhook notifications arrive
• Update inventory counts after processing sales transactions

When to use it: Choose Update when you know the records already exist and you need to modify specific fields. For scenarios where records might or might not exist, the Insert or Update action provides a safer approach.

The Select action retrieves data from your Postgres tables, making it essential for workflows that need to read database information before processing it further. Whether you're building notification systems, generating reports, or syncing data to other platforms, Select is often your starting point.

Key parameters:

• Credential to connect with: Required dropdown to authenticate with your Postgres database. Select your pre-configured credentials here.
• Operation: Set to "Select" to retrieve data from your database.
• Schema: Required field specifying which schema contains your target table. Defaults to "public" and supports both dropdown selection and expressions for dynamic configuration.
• Table: Required dropdown to select the specific table you want to query. Additional configuration options let you filter results, limit returned rows, and specify columns.

Use cases:

• Fetch customer records to personalize email campaigns
• Check inventory levels before processing orders
• Pull analytics data for Slack digest notifications
• Validate data existence before performing other operations

When to use it: Use Select whenever your workflow needs to read data from Postgres. It's particularly powerful when combined with n8n's IF node to create conditional logic based on query results—for example, only sending a notification if a certain record exists.

The Insert or Update action (also known as "upsert") is a smart operation that automatically decides whether to create a new record or update an existing one. It checks for the existence of a record based on a unique key and acts accordingly—eliminating the need for separate existence checks in your workflows.

Key parameters:

• Credential to connect with: Required dropdown to select your Postgres account credentials for database authentication.
• Operation: Set to "Insert or Update" to enable the upsert behavior.
• Schema: Required dropdown specifying the database schema. Supports "From list" selection with "public" as the common default, or dynamic expressions.
• Table: Required dropdown to select the target table for the upsert operation.

Additional configuration includes specifying the unique column(s) used to determine if a record already exists.

Use cases:

• Sync CRM contacts where you want to update existing records or create new ones automatically
• Process webhook data that might contain new or updated information
• Build idempotent workflows that can safely be re-run without creating duplicates
• Maintain user profiles that get updated with each new interaction

When to use it: Insert or Update is the safest choice when you're not certain whether records already exist. It's particularly valuable for sync workflows where data flows continuously and you need to handle both new and existing records gracefully.

The Insert action allows you to add new records to any table in your Postgres database. It's the go-to action for data ingestion workflows where you're capturing information from other applications and storing it in your database.

Key parameters:

• Credential to connect with: Required dropdown for selecting your Postgres account credentials. The screenshot shows "Postgres account" selected.
• Operation: Set to "Insert" to create new records in your target table.
• Schema: Required dropdown to specify the database schema. Defaults to "public" but supports any schema in your database. You can select from a list or use an expression for dynamic schema selection.
• Table: Required dropdown to choose the specific table for insertion. Supports both fixed selection from a list and dynamic expressions.

Use cases:

• Capture form submissions from Typeform or Google Forms and store them in Postgres
• Log webhook events from Stripe, GitHub, or other services for auditing
• Sync new CRM contacts to your analytics database in real-time
• Build data collection pipelines that aggregate information from multiple sources

When to use it: The Insert action is ideal when you're certain you're adding new records. If you might need to update existing records based on a unique identifier, consider the Insert or Update action instead.

The Execute Query action is the most flexible option in the Postgres n8n integration. It lets you run any custom SQL statement against your database, giving you complete control over complex operations that go beyond simple CRUD actions.

This action is perfect for advanced use cases: running aggregate queries for reporting, executing stored procedures, performing complex JOINs across multiple tables, or handling any SQL operation that doesn't fit neatly into the predefined actions.

Key parameters:

• Credential to connect with: Required dropdown to select your pre-configured Postgres account credentials. This authenticates n8n's connection to your database.
• Operation: Set to "Execute Query" to enable custom SQL execution.
• Query: A multiline text field where you enter your SQL statement. This accepts any valid PostgreSQL syntax—SELECT, INSERT, UPDATE, DELETE, or even DDL statements.
• Options: Expandable section for advanced settings, including query parameters for secure variable passing.

Use cases:

• Run complex reporting queries that aggregate data across multiple tables
• Execute stored procedures or functions defined in your database
• Perform bulk operations with custom WHERE clauses
• Build dynamic queries using n8n expressions to inject values safely

When to use it: Choose Execute Query when the predefined actions don't cover your needs, or when you need maximum flexibility. However, for standard operations like inserting or updating single records, the dedicated actions are often simpler to configure.

💡 TIP: Always use query parameters (available in the Options section) when passing dynamic values into your SQL. This prevents SQL injection attacks and ensures your workflows remain secure even when processing untrusted input data.

The Delete action removes records from your Postgres tables based on specified criteria. While powerful, it should be used carefully in automated workflows to avoid unintended data loss.

Key parameters:

• Credential to connect with: Required dropdown to select the Postgres account credentials for authentication.
• Operation: Set to "Delete" to remove records from your database.
• Schema: Required dropdown to specify the database schema containing your target table. Supports list selection ("public" is common) or expression-based input.
• Table: Required dropdown to identify which table contains the records to be deleted.

You'll also configure WHERE conditions to specify exactly which records should be removed.

Use cases:

• Automatically purge old log entries or temporary data after a retention period
• Remove canceled orders or deleted users from your database
• Clean up test data in staging environments
• Implement GDPR data deletion requests automatically

When to use it: Use Delete for cleanup operations and data lifecycle management. Always test your WHERE conditions thoroughly before enabling automated deletion workflows in production, and consider implementing soft deletes (marking records as deleted rather than removing them) for critical data.

💡 TIP: Before implementing Delete in production workflows, consider adding a confirmation step or logging mechanism. You might route records to an archive table first, or send a summary to Slack before permanent deletion—giving you a safety net if something goes wrong. For similar database integrations, explore our MySQL n8n integration guide.