Clockify Automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/clockify-automation --openclawClockify Automation
Automate your Clockify time tracking operations directly from Claude Code. Log time entries, query historical data, manage workspaces, and audit team activity -- all without leaving your terminal.
Toolkit docs: composio.dev/toolkits/clockify
Setup
- Add the Rube MCP server to your Claude Code config with URL:
https://rube.app/mcp - When prompted, authenticate your Clockify account through the connection link provided
- Start automating your time tracking workflows with natural language
Core Workflows
1. Create Time Entries
Log time with project, task, and tag associations, plus billable status.
Tool: CLOCKIFY_CREATE_TIME_ENTRY
Log 2 hours of work on project 64a687e2 in workspace 64a687e3 starting at 9am UTC today with description "API development"
Key parameters:
workspaceId(required) -- workspace where the entry is createdstart(required) -- ISO 8601 start time (e.g.,2026-02-11T09:00:00Z)end-- ISO 8601 end time; omit to create a running timerprojectId-- associate with a projecttaskId-- associate with a taskdescription-- work description (0-3000 chars)tagIds-- array of tag IDsbillable-- whether the entry is billablecustomFieldValues-- array of custom field entries withcustomFieldIdandvalue
2. Query Time Entries
Retrieve historical time entries for reporting, auditing, and invoicing.
Tool: CLOCKIFY_GET_TIME_ENTRIES
Get all time entries for user abc123 in workspace xyz789 from January 2026
Key parameters:
workspaceId(required) -- workspace to queryuserId(required) -- user whose entries to retrievestart/end-- ISO 8601 date range filtersproject-- filter by project IDtask-- filter by task IDtags-- comma-separated tag IDsdescription-- text filter (partial match)hydrated-- settrueto get full project/task/tag objects instead of just IDsin-progress-- settrueto return only the running timerpage/page-size-- pagination (default 50 per page)
3. Delete Time Entries
Remove erroneous, duplicate, or cancelled time entries.
Tool: CLOCKIFY_DELETE_TIME_ENTRY
Delete time entry 5b715448 from workspace 64a687e3
- Requires
workspaceIdandid(the time entry ID) - Use for cleanup of bad imports or duplicates
4. Manage Workspaces
List all workspaces the authenticated user belongs to.
Tool: CLOCKIFY_GET_ALL_MY_WORKSPACES
Show me all my Clockify workspaces
- Optional
rolesfilter -- array of roles like["WORKSPACE_ADMIN", "OWNER"] - Use this to discover workspace IDs before creating or querying entries
5. User Information
Retrieve current user details and list workspace members.
Tools: CLOCKIFY_GET_CURRENTLY_LOGGED_IN_USER_INFO, CLOCKIFY_FIND_ALL_USERS_ON_WORKSPACE
Who am I logged in as? Then list all users in workspace 64a687e3
CLOCKIFY_GET_CURRENTLY_LOGGED_IN_USER_INFOreturns the authenticated user's profile (no parameters needed)CLOCKIFY_FIND_ALL_USERS_ON_WORKSPACErequiresworkspaceId; supportsname,emailfilters and pagination (page,page-sizemax 100)
6. Running Timer Management
Start a timer by omitting end in create, or check for running entries.
Tools: CLOCKIFY_CREATE_TIME_ENTRY, CLOCKIFY_GET_TIME_ENTRIES
Start a timer on project abc in workspace xyz with description "Working on bug fix"
- Create without
endto start a running timer - Use
CLOCKIFY_GET_TIME_ENTRIESwithin-progress: trueto check if a timer is running
Known Pitfalls
- Workspace and user IDs are required: Most Clockify tools require both
workspaceIdanduserId. Always callCLOCKIFY_GET_ALL_MY_WORKSPACESandCLOCKIFY_GET_CURRENTLY_LOGGED_IN_USER_INFOfirst to resolve these IDs. - ISO 8601 timestamps: All time parameters must be in ISO 8601 format with timezone (e.g.,
2026-02-11T09:00:00Z). Omitting the timezone causes unpredictable behavior. - Running timers: Only one timer can run at a time. Creating a new entry without
endwill fail if another timer is already active. Stop the existing timer first. - Pagination defaults:
CLOCKIFY_GET_TIME_ENTRIESdefaults to 50 entries per page. For full exports, loop through pages until no more results are returned. - Tag IDs are workspace-scoped: Tag IDs from one workspace cannot be used in another. Always resolve tags within the target workspace context.
Quick Reference
| Tool Slug | Description |
|---|---|
CLOCKIFY_CREATE_TIME_ENTRY | Create a time entry or start a timer (requires workspaceId, start) |
CLOCKIFY_GET_TIME_ENTRIES | List time entries with filters (requires workspaceId, userId) |
CLOCKIFY_DELETE_TIME_ENTRY | Delete a time entry (requires workspaceId, id) |
CLOCKIFY_GET_ALL_MY_WORKSPACES | List all workspaces for the authenticated user |
CLOCKIFY_GET_CURRENTLY_LOGGED_IN_USER_INFO | Get current user profile info |
CLOCKIFY_FIND_ALL_USERS_ON_WORKSPACE | List all users in a workspace (requires workspaceId) |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/clockify-automation/SKILL.mdView on GitHub Overview
Clockify Automation lets you log time entries, manage workspaces, and audit team activity from Claude Code using natural language. It supports creating entries, querying history, deleting entries, and listing workspaces, all via straightforward commands.
How This Skill Works
After configuring the Rube MCP endpoint and authenticating Clockify, Claude commands map to tools like CLOCKIFY_CREATE_TIME_ENTRY, CLOCKIFY_GET_TIME_ENTRIES, and CLOCKIFY_DELETE_TIME_ENTRY. Provide required fields such as workspaceId and start; include end to close an entry or omit it to start a running timer. Use hydrated=true to fetch full project/task/tag objects when needed.
When to Use It
- Log a new time entry for a specific workspace and project with a start time and description.
- Retrieve historical time entries for reporting or invoicing within a date range.
- Check if a timer is currently running on a workspace.
- List all workspaces the authenticated user belongs to, with optional role filtering.
- Audit team activity by retrieving current user info and listing workspace members.
Quick Start
- Step 1: Add the Rube MCP server to your Claude Code config with URL https://rube.app/mcp
- Step 2: Authenticate your Clockify account through the connection link provided
- Step 3: Start issuing natural language commands like 'Log 2 hours...' or 'Show me all my Clockify workspaces'
Best Practices
- Always include workspaceId when creating or querying time entries.
- Use ISO 8601 start times; omit end to start a running timer.
- Keep descriptions under 3000 characters and pass tagIds as an array of IDs.
- Set hydrated: true when you need full project/task/tag details instead of IDs.
- Paginate large results with page and page-size (default 50 per page).
Example Use Cases
- Log 2 hours of work on project 64a687e2 in workspace 64a687e3 starting at 2026-02-11T09:00:00Z with description "API development"
- Get all time entries for user abc123 in workspace xyz789 from January 2026
- Delete time entry 5b715448 from workspace 64a687e3
- Show me all my Clockify workspaces
- Who am I logged in as? Then list all users in workspace 64a687e3