Log in Sign up
First-party app
Clockodo

Clockodo

Track time with Clockodo: time entries, the running clock, customers, projects, services, users and absences.

stable ProductivityHuman Resources

About

Clockodo ships in the w6w first-party pack. It declares 29 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.clockodo
Version
0.1.0
Author
w6w
Licence
MIT
Categories
Productivity · Human Resources

Overview

Clockodo is a German time-tracking and time-reporting service. This app lists, reads, creates, edits and deletes time entries (as a time span, a lump sum or a lump-sum service), and starts, reads and stops the running clock.

It also manages the master data entries are booked against — customers, projects (with budgets, deadlines and completion) and services — reads users and the authenticated user, and records, approves and deletes absences such as holidays and sick days.

The health check tracks whether the Clockodo API is serving; Clockodo publishes no status page.

Build with Clockodo

Three routes to the same 29 actions. The Workflow tab is generated from Clockodo's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Complete Project

complete-project

Mark a project completed, or reopen it with `completed: false` (PUT /v4/projects/{id}/complete).

Create Absence

create-absence

Record an absence (POST /v4/absences). `dateSince` and `type` are required; `usersId` defaults to the authenticated user.

Create Customer

create-customer

Create a customer (POST /v3/customers). Only `name` is required.

Create Time Entry

create-entry

Create a time entry (POST /v2/entries) in one of three forms: a time span (`timeSince` + `timeUntil` + `servicesId`), a lump sum (`timeSince` + `servicesId` + `lumpsum`), or a lump-sum service (`timeSince` + `lumpsumServicesId` + `lumpsumServicesAmount`). `customersId` and `timeSince` are always required.

Create Project

create-project

Create a project under a customer (POST /v4/projects). `name` and `customersId` are required.

Create Service

create-service

Create a service, the kind of work an entry is booked against (POST /v4/services). Only `name` is required.

Delete Absence

delete-absence

Delete an absence by id (DELETE /v4/absences/{id}). Irreversible.

Delete Customer

delete-customer

Delete a customer (DELETE /v3/customers/{id}). Use `dryRun` to see whether it would be allowed, and `force` to also delete dependent time entries. Irreversible without `dryRun`.

Delete Time Entry

delete-entry

Delete a time entry by id (DELETE /v2/entries/{id}). Irreversible.

Get Absence

get-absence

Read one absence by id (GET /v4/absences/{id}).

Get Running Clock

get-clock

Read the running clock entry of a user (GET /v2/clock); `running` is null when nothing is running. Defaults to the authenticated user.

Get Current User

get-current-user

Read the user the credential belongs to (GET /v4/users/me): id, name, role, team and settings.

Get Customer

get-customer

Read one customer by id (GET /v3/customers/{id}).

Get Time Entry

get-entry

Read one time entry by id (GET /v2/entries/{id}).

Get Project

get-project

Read one project by id (GET /v4/projects/{id}).

Get Service

get-service

Read one service by id (GET /v4/services/{id}).

Get User

get-user

Read one user by id (GET /v3/users/{id}).

List Absences

list-absences

List absences (GET /v4/absences), filterable by user, year, type, status and team. The documented response is `{ data: [...] }` with no paging block.

List Customers

list-customers

List customers (GET /v3/customers), filterable by active state and a full-text search. Paged.

List Time Entries

list-entries

List time entries in a time window (GET /v2/entries). `timeSince` and `timeUntil` are required ISO 8601 UTC timestamps; optionally filter by user, customer, project, subproject, service or text, and set `enhancedList` to add names, text and revenue. Paged.

List Projects

list-projects

List projects (GET /v4/projects), filterable by active state and a full-text search. Paged.

List Services

list-services

List services (GET /v4/services), filterable by active state and a full-text search. Paged.

List Users

list-users

List users (GET /v3/users), filterable by active state and a full-text search. Paged.

Start Clock

start-clock

Start the clock for a customer and service (POST /v2/clock). A clock already running for the user is stopped and reported in `stopped`. `timeSince` backdates the start.

Stop Clock

stop-clock

Stop a running clock entry (DELETE /v2/clock/{id}); `id` is the running entry's id from Get Running Clock. Optionally set the end time, mark the user away, or start a new clock straight away.

Update Absence

update-absence

Edit an absence, for example approve or decline it with `status` (PUT /v4/absences/{id}). Only the fields you pass are sent; at least one is required.

Update Customer

update-customer

Edit a customer (PUT /v3/customers/{id}). Only the fields you pass are sent; at least one is required.

Update Time Entry

update-entry

Edit a time entry (PUT /v2/entries/{id}). Only the fields you pass are sent (an empty string is treated as not passed); at least one field is required.

Update Project

update-project

Edit a project (PUT /v4/projects/{id}). Only the fields you pass are sent; at least one is required.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying Clockodo's real ids. 

{
  "manifestVersion": "2",
  "name": "clockodo-example",
  "steps": [
    {
      "id": "complete-project",
      "uses": {
        "app": "io.w6w.clockodo",
        "action": "complete-project",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "id": "<id>"
      }
    }
  ]
}

Here are some of the things you can do

  • Complete Project

    perform
    complete-project

  • Create Absence

    perform
    create-absence

  • Create Customer

    perform
    create-customer

  • Create Time Entry

    perform
    create-entry

  • Create Project

    perform
    create-project

+24 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for Clockodo, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to Clockodo. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "complete-project",
  payload: {
    id: "<value>",
    // completed: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action complete-project --payload '{"id":"<value>"}'

Give an AI agent Clockodo — without giving it Clockodo's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call 
{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.clockodo#complete-project",
    "input": {
      "id": "<id>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's Clockodo connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

Clockodo's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. Clockodo itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

Clockodo declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

Clockodo platform status

service

Clockodo API reachability

An unauthenticated GET /v4/users/me. The documented `Authentication failed` error envelope proves the Clockodo API is serving; it says nothing about any credential.

quota

API rate-limit headroom