Unify Automations
Logo
Analytics by UnifyApps

Analytics by UnifyApps

Analytics by UnifyApps enables comprehensive data analysis and reporting capabilities.

Overview

Analytics by UnifyApps enables comprehensive data analysis and reporting capabilities. You can aggregate metadata, run SQL queries against the analytics store, query automation execution logs with LogQL, bulk-load files into analytics tables, and export reports (CSV, XLS or XLSX; SQL query results can also be exported as TSV) for generating insights, performance monitoring, and data-driven decision-making.

Screenshot 2026-08-27 at 18.57.05 1.png
Screenshot 2026-08-27 at 18.57.05 1.png

SQL vs LogQL

The SQL actions (Execute Analytics SQL Query, Export SQL Query Result, Execute Analytics SQL Update Query) run against the analytics store — your Storage objects or Platform data. The LogQL actions (Create LogQL Query, Execute LogQL Query) run against automation execution logs, and are used to read node-level variables from automation runs.

Use Cases

  1. Customer Segmentation Analysis — Run analytics queries to group customers by location or purchase history using aggregation functions to identify key demographics and tailor marketing efforts.

  2. Multi-Source Data Integration — Aggregate data from various sources using SQL queries to join tables and identify patterns and correlations.

  3. Automated Quarterly Budget Reports — Finance teams automate quarterly budget report generation by setting time ranges and defining projections, exporting summarized financial data in XLSX format.

  4. Retrieving Metadata for Specific Fields — Gather detailed metadata for fields such as Customer_Name, Customer_Age, and Customer_Location using the Aggregate Metadata action.

Aggregate Metadata

The Aggregate Metadata action retrieves detailed metadata for data fields within a specific object, providing insights into field properties such as sortability, filterability, searchability, and updateability.

Input Fields:

  • Group — Select between Storage or Platform to determine data context

  • Base Report — Choose the object to query for metadata

  • Add ID — Specify the field name for metadata extraction

  • Query — Enter a partial field name to retrieve related metadata (e.g., entering "Cus" returns fields like Customers_Profile)

  • Page — Configure pagination with Offset and Limit

  • Sortable — Enable to retrieve sortable fields

  • Filterable — Enable to retrieve filterable fields

Output includes: Aggregation Field Type, Display Name, Entity Type, Field Type, Sortable, Filterable, and Searchable properties, Updatable status, Name Field indicator.

Analytics Query

The Analytics Query action fetches, processes, and analyzes data from a selected base report with powerful querying capabilities including grouping, filtering, and projecting data.

Input Requirements:

  1. Select Group — Choose Platform or Storage

  2. Select Base Report — Choose the base report object

  3. Select Projections — Choose fields and apply aggregation functions (Count, Sum, Min/Max, Percentage Contribution)

  4. Select Additional Projections — Add supplementary projections

  5. Time Range — Define a time field with start and end times including previous periods for comparison

  6. Filter — Create conditions using fields and values to filter data efficiently

  7. Search Object — Specify fields and their values to narrow down results

  8. Pagination — Use Offset and Limit to manage retrieved records

  9. Sorting — Add fields to sort results by specific attributes

  10. Include Total Count — Set to true for retrieving total count of matching records

Example base report: Node Level Reporting

Node-level reporting provides 35 distinct metrics for tracking execution details, including: Id, Execution Instance Id, Root and Parent Execution Instance Ids, Trigger Instance Id, Workflow, Workflow Version, Deployed Workflow, Concurrent Execution, Current Node details (name, app name, resource name, connection ID), Next and Previous Node, Entry/Resume/Exit timestamps, Status (RUNNING, COMPLETED, FAILED), Wait Time, Retry Count, Successful/Failed/Total Runs Count, Application Id, Cache Hit, Input/Output (PII), State, Node Execution Count, and Debugged flag.

Execute Analytics SQL Query

The Execute Analytics SQL Query action allows users to directly execute custom SQL queries against their data with granular control and flexibility for advanced analysis.

Input Fields:

  1. SQL Query — Enter the SQL query. Prefix table names with ENTITY_ and column names with _pr_ (e.g., Select _pr_columnName from ENTITY_TableName)

  2. Select Group — Choose between Storage or Platform

  3. Define parameters — Declare the bind variables used in your query's WHERE condition: give each the name used in the query and the closest matching data type, then provide its value under Parameters. Use parameters instead of concatenating values into the SQL.

  4. Define Result Schema — Add fields manually, use a code snippet, or map schema from another step

Export Reports

The Export Reports action generates and exports customized reports with selected data projections, filters, sorting options, and time ranges in CSV, XLS, or XLSX formats.

Key input fields: File Name (prefix), Keep exact file name, Group, Base Report, Projections, Time Range, Filter, Search Object, Page (Offset and Limit), Sorts, File Format (CSV, XLS, or XLSX), Batch size.

Converts Filter to SQL Condition

This action transforms visual filter inputs into SQL-compatible condition strings for seamless integration of UI-based filter logic into backend SQL queries. Filters support Equals to, Start with, In, and other operators. The output is a SQL-compatible condition string in JSON format that can be appended directly to SQL queries.

Export SQL Query Result

Executes a custom SQL query and exports the result as a downloadable file in CSV, XLS, XLSX or TSV format. Input: File Name prefix, SQL Query, Select Group, Define parameters (bind variables for the query, as in Execute Analytics SQL Query), optional Result Schema, and File format. Output includes File Type, File Name, Source path, Source Type, a secure download Link, and ua:type (always "FILE").

Execute Analytics SQL Update Query

Modifies existing records in a dataset using SQL UPDATE statements. Input: SQL Query (a valid UPDATE statement) and Select Group. Output: count of records updated.

Create LogQL Query

Builds a LogQL query from structured parameters, for fetching node-level variables from automation execution logs. Input: Workflow Id, Execution Id, Root Execution Id, Node Ids (list of node IDs to filter) and Variable Types (list of variable types to filter). Output: the generated LogQL query string, which you can pass to Execute LogQL Query.

Execute LogQL Query

Runs a LogQL query against automation execution logs. Input: LogQL Query, Start Time and End Time (epoch milliseconds). Output: a list of workflow variables.

Fetch Node Executions from Execution Id

Fetches the node executions of an automation run. Input: Execution ID, Start Time and End Time (epoch milliseconds). Output: a list of node execution objects.

Fetch Routine Load Details

Fetches the routine load details for an analytics table. Input: Select Group (Storage or Platform) and Select Table. Output: a list of routine load jobs with their name, state, table, progress, statistics, error log URLs and timestamps.

Stream Load File Into Analytics Table

Bulk-loads a delimited file into an analytics table. Input:

  • Select Group and Select Table — the target table.

  • File — the delimited file to load.

  • Columns — table column names in the same order as the columns in the file.

  • Populate System Columns — derive id, timestamp, createdTime, modifiedTime, version and deleted on the server.

  • Column Separator, Quote Character, Escape Character and Header Rows To Skip — how the file is parsed.

  • Strict Mode and Max Filter Ratio — the fraction of rows allowed to fail before the load is rejected.

  • Timeout (seconds) — how long the load may run; non-positive values fall back to 900.

  • Load Label — optional; reuse the same label across retries to make them idempotent.

Output: success, label, status, message, and row counts (totalRows, loadedRows, filteredRows, unselectedRows), plus load time and an error URL when rows fail.

Notes

Keep the following in mind when using Analytics by UnifyApps:

  • Prefix table names with ENTITY_ and column names with _pr_ in all SQL queries; omitting these prefixes causes the query to fail.

  • Use Aggregate Metadata to discover available fields before writing analytics or SQL queries — it avoids trial-and-error when field names are unknown.

  • Set a narrow time range and a low Limit when testing queries for the first time; expand the scope only after confirming the query structure is correct.

  • For scheduled reporting, combine Export Reports with a Schedule trigger to generate files automatically at a set cadence.

  • Node Level Reporting exposes 35 execution-level metrics; filter by Status or Workflow Version to isolate data for a specific deployment.

FAQs

Can I join data across multiple tables? 

Yes, SQL queries can aggregate and join data across multiple sources or tables to generate comprehensive reports.

What export formats are supported?

Export Reports supports CSV, XLS and XLSX. Export SQL Query Result also supports TSV.

What is the Query field in Aggregate Metadata? 

It allows users to search for metadata using partial field names when exact names are unknown.