Webhooks

CURRENTLY IN TESTING PHASE (ETA: February 2020)

What are webhooks

Webhooks are automated messages when something happens in an app. They have a message (payload) and are sent to a unique URL.

Why would you use them?

Webhooks allow your apps to get a notification when something happens in Clockify so your app can take an appropriate action. For example, if a time entry is created in Clockify, webhook will let you know about it so you can send that time entry into your own system.

How are webhooks different from API?

When you need to listen for an event and trigger automation, webhooks are more useful. For example, lets say you want to be notifited when a new project is created in Clockify. By using API, you’d need to GET all projects every few hours and deduce what’s new. But with webhooks, you’d get the information the second a project is created, without needing to ask the system “hey, anything new?” every minute.

Clockify implementation

  • Each user can have up to 10 webhooks per user per workspace, and 100 per workspace in total
  • Only the user who created the webhook can see and modify it
  • Available webhooks: NEW_PROJECT, NEW_TASK, NEW_CLIENT, NEW_TIMER_STARTED, NEW_TIME_ENTRY, NEW_TAG

Will there be the possibility to be even notified for changing and deletion of time entries?

By the way it’s great Webhooks are actually implemented!

Not at first. v1 will have webhooks for all “create” events (new timer started, new entry created, new project/client/tag created, etc).

But we do plan to add webhooks for “update” events in the future (entry updated, entry deleted), so they can serve like an audit trail mechanism.

1 Like