Clockify Enhanced Trigger
AI-generatedOverview
The Clockify Enhanced Trigger node listens for specific events occurring within a Clockify workspace and triggers workflows in response. It is designed to integrate Clockify's webhook system with n8n, enabling automation based on real-time updates such as new time entries, invoice creation, user changes, and more.
Common scenarios where this node is beneficial include:
- Automatically processing or notifying teams when a new invoice is created.
- Tracking time entry updates to synchronize with other project management tools.
- Responding to user status changes within a workspace for access control or notifications.
- Monitoring approval request statuses to trigger follow-up actions.
For example, you could use this node to start a workflow that sends an email notification whenever a new task is created or to update a CRM system when a client is added.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select the Clockify workspace by name or specify its ID. This determines the scope of events the webhook will listen to. |
| Webhook Name | A custom name for the webhook being created. Helps identify the webhook within Clockify. |
| Webhook Event | The specific Clockify event to listen for. Options include: Approval Request Status Updated, Balance Updated, Client Created, Invoice Created, Invoice Updated, New Approval Request, Project Created, Tag Created, Task Created, Time Entry Created/Deleted/Updated, Time Off Request Approved/Rejected/Withdrawn/Requested, Timer Started/Stopped, User Activated/Deactivated/Deleted/Email Changed/Joined/Updated. |
Output
The node outputs JSON data representing the payload received from the Clockify webhook event. This JSON contains detailed information about the event, such as the entity affected (e.g., a new invoice or updated time entry) and relevant metadata.
If the webhook event does not match the configured event type or the signature verification fails, the node outputs an empty object.
This node does not output binary data.
Dependencies
- Requires a valid API authentication token credential for Clockify to create, verify, and delete webhooks.
- Needs network accessibility for receiving incoming HTTP POST requests at the webhook URL configured in n8n.
- Uses Clockify's REST API endpoints to manage webhooks and fetch workspace information.
Troubleshooting
- Webhook Not Triggering: Ensure the workspace ID and webhook event are correctly set. Verify that the webhook URL registered in Clockify matches the one provided by n8n.
- Signature Verification Failed: The node verifies incoming webhook requests using a secret token. If the "clockify-signature" header does not match the stored token, the event is ignored. Check that the webhook was created successfully and the token is stored properly.
- Event Mismatch: If the incoming event type differs from the selected webhook event, the node will not emit data. Confirm the correct event type is selected.
- API Request Failures: Errors during webhook creation or deletion may occur due to invalid credentials or insufficient permissions. Verify the API key and workspace access rights.
- Missing Workspace Options: If the workspace list does not load, check the API credentials and network connectivity.