Timeglass webhooks send approved, categorized time from Timeglass to the other tools your team runs on, such as Asana, ClickUp, a CRM, or an ERP. Admins add an endpoint in Timeglass settings, and as soon as time is approved, Timeglass sends it there. Your other systems stay up to date, and nobody on your team copies hours over by hand.
Knowledge workers use more than one tool to run their business. Time often lives in one place while projects and clients live in another, and someone usually ends up spending part of their week keeping the two in agreement. We built webhooks so that work happens on its own.
Why time tracking inside a project management tool wasn't working
This feature started with a request from a customer, a consulting firm of about 70 people. They came to us because time tracking inside their project management tool had low adoption. Their engineers and project managers bounce between several workstreams each day, and stopwatch timers and per-ticket hour logging were hard to keep up with every time someone switched tasks.
Timeglass handled the capture side by recording their work automatically and attributing it to the right client, project, and task. Their project management tool remained the place where they kept their projects, clients, and tasks, and over time the two systems started to fall out of sync.
To keep them aligned, the team was using the Timeglass MCP server to pull data out and update their project management tool by hand. That approach worked, but it added a recurring chore to a rollout that was meant to remove chores. They asked us for an automatic way to keep both systems in agreement, and webhooks are the result.
Other customers have asked for something similar. An agency evaluating Timeglass wants to keep its current project management platform and use Timeglass data for that platform's time tracking. Other teams have asked whether Timeglass can connect to their CRM, ERP, or internal knowledge systems. Taken together, these requests showed us that people want their Timeglass data to flow into the tools they use every day.
How Timeglass webhooks sync time, projects, and clients
Timeglass calls your endpoint as soon as time is approved, so your team doesn't need to write a scheduled job that keeps checking our API for changes. The sync runs in both directions: Timeglass pulls your projects and clients in, and sends approved time back out. Here is how the flow works from start to finish:
1. An admin adds an endpoint URL in Timeglass settings and turns on the project and client sync, approved time, or both.
2. Shortly before timesheets are prepared each day, Timeglass asks your endpoint for your current projects, clients, and categories.
3. Timeglass captures work through the day and organizes it into draft timesheet entries.
4. When time is approved or edited (by a manager, by the person submitting their timesheet, or automatically), Timeglass sends it to your endpoint.
5. A small service on your side receives that data and writes the tasks, projects, clients, and hours into your system.
Webhooks build on the existing Timeglass API, so anything you can read from the API can now be sent to you automatically.
What you can connect: Asana, ClickUp, a CRM, or an ERP
Because your endpoint decides where the data goes, webhooks can connect Timeglass to almost any tool. For teams that want time tracking in Asana or ClickUp without asking everyone to run timers, this is the path: Timeglass captures the time, and your endpoint writes it into the tool.
Tools with a consistent data model, such as Asana, are the simplest to connect, and an adapter built for one team can usually be reused by others. Tools like ClickUp let each workspace define its own fields, so an adapter for those needs to be shaped around your specific setup. For timesheet, payroll, PSA, and ERP systems, Timeglass can send daily totals per person, project, and category instead of individual activities.
Setting up webhooks takes a developer, or us
Webhooks are designed for teams that have a developer or a technical admin who is comfortable writing and hosting a small service. For those teams, setup is fairly light, and our webhooks docs include a starter adapter in Node.js that you can use as a starting point.
If your team doesn't have a developer available, we're happy to help you build the receiving side and get the integration running. Talk to us.
Common Questions
Frequently asked questions
Does Timeglass have webhooks?
Yes. Workspace admins can add a webhook endpoint in Timeglass settings today. Timeglass then syncs your clients, projects, and categories once a day and sends approved time to your endpoint.
What data do Timeglass webhooks send?
Approved, categorized time, either as individual activities or as daily totals per person, day, project, and category. Before timesheets are prepared each day, Timeglass also asks your endpoint for your current projects, clients, and categories.
Can Timeglass handle time tracking for Asana or ClickUp?
Yes, through a small adapter your developer hosts. Asana's consistent data model makes it the simplest to connect. A ClickUp adapter is shaped around your workspace's custom fields.
Do I need a developer to use Timeglass webhooks?
Usually, since someone needs to host the receiving service. If you don't have one, our team will help you build it.
How are webhooks different from the Timeglass API and MCP server?
With the API, your system asks Timeglass for data. With the MCP server, an AI assistant like Claude or ChatGPT queries it. With webhooks, Timeglass sends approved time to you automatically, with no one asking.
Turn on webhooks in settings today
Webhooks are available now, and admins can find them in Timeglass settings. The setup guide and sample code are in our webhooks docs.
We built Timeglass so that nobody has to remember to track their time, and webhooks extend that same idea to keeping the rest of your stack up to date. If there's a tool you'd like to connect and you aren't sure where to start, reach out to our team and we'll help you get it set up.
