MCP
A2APrerequisites
Before continuing, you should have already completed the following for this connector:Configure the Connector
Connector Profile
Link an Account
Link Account
How Clockify webhooks are set up
Clockify webhooks are provisioned automatically when you connect your account — there is nothing to configure in Clockify and no URL to paste. StackOne registers one Clockify webhook per event you enable, pointing at StackOne’s receiver.
- No callback URL to copy, and no verification step to complete.
- Webhooks are created on the account’s default workspace.
- Only the events you enable in StackOne are registered in Clockify and delivered.
Before you connect
Make sure the API key you connect with can access the resources you want events for, and that your plan allows enough webhooks.
- Use an API key belonging to a workspace member with access to the relevant resources; some events (for example project or user changes) require workspace admin rights.
- Clockify limits webhooks per workspace by plan — the Free plan allows up to 3. Enable only the events you need so provisioning stays within your plan’s limit.
Available webhook events
The following Clockify events can be enabled. Only events selected in StackOne are registered in Clockify and delivered — Clockify will not send events you have not subscribed to.
Client events
Events on clients.
- New Client (
NEW_CLIENT) — Fired when a client is created - Client Updated (
CLIENT_UPDATED) — Fired when a client is updated - Client Deleted (
CLIENT_DELETED) — Fired when a client is deleted
Project events
Events on projects.
- New Project (
NEW_PROJECT) — Fired when a project is created - Project Updated (
PROJECT_UPDATED) — Fired when a project is updated - Project Deleted (
PROJECT_DELETED) — Fired when a project is deleted
Task events
Events on tasks within projects.
- New Task (
NEW_TASK) — Fired when a task is created on a project - Task Updated (
TASK_UPDATED) — Fired when a task is updated - Task Deleted (
TASK_DELETED) — Fired when a task is deleted
Tag events
Events on tags.
- New Tag (
NEW_TAG) — Fired when a tag is created - Tag Updated (
TAG_UPDATED) — Fired when a tag is updated - Tag Deleted (
TAG_DELETED) — Fired when a tag is deleted
Time entry events
Events on time entries.
- New Time Entry (
NEW_TIME_ENTRY) — Fired when a time entry is created - Time Entry Updated (
TIME_ENTRY_UPDATED) — Fired when a time entry is updated - Time Entry Deleted (
TIME_ENTRY_DELETED) — Fired when a time entry is deleted - Time Entry Split (
TIME_ENTRY_SPLIT) — Fired when a time entry is split into multiple entries - Time Entry Restored (
TIME_ENTRY_RESTORED) — Fired when a deleted time entry is restored
Timer events
Events on the running timer.
- Timer Started (
NEW_TIMER_STARTED) — Fired when a running timer is started - Timer Stopped (
TIMER_STOPPED) — Fired when a running timer is stopped
Time off and balance events
Events on time off requests and balances (requires the Time Off paid feature).
- Time Off Requested (
TIME_OFF_REQUESTED) — Fired when a time off request is submitted - Time Off Request Approved (
TIME_OFF_REQUEST_APPROVED) — Fired when a time off request is approved - Time Off Request Rejected (
TIME_OFF_REQUEST_REJECTED) — Fired when a time off request is rejected - Time Off Request Updated (
TIME_OFF_REQUEST_UPDATED) — Fired when a time off request is updated - Time Off Request Withdrawn (
TIME_OFF_REQUEST_WITHDRAWN) — Fired when a time off request is withdrawn - Balance Updated (
BALANCE_UPDATED) — Fired when a time off balance changes
Approval events
Events on timesheet approval requests (requires the Approvals paid feature).
- New Approval Request (
NEW_APPROVAL_REQUEST) — Fired when an approval request is submitted - Approval Request Status Updated (
APPROVAL_REQUEST_STATUS_UPDATED) — Fired when an approval request is approved, rejected, or withdrawn
Expense events
Events on expenses (requires the Expenses paid feature).
- Expense Created (
EXPENSE_CREATED) — Fired when an expense is created - Expense Updated (
EXPENSE_UPDATED) — Fired when an expense is updated - Expense Deleted (
EXPENSE_DELETED) — Fired when an expense is deleted - Expense Restored (
EXPENSE_RESTORED) — Fired when a deleted expense is restored
Invoice events
Events on invoices (requires the Invoicing paid feature).
- New Invoice (
NEW_INVOICE) — Fired when an invoice is created - Invoice Updated (
INVOICE_UPDATED) — Fired when an invoice is updated
Scheduling events
Events on scheduled assignments (requires the Scheduling paid feature).
- Assignment Created (
ASSIGNMENT_CREATED) — Fired when a scheduled assignment is created - Assignment Updated (
ASSIGNMENT_UPDATED) — Fired when a scheduled assignment is updated - Assignment Deleted (
ASSIGNMENT_DELETED) — Fired when a scheduled assignment is deleted - Assignment Published (
ASSIGNMENT_PUBLISHED) — Fired when scheduled assignments are published
Rate events
Events on billable and cost rates.
- Billable Rate Updated (
BILLABLE_RATE_UPDATED) — Fired when a billable rate is changed - Cost Rate Updated (
COST_RATE_UPDATED) — Fired when a cost rate is changed
Workspace user events
Events on workspace membership and user profiles.
- Users Invited to Workspace (
USERS_INVITED_TO_WORKSPACE) — Fired when users are invited to the workspace - Limited Users Added to Workspace (
LIMITED_USERS_ADDED_TO_WORKSPACE) — Fired when limited users are added to the workspace - User Joined Workspace (
USER_JOINED_WORKSPACE) — Fired when a user accepts an invite and joins the workspace - User Activated (
USER_ACTIVATED_ON_WORKSPACE) — Fired when a user is activated on the workspace - User Deactivated (
USER_DEACTIVATED_ON_WORKSPACE) — Fired when a user is deactivated on the workspace - User Removed (
USER_DELETED_FROM_WORKSPACE) — Fired when a user is removed from the workspace - User Email Changed (
USER_EMAIL_CHANGED) — Fired when a user’s email address changes - User Updated (
USER_UPDATED) — Fired when a user’s profile is updated
Delivery format
Details of how Clockify delivers events to StackOne.
JSON payloads
Clockify delivers each event as its own HTTP POST with a JSON body containing the affected entity (its id is used as the event ID). Clockify sends one event per request; deliveries are not batched.