tmetric

n8n community node for TMetric time tracking: full coverage of TMetric REST API v3 and v2

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: n8n-nodes-tmetric

Documentation

n8n-nodes-tmetric

n8n community node for TMetric time tracking. It covers the whole TMetric REST API: every operation of API v3 (136) and API v2 (112), generated from the official OpenAPI specifications.

Installation · Credentials · Usage · Operations · Development · Compatibility

Installation

In n8n: Settings → Community nodes → Install, enter n8n-nodes-tmetric, accept the risk notice and install.

In queue mode, restart the instance after installing or updating the package, so that the workers load it too.

See the n8n community nodes documentation for other ways to install.

Credentials

Create a TMetric API credential:

  • API Token: in TMetric, open My Profile → Get new API token. A token is valid for one year; generating a new one invalidates the previous token.
  • Base URL: https://app.tmetric.com unless you use a different TMetric server.

The same credential is used for API v3 and v2. Test calls GET /api/v3/user.

Usage

  1. Choose the API Version. Use v3 by default; switch to v2 for operations that exist only there (see below).
  2. Choose the Resource and Operation.
  3. Workspace and User fields are dropdowns loaded from your account; you can also pass an ID with an expression.
  4. Optional API parameters are under Query Parameters.
  5. Operations with a request body have a Body (JSON) field. It starts empty; the hint under the field shows an example from the API specification. PUT replaces the whole object, so send every field you want to keep (get the object first, change it, send it back).

Behaviour worth knowing:

  • List responses are split into one item per element. Turn this off with Options → Split Into Items.
  • List parameters (project IDs, user IDs, statuses) are comma-separated, for example 123, 456. They are sent as repeated query parameters (ProjectList=123&ProjectList=456), as TMetric expects.
  • Dates: parameters that TMetric expects as YYYY-MM-DD are trimmed automatically, so a full date-time from an expression works.
  • Files: CSV, PDF and XLSX exports and attachment downloads are returned as binary data (field data by default). Uploads (invoice attachments, expense receipts) read the file from an input binary field.
  • No pagination: TMetric does not paginate. Time entries are limited by the date range you request; Get workspace tasks returns at most 500 tasks (HTTP 206), so filter it.
  • File size limit: uploads and downloads larger than 100 MB are rejected to protect worker memory.
  • Not exposed as an AI tool: the node cannot be attached to n8n AI Agents in 0.1.x. A later release may add this for read-only operations.

Operations

API v3 resources: Accounts (two-factor settings), Clients, Exchange Rates, Expenses, Integrations, Invoices, Members, Notifications, Projects, Reports (project summary, profitability), Schedule, Tasks, Teams, Time Balance, Time Entries (including starting and stopping the timer), Time Off (read), Timesheets, User.

API v2 resources: Account Members, Accounts, Activity, API Version, Clients, Demo Data, Integrations, Invoices, Projects, Recent Tasks, Reports (activity, apps usage, detailed, long timers, projects, tasks, team, with CSV/PDF export), Tags, Time Entries, Time Off Balances, Time Off Policies, Time Off Requests, Timeline, Timer, User Groups, User Profile.

Use v2 for these, which v3 does not offer:

Task v2 resource
Create, update, delete, approve or deny a time off request Time Off Requests
Time off policies and balances Time Off Policies, Time Off Balances
Create, update, delete tags and work types Tags
Create, update, delete teams User Groups
Detailed, task, team, activity and apps usage reports; CSV/PDF export Report: …
Timeline, screenshots and captured activity Timeline, Activity
Start a timer from an external issue Timer

Development

Requirements: Node.js 22+.

npm install
npm run generate   # regenerate operations from specs/*.json
npm run build
npm run lint
npm run check      # offline check of all operations against the specs
npm run dev        # n8n with the node loaded and hot reload

nodes/Tmetric/generated/* is produced by scripts/generate.mjs from specs/tmetric-v3.json and specs/tmetric-v2.json. When TMetric publishes a new specification, replace the file in specs/, run npm run generate, then npm run check. Fixes for gaps in the published specifications live in BODY_OVERRIDES in the generator.

Publish (lint, build and publish from your machine):

npm run publish:local

Compatibility

Built with @n8n/node-cli 0.55 and n8n-workflow 2.46. Requires n8n 1.x or 2.x with community nodes enabled.

Resources

License

MIT

Discussion