n8n-nodes-privatus-analytics

n8n community nodes for Privatus Analytics, the cookieless web analytics service. They use only the public Privatus Analytics API and its signed webhooks, have no runtime dependencies, and never send your data anywhere except to https://privatusanalytics.com.

• Privatus Analytics node: read stats, manage goals, chart notes, campaigns, uptime checks, alerts, status pages, exports, members, site audits, experiments and testimonials (16 resources, 51 operations).
• Privatus Analytics Trigger node: start a workflow on any of 25 events, such as an alert firing, an uptime check going down, a new testimonial or a finished export. Every delivery is verified with its signature.

n8n is a workflow automation platform. See the community nodes installation guide for how to install a package.

Installation

1. In n8n, open Settings, then Community Nodes.
2. Choose Install, enter n8n-nodes-privatus-analytics and confirm.

On n8n Cloud the nodes appear in the nodes panel once the package is verified. On a self-hosted n8n you can also run npm install n8n-nodes-privatus-analytics in ~/.n8n/nodes.

Credentials

You need an API token of the Privatus Analytics workspace you want to use.

1. In Privatus Analytics, open Workspace settings, then API tokens, and create a token. It starts with pat_.
2. For every operation and the trigger to work, keep all permissions, choose Every site you can access and set the expiry to never. The trigger adds a webhook, which needs the workspace settings permission and every site.
3. In n8n, create a Privatus Analytics API credential and paste the token. n8n tests it with GET /workspaces.json.

A token belongs to exactly one workspace, so there is no workspace to choose. To use two workspaces, create two credentials.

Privatus Analytics node

How it behaves:

• Dropdowns (sites, alert rules, uptime checks, experiments, testimonials, status pages, requests, segments, forms, tags and collections) are filled from your workspace. Every one also accepts an ID or an expression, for example ={{ $json.site_id }}.
• Return All and Limit on every list. Return All reads every page (100 rows each).
• Stats operations take a period (last 7 days, month to date, custom and more), filters as a JSON list like [["country","is","US"],["page","starts_with","/blog"]], and a saved segment. Get Top Values and Get Time Series return one item for each row or point.
• Dates can be picked or given as text. Day fields are sent as YYYY-MM-DD and the month of a campaign cost as YYYY-MM.
• Errors show the message of the API, with the field details of a validation error. A 402 says that a higher plan is needed.
• Continue on Fail is supported, and the node can be used as a tool by an AI agent.
• Custom API Call sends a GET, POST, PATCH or PUT to any path of the API with the credential of the node. Only a path on privatusanalytics.com is accepted, so the token cannot be sent anywhere else.

Nothing in this package deletes data. Deleting sites, testimonials, goals and the like is left to the Privatus Analytics app.

Example: weekly traffic report

1. Schedule Trigger, every Monday at 8:00.
2. Privatus Analytics, resource Stats, operation Get Overview, your site, period Last 7 Days, Additional Fields, Compare With, Previous Period.
3. Slack or Send Email, with {{ $json.metrics.visitors }} and {{ $json.change.visitors }} in the message.

Example: thank a happy customer

1. Privatus Analytics Trigger, event New Testimonial, filter Minimum Rating 5 Stars.
2. Privatus Analytics, resource Testimonial, operation Approve, with the site from {{ $json.site_id }} and the testimonial from {{ $json.testimonial.id }}.
3. Send Email to say thank you.

Privatus Analytics Trigger node

Choose one or more events. When the workflow is activated the node creates one webhook in your workspace (POST /workspaces/{id}/webhooks.json) and keeps its signing secret. When the workflow is deactivated the webhook is deleted. Using the test button works the same way.

Events: Alert Resolved, Alert Triggered, Analytics Import Completed, Analytics Import Failed, Experiment Ended, Export Ready, Goal Alert Triggered, New Member, New Reviews Found by Sync, New Site, New Testimonial, Site Audit Completed, Site Deleted, Testimonial Approved, Testimonial Deleted, Testimonial Form Submitted, Testimonial Import Finished, Testimonial Moved to Trash, Testimonial Rejected, Testimonial Request Finished, Testimonial Request Sent, Testimonial Restored, Uptime Check Down, Uptime Check Recovered and Usage Threshold Reached.

Filters (all optional): Site, Alert Rule, Form, Request and Minimum Rating. A filter applies to the events that carry that field, and the other events pass. A delivery that does not match is acknowledged and starts nothing.

Security. Every delivery carries a Privatus-Signature: t=<unix time>,v1=<hex> header, where v1 is the HMAC-SHA256 of <t>.<raw body> keyed with the signing secret. The node answers 401 and starts nothing when the signature is missing, wrong, or more than five minutes old. n8n must give the node the raw request body for this check, which it does for JSON deliveries.

Output. One item for each delivery: the data of the event plus id (the delivery ID), event, occurred_at and workspace_id. An id inside the data moves to record_id, or export_id for Export Ready. The payloads are documented at privatusanalytics.com/docs/api/webhooks.

Development

npm install
npm run lint        # n8n-node lint (the n8n community nodes rules)
npm test            # builds, then runs the unit tests with node --test
npm run dev         # n8n with the nodes loaded, using n8n-node dev
npm run sync-spec   # refresh nodes/shared/spec.json from https://privatusanalytics.com/openapi.json

nodes/shared/spec.json is the part of the OpenAPI document that the nodes use. Labels, descriptions, choices and types of the fields come from it, and nodes/shared/request.ts builds every request from it (path parameters, lists as status[]=a&status[]=b, filters as JSON, typed bodies). Run npm run sync-spec after an API change.

Releasing: set the version in package.json and CHANGELOG.md, commit, and push a tag that matches it. The Publish workflow tests, builds and publishes to npm with provenance.

License

MIT