Guide telemetry event registration, emission, and validation across the n8n codebase.
npx skills add https://github.com/n8n-io/n8n --skill n8n-telemetry
Please help me install this Agent Skill. Skill: n8n:telemetry Source: https://github.com/n8n-io/n8n/tree/main/.agents/skills/telemetry Command: npx skills add https://github.com/n8n-io/n8n --skill n8n-telemetry
Developers adding or modifying telemetry events in n8n risk breaking downstream analytics by renaming events, duplicating names, or changing property types. This Skill enforces a centralized registry with strict naming, typing, and migration rules so product analytics remain consistent across frontend and backend.
@n8n/telemetry catalog to find existing events, their meanings, and property schemas before adding new ones.track() calls correctly in frontend (useTelemetry) and backend (Telemetry.track or RelayEventMap) using shared registry entries.Use the n8n telemetry skill to register a new product event called "User pinned node data" under the WORKFLOW domain with a typed zod schema.
High-intent search queries and answers about installing and using this skill.
Check the catalog with `pnpm --filter @n8n/telemetry catalog`, pick a domain by the event's subject, write a zod-typed entry in `packages/@n8n/telemetry/src/events/`, then emit it via `useTelemetry().track` on the frontend or `Telemetry.track` on the backend using the registry entry.
The registry in `packages/@n8n/telemetry` defines one entry per event with its emitted name, description, and zod property schema. Entries are composed into `TELEMETRY_EVENT.<DOMAIN>.<EVENT>` and passed to `track()` for compile-time checks and runtime validation.
No. Renaming an emitted event orphans the BigQuery table that materializes from it. Treat renames as delete-plus-create, never reuse names, and coordinate removals with the data team before deleting the registry entry.
Yes. Backend events can be emitted either through a `RelayEventMap` handler in `packages/cli/src/events/relays/telemetry.event-relay.ts` or a direct `Telemetry.track(...)` call, both referencing the same registry entry.
Typecheck fails when properties are typo'd, missing, or wrongly typed against the registry entry's zod schema. Use the registry entry itself rather than a string literal so TypeScript catches mismatches at compile time.
Events not yet migrated to the registry do not appear in the catalog. For these, search `track()` call sites directly in `packages/frontend/editor-ui/src/app/plugins/telemetry/index.ts` and `packages/cli/src/telemetry/index.ts`.
spencerpaulyRecommend existing skills for tasks already covered by the skill list.
geezerrrrCreate, update, and retrieve Notion pages, databases, and blocks via the Notion API.
OliverOuyangAnalyze skill execution telemetry to identify bottlenecks and generate prioritized optimization plans.
FrekiManagarmIntegrate PostHog analytics into JavaScript web apps with event capture.