QUESTDB n8n INTEGRATION: AUTOMATE QUESTDB WITH N8N
Looking to automate QuestDB with n8n? You're in the right place. This integration lets you connect QuestDB—the high-performance time-series database—directly to your n8n workflows, enabling you to insert data and execute queries without writing a single line of backend code.
With the QuestDB n8n integration, you get access to 2 powerful actions that cover the essential database operations: inserting records and running custom SQL queries. Whether you're building real-time data pipelines, syncing IoT sensor data, or automating analytics workflows, this integration handles the heavy lifting.
In this guide, you'll discover exactly how to connect QuestDB to n8n, understand each available action in detail, and learn practical use cases to get the most out of this integration.
Need help automating Questdb with n8n?
Our team will get back to you in minutes.
Why automate Questdb with n8n?
The QuestDB n8n integration gives you access to 2 core actions that let you interact with your time-series database directly from any workflow. You can insert data into tables and execute custom SQL queries—all triggered by events from over 400 other applications in n8n's ecosystem.
Significant time savings: No more writing custom scripts or manually importing data into QuestDB. Set up workflows that automatically push data from webhooks, APIs, or other apps straight into your database tables. What used to require dedicated backend development now takes minutes to configure.
Seamless real-time data pipelines: Connect QuestDB to your entire tech stack. Receive data from IoT devices via MQTT, process it through n8n, and insert it directly into QuestDB. Or pull data from your CRM like HubSpot, transform it, and store it for time-series analysis. The possibilities are extensive.
Zero oversight on data operations: Your workflows run 24/7. Every time a specific event occurs—a form submission, an API call, a scheduled trigger—your data flows into QuestDB automatically. No manual intervention, no forgotten imports, no data gaps.
Concrete examples of what you can automate:
- IoT data ingestion: Automatically store sensor readings as they arrive
- Log aggregation: Push application logs into QuestDB for analysis
- Scheduled data sync: Run periodic queries and export results to other tools
- Real-time analytics pipelines: Insert transaction data as it happens for instant dashboards
How to connect Questdb to n8n?
! 1 stepHow to connect Questdb to n8n?
- 01
Add the node
The QuestDB n8n integration uses PostgreSQL wire protocol credentials to authenticate. QuestDB is compatible with PostgreSQL clients, which makes the connection straightforward in n8n.Basic configuration:Open your n8n workflow and add a QuestDB node from the node panelCreate new credentials: Click on "Credential to connect with" and select "Create New"Enter your QuestDB connection details: Provide your host address (e.g., localhost or your server IP), port (default is 8812 for PostgreSQL wire protocol), database name, username, and passwordTest the connection: n8n will verify that it can reach your QuestDB instanceSave and use: Once validated, your credentials are stored securely and available across all QuestDB nodes in your workflows
TIP💡 TIP: If you're running QuestDB locally for development, make sure the PostgreSQL wire protocol is enabled (it is by default on port 8812). For production deployments, always use secure connections and consider restricting access by IP. Store your credentials in n8n's credential manager rather than hardcoding them—this makes rotating credentials much easier down the line. For complex setups, check the n8n troubleshooting guide if you encounter connection issues.- 01
Need help automating Questdb with n8n?
Our team will get back to you in minutes.
Questdb actions available in n8n
01 Action 01Insert
The Insert action is your go-to for adding new records to QuestDB tables. It's designed for high-throughput data ingestion, which is exactly what QuestDB excels at as a time-series database.
Key parameters:
- Credential to connect with: A required dropdown to select your saved QuestDB connection credentials. This authenticates n8n with your database instance.
- Table: A required text field where you specify the exact name of the target table. Make sure the table already exists in QuestDB before running the workflow.
- Columns: A text field accepting a comma-separated list of column names (e.g.,
id,name,description). This defines which columns will receive data and must match the structure of your incoming data. - Return Fields: An optional text field to specify which columns should be returned after insertion. Use
*to retrieve all fields from the newly inserted row(s), or list specific columns.
Use cases:
- Insert IoT sensor readings from MQTT or HTTP webhooks into a time-series table
- Store form submissions from Typeform or Google Forms with timestamps
- Log API responses from external services for historical analysis
- Push processed data from previous workflow steps into QuestDB for storage
This action works best when you have structured, predictable data flowing through your workflow. Combine it with n8n's transformation nodes to format data before insertion.
02 Action 02Execute Query
The Execute Query action gives you full control over your QuestDB interactions. Run any valid QuestDB SQL query—SELECT statements for data retrieval, aggregations for analytics, or even administrative commands.
Key parameters:
- Credential to connect with: A required dropdown to select your QuestDB account credentials for authentication.
- Operation: A required dropdown currently set to "Execute Query", indicating the module is configured to run a database query.
- Query: A required multi-line text field where you enter your QuestDB SQL query. This accepts any valid SQL that QuestDB supports, from simple SELECT statements to complex aggregations.
- Additional Fields: An optional section for adding extra configuration properties if needed.
Use cases:
- Retrieve recent data with
SELECT * FROM sensors WHERE timestamp > dateadd('h', -1, now()) - Run aggregations like
SELECT avg(temperature), max(temperature) FROM sensors SAMPLE BY 1h - Clean up old data with scheduled deletion queries
- Check table structure or run diagnostic queries
Pro tip: Combine Execute Query with n8n's scheduling trigger to create automated reporting workflows. Run a query every hour, format the results, and send them to Discord or email. You can also chain queries—use one Execute Query node to fetch data, transform it, then use another node to act on the results.
Build your first workflow with our team
Drop your email and we'll send you the catalog of automations you can ship today.
- Free n8n & Make scenarios to import
- Step-by-step setup docs
- Live cohort + community support
Frequently asked questions
Is the QuestDB n8n integration free?
Yes, the QuestDB integration is included natively in n8n at no additional cost. If you're using n8n's self-hosted version (open-source), you have unlimited access to all QuestDB actions. For n8n Cloud users, the integration is available on all plans, but execution limits depend on your subscription tier. QuestDB itself is also open-source and free to run, making this a cost-effective stack for time-series data workflows. The only potential costs are infrastructure (if hosting on cloud servers) and n8n Cloud subscription fees if you choose the managed option.What data can I sync between QuestDB and n8n?
You can insert any structured data into QuestDB tables and retrieve any data through SQL queries. This includes time-series data like sensor readings, metrics, logs, financial ticks, and event streams. The Insert action accepts data from any n8n node—HTTP requests, webhooks, API responses, file imports, or outputs from other integrations like Airtable or Google Sheets. The Execute Query action returns query results as JSON objects that you can process, filter, or send to any other application in your workflow. Essentially, any data that fits into QuestDB's column types (timestamps, numbers, strings, symbols) can flow through this integration.How long does it take to set up the QuestDB n8n integration?
Initial setup typically takes 5-10 minutes. You'll need a running QuestDB instance with the PostgreSQL wire protocol enabled (default on port 8812), your connection credentials, and an existing table structure. Once credentials are configured in n8n, adding QuestDB nodes to workflows takes seconds. The most time-consuming part is usually designing your data model and queries, not the integration itself. If you're already familiar with QuestDB's SQL dialect, you can have a working workflow in under 15 minutes from scratch. For more complex automation scenarios, explore our downloadable automation catalog for inspiration.
