OpenRuna
Sign in
← Workflows

Umami analytics template

17 nodes · manual, schedule, httpRequest, baserow

Engine
n8n
Nodes
17
Trigger
scheduled/triggered
Source file
1850_Code_Schedule_Automation_Webhook.json

Workflow flow

IntegrationsManualScheduleHTTPBaserowCode
100%
TRIGGER

When clicking ‘Test workflow’

Manual

TRIGGER

Schedule Trigger

Schedule

Get view stats from Umami

HTTP

Parse Umami data

Code

Send data to A.I.

HTTP

Get page data from Umami

HTTP

Parse Umami data1

Code

Get page view data from Umami

HTTP

Parse Umami

Code

Send data to A.I.1

HTTP

Save data to Baserow

Baserow

11 steps · flows top to bottom, branches left to right

Browse by integration

manualschedulehttpRequestbaserow
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Umami analytics template. 17 nodes across manual, schedule, httpRequest, baserow, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Umami analytics template" chains 17 nodes to move data between manual, schedule, httpRequest, baserow. 17 nodes · manual, schedule, httpRequest, baserow It starts from a scheduled/triggered trigger and routes data through every node in order. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 17-node flow from scratch.
  • Benchmark it against your current manual integration to spot missing steps or redundant nodes.
  • Study how data moves from manual to schedule before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the manual stack.

Example output

Imported into n8n, "Umami analytics template" exposes 17 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, schedule, httpRequest, baserow. Set your credentials on the manual node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Umami analytics template" JSON into a plain-English runbook, node by node. It can flag where manual rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for manual, schedule, httpRequest, baserow. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Umami analytics template" — extract manual IDs and secrets into environment variables without changing the 17-node structure.

Frequently asked questions

How do I import "Umami analytics template" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Umami analytics template" use?
It uses: manual, schedule, httpRequest, baserow. The flow diagram above shows how each service connects across the 17 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own manual and schedule credentials in n8n after import.
What trigger type does "Umami analytics template" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Umami analytics template" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for manual, schedule, httpRequest, baserow.

Related resources