Keep your time tracking clean without extra work. This setup listens for ticket updates from your system and flips a Clockify project to active or archived based on the ticket status. It is great for support teams that track time by ticket and want tidy reports.

A webhook receives a POST with ticket fields like number, customer name, and status. An IF check looks at the status. If the status is not Resolved, the flow finds the matching Clockify project by a name pattern built from the ticket data and sets archived to false. If the status is Resolved, it finds the same project and sets archived to true. The flow uses both the Clockify node for search and a direct API call for the update. This keeps project lists accurate and lets managers see only the work that is still open.

Set up a Clockify API key and point your ticket tool or a test sender to the webhook URL. Expect less manual work and fewer mistakes, since projects update right when status changes. Ideal for helpdesk tickets, client issues, and tasks that end when a ticket is resolved.

• Webhook trigger receives a POST with ticket fields like number, customer name, and status.
• IF check evaluates if status is Resolved or not to choose the right path.
• Clockify search uses a dynamic name pattern from the webhook to find the exact project.
• HTTP PUT updates the Clockify project to archived or active based on the status.
• HTTP Header Auth passes the Clockify API key securely in each update call.
• Sets isPublic to true on updates to keep visibility rules consistent.

• Reduce manual project updates from 30 minutes a day to 5 minutes
• Automate 90 percent of project archiving tasks
• Improve project data accuracy by 95 percent using ticket status
• Keep Clockify project lists clean for faster reporting
• Connect ticket updates to Clockify without custom code

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Clockify and Webhook.site. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create a Clockify credential. Choose the Clockify API credential type, enter your Clockify API key from the Clockify API page, and save it.
4. Open each Clockify node in the workflow and select your new Clockify credential in the Credential to connect with dropdown.
5. Double click each HTTP Request node. In the Credential to connect with dropdown, create a new HTTP Header Auth credential. Set the header name to X-Api-Key and the value to your Clockify API key. Save and select it.
6. In both Clockify nodes, replace the workspaceId value with your actual Clockify workspace ID. You can copy it from your Clockify workspace settings or from the workspace URL.
7. Open the Webhook node and copy the Production URL. In your ticket system or test tool, send a POST to this URL with a JSON body that includes attributes.number, attributes.customer_business_then_name, and attributes.status.
8. Check the name filter in the Clockify nodes. It builds a project name from the ticket number and customer name. Adjust the expression to match how you name projects in Clockify.
9. Test an open ticket case. Send a POST where attributes.status is not Resolved. Confirm in Clockify that the matching project shows archived set to false.
10. Test a resolved ticket case. Send a POST where attributes.status is Resolved. Confirm the same project now shows archived set to true.
11. If no project updates, make sure the project name in Clockify exactly matches the name pattern, your workspaceId is correct, and your API key is valid.