Execute Query
Infoveave Data Automation — Database
Write the query once. Run it automatically in every workflow execution.
Every reporting and ETL pipeline depends on SQL queries to filter, join, and reshape data. Execute Query brings that power directly into the Infoveave workflow canvas — no scripting environment required. Connect to any supported database, write your SQL, and the activity returns a structured result set that flows into the next pipeline step. When you need to generate report files, enable Save As File to export query results as encrypted, formatted Excel or CSV outputs split by any column in the result.
What Execute Query does
Execute parameterized SQL queries on connected databases and file-based sources inside your Infoveave workflow. Filter, join, and aggregate data — then export results as a structured table or encrypted file.
Part of Infoveave Data Automation on the Unified Data Platform.
When to use Execute Query
- You need to read or filter data from a connected database or file-based source as a workflow step
- Your pipeline requires joining, aggregating, or reshaping data using SQL before downstream processing
- You need to generate structured output files from query results — split by region, department, or category
- You are building ETL pipelines that pull from SQL-compatible sources at regular schedule intervals
When to avoid it
- You need to insert or update rows in a database — use Insert into Database or Update Rows instead
- You are querying a REST API or OData endpoint — use Execute API or Retrieve OData
- Your data transformation only requires no-code column operations — use the Transformations library instead
Where it fits in your Infoveave automation
Execute Query is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Execute Query
Real scenarios where this transformation saves hours of manual work.
Regional Sales Report Generation
A scheduled workflow executes a parameterized SQL query on the sales database to retrieve transactions by region and month. With Split by Column set to Region and Save As File enabled, separate encrypted Excel files are generated for each regional manager — fully automated on the first of every month.
Inventory Snapshot for Replenishment
A daily inventory workflow queries the warehouse management system database to pull current stock levels for all SKUs below the reorder threshold. The result flows into a transformation step that calculates order quantities before loading into the procurement system.
Production Log Extraction
A shift-end workflow executes a SQL query on the MES database to extract all production events from the last 8 hours. Results feed into OEE calculation transformations and load into the shop floor analytics dashboard.
See Execute Query in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
prod-postgres-dbSELECT * FROM SalesData WHERE Region = 'East' AND Month = '2026-03'trueRegionSales_Report_{Region}_{Date}SalesDataInput Data
| (connected data source — no row input required) |
Output Data
| Name | Product | Region | Revenue |
|---|---|---|---|
| John | Laptop | East | 1200 |
| Alice | Printer | East | 400 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Connection
The registered database or file-based data source connection. Supports PostgreSQL, MySQL, MSSQL, Azure SQL, and other SQL-compatible sources configured in the Studio connections panel.
Query
The SQL query to execute. Supports parameterized queries using workflow variables. Use SELECT, JOIN, WHERE, GROUP BY, and all standard SQL constructs supported by the connected database.
Save As File
When enabled, query results are saved as a structured file (Excel, CSV) rather than passed as an in-memory table to the next activity. Required when the downstream step expects a file rather than tabular data.
Split by Column
Column whose distinct values are used to generate a separate output file per value. For example, setting Split by Column to 'Region' with five distinct regions generates five individual files — one per region.
Secret Key
Optional encryption key that password-protects the generated output file. Available only when Save As File is enabled. Used to meet data security requirements for file distribution.
Frequently asked questions
Everything you need to know about Execute Query in Infoveave.
Also in Database — and what runs before & after
Transformations in the same family as Execute Query, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Execute Query is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
