TIMESCALEDB n8n INTEGRATION: AUTOMATE TIMESCALEDB WITH N8N

The Update action modifies existing records in your TimescaleDB tables based on a unique key. Use this when you need to change values in already-stored data—updating statuses, correcting entries, or syncing changes from external systems back into your database.

Key parameters:

• Credential to connect with: A required dropdown for selecting your TimescaleDB account credentials.
• Schema: A required text field for the database schema (typically "public").
• Table: A required text field specifying which table contains the records to update.
• Update Key: A required text field defining the column used to identify which records to modify (e.g., "id"). This acts as your WHERE clause reference.
• Columns: A required text field with comma-separated column names that will be updated (e.g., "name,description,status").
• Return Fields: An optional field to specify which columns should be returned after the update completes.
• Additional Fields: Optional advanced properties for complex update scenarios.

Practical use cases:

• Update order statuses when shipping providers send webhook notifications
• Sync customer profile changes from your CRM back into TimescaleDB
• Mark sensor alerts as "resolved" when acknowledgment events arrive
• Update inventory quantities when stock movements are recorded in external systems

Pro tip: Combine the Update action with a preceding database query or API call to dynamically fetch the update key values. This lets you build workflows that first identify which records need updating, then apply the changes in sequence.

The Insert action allows you to add new records directly into any TimescaleDB table from your n8n workflow. This is your go-to operation for feeding data into your time-series database—whether it's sensor readings, user events, transaction logs, or any other data that needs to be stored.

Key parameters:

• Credential to connect with: A required dropdown to select your configured TimescaleDB account credentials for authentication.
• Schema: A required text field specifying which database schema contains your target table. Defaults to "public" for most standard setups.
• Table: A required text field where you enter the exact name of the destination table.
• Columns: A required text field accepting a comma-separated list of column names (e.g., "id,name,description,timestamp") indicating which columns will receive data.
• Return Fields: An optional field specifying which columns to return after insertion. Use "*" for all fields or list specific columns.
• Additional Fields: An optional section for advanced configurations like conflict handling or SQL-specific clauses.

Practical use cases:

• Insert IoT sensor data from MQTT webhooks into a hypertable for time-series analysis
• Log user activity events from your application into TimescaleDB for behavioral analytics
• Store payment transaction records from PayPal n8n integration for financial reporting
• Archive form submissions from Typeform or Google Forms into structured database tables

This action pairs perfectly with n8n's scheduling capabilities—set up a workflow that pulls data from an API every 5 minutes and inserts it into TimescaleDB for continuous data collection.

The Execute Query action gives you full SQL flexibility within your n8n workflows. When Insert and Update aren't enough, this action lets you run any valid SQL statement against your TimescaleDB instance—complex SELECTs, JOINs, aggregations, or even DDL commands if your credentials permit.

Key parameters:

• Credential to connect with: A required dropdown to select your TimescaleDB account credentials.
• Query: A required text area where you write the SQL query to execute. This accepts any valid PostgreSQL/TimescaleDB SQL syntax.
• Additional Fields: Optional section for advanced configurations or query parameters.

Practical use cases:

• Run aggregation queries to calculate daily averages from time-series data and send reports via email
• Execute TimescaleDB-specific functions like time_bucket() for downsampling data within workflows
• Perform complex JOINs across multiple tables to enrich data before sending it to external services
• Run scheduled maintenance queries like continuous aggregate refreshes or data retention policies
• Query recent data to check thresholds and trigger alerts when values exceed limits

This action is particularly powerful for analytics workflows. For example, you could schedule a daily workflow that runs SELECT time_bucket('1 hour', time) AS bucket, AVG(temperature) FROM sensors WHERE time > NOW() - INTERVAL '24 hours' GROUP BY bucket and sends the results to Discord or stores them in a Google Sheet for stakeholder review.

When to use it: Choose Execute Query when you need read operations (SELECT), complex multi-table operations, TimescaleDB-specific functions, or any SQL that goes beyond simple INSERT/UPDATE. It's your escape hatch to the full power of SQL within visual automation workflows.