npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@mikiguillamon/n8n-nodes-solidtime

v0.2.6

Published

n8n community node for Solidtime with guided operations, flexible API requests, and AI agent tool support.

Downloads

93

Readme

@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 Token
  • Chart
  • Client
  • Project
  • Project Member
  • Report
  • Public Report
  • Invitation
  • Member
  • Organization
  • Tag
  • Task
  • Time Entry
  • User
  • Currency
  • Importer
  • Import
  • Export
  • Custom API Request

Supported Operations

  • 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

Requirements

  • n8n with community nodes enabled
  • Node.js ^22.22.0 || >=24.0.0 for local development
  • A Solidtime API token
  • A Solidtime organization ID

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:

  • Base URL: https://app.solidtime.io for cloud, or your self-hosted base URL without /api
  • API Token
  • Organization ID
  • License Key

Authentication uses the Solidtime bearer token format:

Authorization: Bearer <api-token>

License Behavior

The node is already prepared for commercial licensing.

Current behavior:

  • Any license key with 10 or more characters is accepted
  • Validation is centralized and cached
  • The validation layer is ready to switch to a remote license server later

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:

  • users and memberships
  • API tokens
  • organizations
  • clients
  • members
  • projects and project members
  • reports and public reports
  • tags
  • tasks
  • time entries
  • charts
  • invitations
  • currencies
  • importers, imports, and exports

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:

  • HTTP method
  • Relative API path
  • Additional query parameters as key/value rows
  • Additional headers as key/value rows
  • JSON request body
  • Shared credentials and shared transport logic

Security rules applied by the node:

  • Absolute URLs are rejected
  • Path traversal like .. is rejected
  • The request is always anchored to the configured Solidtime base URL

Examples:

  • /v1/organizations/<organization-ID>/projects
  • /api/v1/organizations/<organization-ID>/time-entries

AI Tool Usage

The node is marked with usableAsTool.

AI-oriented behavior included:

  • Semantic resource and operation names
  • Guided fields for common actions
  • Safe defaults
  • Output mode with Simplified or Raw
  • Local Limit handling for list operations when needed

Known API Limits

  • Some export endpoints can return non-JSON payloads depending on the selected format
  • Import.data remains free-form because the official contract does not publish a fully structured payload schema for each importer type
  • Pagination behavior depends on the endpoint family: some use page, others use limit / offset

Examples

Create a project

  • Resource: Project
  • Operation: Create
  • Name: Website redesign
  • Color: #2563eb

Get time entries for a user

  • Resource: Time Entry
  • Operation: Get Many
  • User ID: <user-uuid>
  • After: 2026-05-01
  • Return All: false
  • Limit: 100

Call an unsupported endpoint

  • Resource: Custom API Request
  • HTTP Method: GET
  • Path: /v1/organizations/<organization-ID>/...

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.

Official References