> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # Clockify > Read Clockify workspaces, clients, projects, tasks, time entries and reports in Hebno, and log time to Clockify after you confirm. The Clockify integration makes tracked time available in your client work. Ask how many hours a client took last month, how close a project is to its estimate, or what the team logged on an engagement this week, and Hebno answers from Clockify with each project and time entry cited. When you ask Hebno to log time, it shows a confirmation card and writes to Clockify only after you confirm. ## At a glance | | | | - | - | | **Connection** | Personal connection. Each member connects their own Clockify account. | | **Default access** | Read and write | | **Attach** | Projects, clients, a member's time entries for a week, summary and detailed reports | | **Search** | Hebno searches Clockify when a request mentions a client, project, task, tag, hours or a period | | **Link** | A project links to one or more Clockify projects | | **Write** | Log time. Every write needs a person to confirm. | ## Before you start You need: * A Clockify account that is a member of the workspace you want to use. * An allowed integration. An owner or admin sets **Clockify** to **Allow** under **Admin → Connectors → Catalogue**. * A Clockify API key. In Clockify, open **Profile settings → Preferences → Advanced**, select **Manage API keys** and generate a key named for Hebno. Clockify has no scopes. The API key acts with your own Clockify role: | Clockify role | What Hebno can read for you | | - | - | | **Regular user** | Your own time entries, and public projects and projects you are a member of | | **Team manager** or **Project manager** | Time of the people or projects you manage | | **Admin** or **Owner** | All clients, projects, tasks and time entries in the workspace, and reports for everyone | ## Connect Clockify **1. Start the connection** Open **Settings → Connections**, find **Clockify** and select **Connect**. You can also select **Connect** from the prompt in a chat. **2. Paste your API key** Paste the API key and select **Connect**. Hebno detects your Clockify region and lists the workspaces your account belongs to. **3. Choose a default workspace** Pick the workspace Hebno uses for new time entries. You can still ask about any workspace you belong to. The card shows **Connected** with your Clockify email. Hebno reads and writes with your own permissions, so you see only the projects and time that your Clockify role can open. Keys are encrypted at rest. Select **Disconnect** at any time, or ask an admin to revoke the connection under **Admin → Connectors → Connections**. Deleting the key under **Manage API keys** in Clockify also ends the connection. ## What Hebno reads | Clockify object | Fields Hebno uses | Typical questions | | - | - | - | | **Workspace** | Name, currency, rounding, required field settings | "Which workspace is the Contoso work in?" | | **Client** | Name, archived flag | "Which projects do we track for Contoso Retail?" | | **Project** | Name, client, billable flag, estimate, budget, colour, public flag, members | "How close is the Contoso project to its time estimate?" | | **Task** | Name, project, assignees, estimate, status | "Who is assigned to the interview task?" | | **Time entry** | User, project, task, description, start, end, duration, tags, billable flag, approval status | "What did I log on Contoso last week?" | | **Tag** | Name | "How much time is tagged workshop this month?" | | **Summary report** | Time grouped by client, project, user, task or tag for a period, billable totals and amounts where your role allows | "Break down October hours on Contoso by person." | | **Detailed report** | Each time entry for a filter and period | "List every entry on the Contoso project from 2 to 6 November." | Reports come from the Clockify Reports API at the time of the request, so totals match what you see in Clockify. Amounts and rates appear only if your role can see them. Reads are live. Hebno queries Clockify when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts a reply uses become part of the conversation. Anyone you share the conversation with can read them, including time entry descriptions from Clockify. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. | Action | Clockify object | Fields on the card | | - | - | - | | **Log time** | Time entry | Workspace, project, task, description, date, start and end time, tags, billable | ![Confirmation card for Clockify with editable fields](https://mintcdn.com/hebno/JIjAXWoGoB3PLSSb/images/card-clockify.png?fit=max\&auto=format\&n=JIjAXWoGoB3PLSSb\&q=85\&s=66ae2b5b76a670ee24ca44fd57583752) A Clockify change pending confirmation. Nothing is written until you confirm. Hebno logs completed entries only. It never starts or stops a running timer, edits or deletes existing entries, submits or approves timesheets, or changes projects, rates or workspace settings in Clockify. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant Clockify You->>Hebno: Log 2 hours on Contoso interviews this afternoon Hebno->>Clockify: Find the Contoso project and task in your workspace Clockify-->>Hebno: Project Contoso pricing review, task Stakeholder interviews Hebno-->>You: Confirmation card with project, task, start, end You->>Hebno: Confirm Hebno->>Clockify: Create time entry as you Clockify-->>Hebno: Time entry created Hebno-->>You: Done, with the entry details ``` Writes are made as your Clockify user, so the entry appears in your own time tracker and reports. ## Link a project to a Clockify project Linking marks which Clockify projects belong to an engagement, so you can ask "how many hours so far?" without naming the project. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **Clockify**. 3. Choose the workspace, search by project or client name, and select the project. Repeat for each Clockify project in the engagement. In chats tagged to the project, Hebno starts with the linked Clockify projects for any time question, and time cards default to them. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use Clockify in chat * **Attach**: open the **+** menu, choose **Sources → Clockify**, and pick a project, a client, your week or a report. Or type `/` and choose **Clockify**. * **Ask**: name the client, project or period in your request. For example: > How many billable hours did we log on Contoso Retail in October, and how does that compare with the project estimate? > Which tasks on the Contoso pricing review took longer than estimated? > Log 1.5 hours on Contoso, readout preparation, for today from 14:00 with the tag workshop. * **Research runs** show a **Checking Clockify** step, with a chip for each project, report and time entry it read. * **Agents** can read Clockify on a schedule, for example a Friday list of people with fewer than 30 hours logged this week. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Connect** fails with `401 Unauthorized` | The key was deleted or mistyped. Generate a new key under **Manage API keys** and connect again. | | A workspace is missing after connecting | The workspace is on a different Clockify region from the one detected. Disconnect, reconnect and choose the region shown in your Clockify address. | | A time entry fails with a required field message | The workspace requires a project, task, tag or description. Fill them in on the card and select **Confirm** again. | | A time entry fails for a past week | An admin locked timesheets before a date, or the week is approved. Ask a workspace admin to reopen the week. | | Other people's time or amounts are missing | Your Clockify role cannot see them. Ask a workspace admin for manager or admin access. | | Requests fail with `429 Too Many Requests` | Clockify limits requests per second for each key. Wait a moment, or narrow the period. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Toggl Track](https://hebno.com/docs/integrations/toggl-track.md) * [Harvest](https://hebno.com/docs/integrations/harvest.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.