Analytics & BI nodes connect n8n with services that collect, organize, or report metrics. Depending on the integration, those metrics may describe product usage, website activity, revenue, customer behavior, or wider business performance. This category helps n8n users find community nodes that bring data from analytics and business-intelligence tools into workflows.
Once metrics are available in n8n, you can route them into a report, compare them with a threshold, combine them with other workflow data, or send a follow-up to the person who needs to review them. Each node exposes its own actions and fields, so check the listing to see exactly which service data it can retrieve and how it returns that data.
What Analytics & BI nodes can help you work with
Product analytics
Product analytics can show how people use an application: which events they trigger, where they move through a funnel, which features they return to, and where they stop. When a connected service exposes these events or reports through its API, an n8n node can bring selected results into a workflow for a scheduled digest, an internal alert, or a review queue.
The event names and definitions come from the product and its tracking setup. Before using a metric, confirm what it counts, which users or sessions it includes, and what date range the result covers. An event total without that context can be easy to misread.
Web analytics
Web analytics data can include visitors, sessions, traffic sources, landing pages, and conversion events. A workflow can gather a chosen set of metrics on a schedule and pass them into a report or another system. You can also use a workflow to flag a value that needs attention, provided the source node returns the fields and time ranges needed for that check.
Web analytics definitions vary. For example, a visitor count and a session count describe different things, and attribution can depend on the connected service's reporting rules. Check those definitions before comparing results across sources.
Reporting and business intelligence
Reporting and BI integrations can expose saved reports, datasets, query results, or business measures. In n8n, those results can become part of a larger process: distribute a weekly summary, route an unusual result for review, or pass selected figures to a planning workflow.
Some nodes only read data; others may support additional actions. Do not assume a node can create or edit dashboards just because it belongs to an analytics category. Review its listed operations and the permissions its credentials require.
Revenue and business metrics
Some analytics-related services expose revenue, growth, customer, or marketplace data rather than website or in-product events. The current Analytics & BI listing includes operations for browsing structured records with revenue and growth fields, applying filters, and retrieving a detailed profile. This can help workflows use business metrics as inputs alongside other information.
Examples of analytics workflows in n8n
A category node can retrieve the data while other n8n steps schedule the run, transform results, and deliver the next action. Common patterns include:
- Send a metrics digest: retrieve selected product or web metrics on a schedule, format the relevant fields, and send a concise report to the people who use it.
- Flag a change for review: check a returned value against a threshold and route the result for follow-up. For a week-over-week or month-over-month comparison, the workflow needs a date-range option from the source or a saved earlier snapshot.
- Bring several measures together: retrieve fields from more than one source, align them by date, product, or another shared key, then send the combined result to a reporting step.
- Enrich a business record: retrieve a metric-rich profile or record, then add selected fields to a downstream process when the node supports the required filters and lookup.
These patterns depend on the operations available in each listing. A node that returns current totals may not provide historical data, and a workflow cannot calculate a trend unless it receives comparable time periods or stores earlier results.
Choose a node by the metric you need
Start with the question you want the workflow to answer. Then check whether a node can retrieve the relevant metric, report, or record. Compare the returned fields with the next step in your workflow so you know whether the data can be grouped or compared in the way you need.
Before installing, review:
- Metric definitions: What does each number count, and which events, users, or records are included?
- Time period: Can you choose a date range or reporting interval? Does the response include a timestamp or timezone?
- Filters and pagination: Can you narrow a report to the relevant product, segment, page, or record? Does the node return one page or multiple pages of results?
- Output fields: Are currency, units, dimensions, and identifiers clear enough for later workflow steps?
- Credentials and access: Which API key or account permissions are required, and what data can that connection read?
- Available actions: Does the node retrieve data only, or can it also create or update reports or records?
- n8n compatibility: Check the listing for current verification and installation requirements. Community node support varies.
For comparisons, use the same metric definition and date boundaries on each side. If one source reports calendar months and another returns rolling 30-day totals, keep that difference visible in the report instead of treating the numbers as directly equivalent.
Provenance and verification
The current Analytics & BI listing is published with npm provenance. Provenance links a package release to its source and build, which helps you inspect how that release was produced. It is separate from n8n verification: provenance does not mean n8n has verified the node. Check the listing for its current verification and installation status. The current listing is marked for self-hosted n8n.
Build an n8n node for your analytics product
If you build a product analytics, web analytics, reporting, or BI service, NativeShip can help you create and publish an n8n community node so users can bring your data into their workflows. Try NativeShip.
