Zapier connects ClockMe to 6,000+ apps via HTTP webhooks and the ClockMe REST API today. Automatically log time when a Jira issue is resolved, start a timer from a Slack command, or create a ClockMe entry when a Toggl export runs. A native Zapier app with official triggers (Timer started, Entry created) and actions (Start timer, Stop timer, Log time) is on the ClockMe roadmap — but the REST API gives you the same power today.
Want your key pre-filled?
Sign in to ClockMe and use the setup wizard — it generates the exact config with your real API key and project ID already embedded.
A native Zapier app with official triggers and actions is on the ClockMe roadmap. It will make setup much easier than the current webhook approach. In the meantime, 'Webhooks by Zapier' plus the ClockMe REST API gives you the same capabilities.
Any Zapier trigger can start a timer: Google Calendar event start, Jira issue assigned, Linear task moved to In Progress, Slack command, Notion database update — anything Zapier can listen to can trigger a POST to /api/timer/start.
Yes. POST to https://clockme.co/api/timer/stop with your Authorization header. No body required — it stops the currently running timer for the API key owner.
Required: projectId. Optional: startTime (ISO 8601), endTime (ISO 8601), description (string), taskId (if logging to a specific task). If you omit endTime, the entry is logged as a running timer.