Description
@mikiguillamon/n8n-nodes-solidtime
Professional n8n community node for Solidtime Cloud and self-hosted Solidtime instances.
It implements the official Solidtime API contract exposed by the exported api-1.json and api-1.yaml specifications, with guided UI for the public resources, filters, enums, and payloads, plus a safe Custom API Request escape hatch for anything outside the modeled surface.
Supported Resources
API TokenChartClientProjectProject MemberReportPublic ReportInvitationMemberOrganizationTagTaskTime EntryUserCurrencyImporterImportExportCustom API Request- CRUD where the official API exposes CRUD
- user profile and memberships
- API token management
- organization settings
- members, projects, project members, clients, tags, tasks, reports, invitations
- time entry listing, create/update/delete, bulk update, bulk delete, aggregate, export, aggregate export
- chart endpoints
- importer discovery and import launch
- organization export launch
Custom API Request- n8n with community nodes enabled
- Node.js
^22.22.0 || >=24.0.0for local development - A Solidtime API token
- A Solidtime organization ID
Base URL:https://app.solidtime.iofor cloud, or your self-hosted base URL without/apiAPI TokenOrganization IDLicense Key
Supported Operations
Requirements
Installation
On a self-hosted n8n instance:
1. Go to Settings > Community Nodes
2. Select Install
3. Enter @mikiguillamon/n8n-nodes-solidtime
4. Confirm the installation prompt
5. Restart n8n if your deployment requires it
Credentials
Create Solidtime API credentials with:
Authentication uses the Solidtime bearer token format:
Authorization: Bearer
License Behavior
The node is already prepared for commercial licensing.
Current behavior:
How the Node Covers the API
As of May 15, 2026, this package is aligned to the exported official API specs that include 46 public paths across:
The node models those resources with guided operations and leaves Custom API Request as a fallback for future or private endpoints.
Custom API Request
Custom API Request supports:
Security rules applied by the node:
.. is rejectedExamples:
/v1/organizations//projects /api/v1/organizations//time-entries AI Tool Usage
The node is marked with usableAsTool.
AI-oriented behavior included:
Output mode with Simplified or RawLimit handling for list operations when neededKnown API Limits
Import.data remains free-form because the official contract does not publish a fully structured payload schema for each importer typepage, others use limit / offsetExamples
Create a project
ProjectCreateWebsite redesign#2563ebGet time entries for a user
Time EntryGet Many2026-05-01false100Call an unsupported endpoint
Custom API RequestGET/v1/organizations//... Development
npm install
npm run lint
npm run build
npm pack --dry-run
npm run dev
Validation
The package should pass:
npm run lint
npm run build
npm pack --dry-run
Release
The release workflow is documented in RELEASE.md.
Public publishing is configured through GitHub Actions with npm provenance.