--- title: "Clockodo Integration" description: "Clockodo is the German time tracking and workforce management platform. Agents start and stop the clock, create and report on time entries, manage customers, projects, and services, and handle absences, target hours, overtime, and work time change requests." url: https://flowrunner.ai/integrations/clockodo date_modified: 2026-09-04T14:52:04-07:00 --- # Clockodo [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Clockodo is the German time tracking and workforce management platform. Agents start and stop the clock, create and report on time entries, manage customers, projects, and services, and handle absences, target hours, overtime, and work time change requests. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 146 actions · Basic auth · available [Clockodo website](https://clockodo.com/) · [Platform Documentation](https://docs.clockodo.com/) · Capability data verified 2026-08-24 1. The month closes and the delivery team's time has to be reconciled before invoicing 2. List Grouped Entries returns hours and revenue grouped by customer, project, and day 3. List Project Reports reads budget consumption against each project's calculated figures 4. Agent flags entries with no project, the wrong service, or a billable flag that contradicts the rate rule 5. Update Grouped Entries is called once, which returns a confirmation key and changes nothing 6. The corrections and the totals they would produce are posted to the project lead 7. The lead approves, and only then is the confirmation key spent on the second call ## What This Integration Enables Clockodo is not a stopwatch with reports attached. Its API is one hundred and forty-six operations wide because it covers the whole employment record that time tracking feeds: target hour schedules, holiday quotas and carryovers, overtime carryovers and reductions, regional public holiday calendars, recorded presence and the change requests that correct it. Hours entered here do not just describe work, they resolve into revenue through a rate tree and into entitlement through a quota. That is the reason to automate it, and the reason to be careful about it. FlowRunner agents run the clock, create and correct time entries, read Clockodo's own grouped and calculated reports rather than recomputing totals from raw entries, manage customers, projects, subprojects, services, and lump sums, maintain the hourly rate tree, and handle absences, target hours, balances, and work time change requests. Two mechanics shape how a flow should be built. Rates resolve by specificity: Clockodo walks the tree and the most specific matching rule wins, with sibling order breaking a tie, so a flow that changes a rate is changing what every unmatched hour is worth. And the API key carries one person's access rights, which means a permission refusal is a statement about that person rather than about the credential being wrong. ### Without FlowRunner **Month end is an archaeology exercise**: Somebody opens a spreadsheet and works out what happened three weeks ago **Corrections are made one entry at a time**: Fixing a mis-booked week means editing each entry by hand and hoping none was missed **Entitlement lives in a second system**: Holiday balances and overtime are tracked apart from the hours that produce them ### With FlowRunner **The reconciliation runs continuously**: Grouped totals and budget consumption are read on a schedule, not at the deadline **Bulk corrections are proposed as one reviewable change**: The agent assembles the correction and shows the totals it would produce **One record answers both questions**: Hours, absences, target hours, and balances are read from the same place ## Use Case Scenarios ### Budget alerts that use the vendor's arithmetic Rather than summing raw entries, the agent reads List Project Reports, which carries tracked time, budget consumption, and revenue as Clockodo already calculates them. Projects crossing a consumption threshold are posted to the project lead in [Slack](https://flowrunner.ai/integrations/slack) with the subproject breakdown attached, because a subproject is separately budgeted and the parent total hides where the overrun actually is. Where a project is complete, Complete Project stops further tracking against it while leaving everything already tracked in reports, which is the reversible move that deleting a project is not. ### Absence requests routed to the person who decides An absence request is created without a status, which in Clockodo is an enquiry rather than a decision. The agent reads List Absences for the requester's team and List User Non-Business Days to work out who is actually off on the same dates, since that read resolves each person's calendar assignment rather than assuming a single company calendar. Coverage conflicts and remaining quota are posted to the approving manager, who approves or declines. Update Absence records the decision, and the approved dates are mirrored into [Personio](https://flowrunner.ai/integrations/personio) so the HR record and the time record agree. The agent never books an absence as already approved. ### Invoice preparation that stops at the money boundary At month end, List Grouped Entries produces a nested breakdown by customer, then project, then day, with hours and revenue on each level. The agent checks each project's billable flags against the rate rules that would apply, flags entries with no service or an obviously wrong one, and assembles the corrected picture. Approved totals become draft invoices in [lexoffice](https://flowrunner.ai/integrations/lexoffice), and the reconciliation appends to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Set Project Billed then records what was actually invoiced, which is the flag Clockodo's own project reports use to separate delivered work from billed work. ## Human-in-Loop Highlight Clockodo already built the pause, and the honest design is to use it rather than to invent one. Update Grouped Entries and Delete Grouped Entries both edit or remove every time entry matching a date range and filter, and both are deliberately two-step: the first request changes nothing and answers with a confirmation key, and only a second request carrying that key applies the change. There is no undo on the delete, and the update can move a week of hours onto a different project or mark them billed, which changes what a customer is charged. A poorly built flow consumes both calls in a row and turns a vendor-designed checkpoint into a formality. A FlowRunner agent does not hold the key. It makes the first call, then posts what came back: "This correction covers 214 entries between 1 and 31 August for the Meridian project, moving them to Meridian Phase 2 and marking them billable. Current total 386.5 hours at 41,200 EUR. After the change: 386.5 hours at 44,700 EUR. Nothing has changed yet. Apply?" The project lead answers, and the second call runs with their approval attached to it. The same rule covers Create Absence, where setting a status of approved records leave as already granted and bypasses the manager who would otherwise have granted it, and Decline Work Time Change Request, which is final in a way that deleting a pending request is not. This is the [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord) in its simplest form: the agent does the assembling and a person spends the key. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 146 actions ### The clock 5 - **Get Running Clock** Returns the time entry the clock is currently running on, or an empty result when nothing is running. Administrators can read another co-worker's clock. - **Start Clock** Starts the clock on a new time entry against a customer and a service. Backdating raises two separate questions the operation asks explicitly: what happens to entries already covering that period, and whether the punch is happening now even though the entry starts earlier. - **Change Running Clock** Adjusts the start time or accumulated duration of the entry the clock is running on. Clockodo treats the prior values as an optimistic lock, so a flow supplies them where a concurrent change would matter. - **Stop Clock** Stops the running clock and closes its time entry. Starting a new one in the same call is how a break or a task switch is recorded without losing the clock. - **Start Favorite** Starts the clock from a saved favorite, which carries its own customer, project, service, billable flag, and description. ### Time entries 9 - **List Time Entries** Returns time entries inside a date range, which is required on this route. Filters narrow by user, customer, project, service, billable state, or text, and the enhanced form has Clockodo resolve names into each row. - **Get Time Entry** Returns one time entry with its customer, project, service, user, duration, billable state, and hourly rate. - **Create Time Entry** Records a finished block of time, or a lump sum charge, without using the clock. The rate is derived from the customer, project, and service unless it is overridden. - **Update Time Entry** Changes an existing time entry. The description is the one field where an empty string is meaningful, because Clockodo clears the stored text when it receives one. - **Delete Time Entry** Permanently deletes one time entry. There is no undo, and an entry already marked as billed is normally protected by Clockodo's own rules. - **Search Entry Descriptions** Searches the descriptions already used on time entries, which is how Clockodo's own client offers autocompletion. The suggestion set differs by context. - **List Grouped Entries** Returns time aggregated into groups rather than as individual entries, which is Clockodo's reporting shape. Grouping nests, so customer then project then day gives a three-level breakdown of hours and revenue. - **Update Grouped Entries** Edits every time entry matching a date range and filter in one call. It is deliberately two-step: the first request changes nothing and returns a confirmation key, and only a second request carrying that key applies the edit. - **Delete Grouped Entries** Deletes every time entry matching a date range and filter, using the same two-step confirmation key. There is no undo, which is why this page's human gate sits on the key. ### Customers 6 - **List Customers** Returns customers with their color, number, and default billable setting. A management scope returns the wider list a co-worker with customer management rights would see. - **Get Customer** Returns one customer with its number, color, note, and default billable setting. - **Create Customer** Creates a customer, which is the top level a project and its tracked time hang from. Several fields require elevated rights, and Clockodo refuses the whole call rather than ignoring them. - **Update Customer** Changes a customer's name, number, color, note, or default billable setting. Deactivating is how a customer is retired: existing time stays in reports and the customer stops appearing in pickers. - **Delete Customer** Deletes a customer. A dry run first shows what would be removed, because Clockodo refuses the delete while projects or tracked time remain unless forced, and forcing takes that data too. - **Count Customer Projects** Returns how many projects each customer has, which is the cheap way to find out whether deleting a customer would take projects with it. ### Projects and subprojects 15 - **List Projects** Returns projects with their customer, budget, deadline, and completion settings, narrowed by filter. - **Get Project** Returns one project with its customer, budget, start date, deadline, and automatic completion setting. - **Create Project** Creates a project under a customer. The start date and deadline are behavioral rather than decorative: tracking becomes available on the start date, and automatic completion closes the project on the deadline. - **Update Project** Changes a project's name, customer, budget, dates, or flags. Only supplied fields are written, so removing a budget entirely takes an explicit null rather than an empty value. - **Complete Project** Marks a project complete or reopens it. Completing stops further tracking while leaving everything already tracked in reports, which is the reversible alternative to deleting it. - **Set Project Billed** Records that a project has been invoiced, optionally with the amount. It is the flag Clockodo's project reports use to separate delivered work from invoiced work. - **Create Next Project Interval** Rolls a recurring project forward by creating its next interval, copying settings into a fresh period. It suits retainer work tracked against a new project each month or quarter. - **Delete Project** Deletes a project. A dry run first shows what would go with it, because Clockodo refuses while tracked time remains unless forced, and forcing deletes that time too. - **List Project Reports** Returns Clockodo's project report rows: tracked time, budget consumption, and revenue per project and subproject. This is the read a budget alerting flow wants, because the figures are already calculated. - **List Subprojects** Returns subprojects, which split a project into separately budgeted parts. - **Get Subproject** Returns one subproject with its parent project, budget, and dates. - **Create Subproject** Creates a subproject with its own budget, dates, and service restrictions, for a project that needs several separately tracked parts. - **Update Subproject** Changes a subproject's name, budget, dates, or flags. There is no field for moving a subproject to a different project, so it stays under the one it was created in. - **Complete Subproject** Marks a subproject complete or reopens it, stopping further tracking while leaving tracked time in reports. - **Delete Subproject** Deletes a subproject. A dry run first shows what would go with it, and forcing takes any tracked time hanging from it. ### Services and lump sums 10 - **List Services** Returns services, which are the kinds of work time is booked against. Every time entry needs one. - **Get Service** Returns one service with its number, note, and active state. - **Create Service** Creates a service. Some fields require elevated rights, and Clockodo refuses the whole call rather than dropping them. - **Update Service** Changes a service's name, number, note, or active state. Deactivating retires it without touching the time already booked against it. - **Delete Service** Deletes a service. A dry run first shows what would go with it, and forcing deletes the entries that reference it. - **List Lump Sum Services** Returns lump sum services, which are fixed price line items charged by the unit rather than by tracked time. - **Get Lump Sum Service** Returns one lump sum service with its unit price and unit label. - **Create Lump Sum Service** Creates a fixed price service charged per unit. The price is the price of one unit, and the quantity is chosen on each entry that uses it. - **Update Lump Sum Service** Changes a lump sum service's name, unit price, unit label, or active state. Entries already recorded keep the price they were charged at. - **Delete Lump Sum Service** Deletes a lump sum service. A dry run first shows what would go with it, and forcing removes entries that charge it. ### Hourly rates 7 - **List Hourly Rates** Returns the hourly rate tree. Clockodo resolves a rate by walking it, so a rule naming a customer, project, service, and user is more specific than one naming only a customer, and the most specific match wins. - **Get Hourly Rate** Returns one rate rule with the customers, projects, services, and users it applies to. - **Create Hourly Rate** Adds a rate rule to the tree. A parent decides where the rule sits, and leaving a dimension's list empty means any, so a rule with only a customer applies to all of that customer's work. - **Update Hourly Rate** Changes a rate rule's amount or the dimensions it applies to. A supplied list replaces the stored one rather than adding to it. - **Set Default Hourly Rate** Sets the company-wide fallback rate used when no rule matches. Every unmatched hour is valued at this figure, so it decides the revenue reported for work nobody wrote a rule for. - **Sort Hourly Rates** Reorders the rate rules under one parent. Order decides which rule wins between siblings that are equally specific, so this is how a tie is broken. - **Delete Hourly Rate** Deletes a rate rule. Work that matched only this rule falls back to the next less specific match, and to the default rate when none exists. ### People and teams 14 - **List Users** Returns the co-workers in the account with their role, language, wage type, and edit lock settings, narrowed by scope to the people this key may act on for a given purpose. - **Get User** Returns one co-worker with their role, team, language, time zone, wage type, and edit lock configuration. - **Get Current User** Returns the co-worker the API key belongs to, together with the company settings that apply to them. Calling it first avoids hard-coding an identifier. - **Get My Aggregates** Returns the running totals Clockodo shows the signed-in co-worker: overtime balance, remaining holiday, and today's tracked time. It is the read a daily digest wants, because the arithmetic is already done. - **Create User** Invites a co-worker into the account. Whether the person is actually told is a separate setting that defaults to off, so a user created without it exists but never receives an invitation. - **Update User** Changes a co-worker's record. Only supplied fields are written, which makes it safe for flipping a single setting such as deactivating a leaver. - **Delete User** Deletes a co-worker. Deactivating is almost always the right move instead, because a forced delete takes the person's tracked time with it. A dry run shows what is at stake. - **Get User Customer And Project Access** Returns which customers and projects one co-worker may add time to, report on, and edit, resolved rather than inferred from group membership. - **Get User Service Access** Returns which services one co-worker may book time against, resolved from their access groups and any individual overrides. - **List Teams** Returns the teams co-workers are grouped into, each with its leader and members. Teams are what absence approval and reporting are usually scoped by. - **Get Team** Returns one team with its leader and the co-workers in it. - **Create Team** Creates a team and optionally fills it. Naming a leader is what gives that person the team's approval and reporting rights. - **Update Team** Renames a team, changes its leader, or sets its membership. The member list replaces the stored one rather than adding to it. - **Delete Team** Deletes a team. The co-workers in it are not deleted, they simply stop belonging to a team. ### Absences 5 - **List Absences** Returns holiday, sickness, and other absences. Clockodo returns the current year by default rather than everything, so a flow needing a specific year asks for it. - **Get Absence** Returns one absence with its type, dates, approval status, and any note. - **Create Absence** Books an absence for a co-worker. The status decides whether this is a request or a decision: leaving it empty enquires, while setting it to approved records leave as already granted and bypasses the approval a manager would otherwise give. The override option names absences Clockodo may shorten or delete to make room. - **Update Absence** Changes an absence's dates, type, or approval status. Approving or declining here is how a flow acts on a pending request, and cancelling withdraws one already granted. - **Delete Absence** Permanently deletes an absence and returns the days to the co-worker's quota. Cancelling keeps the record, which is usually what an audit trail wants instead. ### Target hours 5 - **List Target Hours** Returns the target hour schedules that say how much each co-worker is expected to work. A schedule is dated, so a change from full time to part time is two records rather than one edited one. - **Get Target Hours** Returns one target hour schedule with its per weekday hours or monthly target and its validity period. - **Create Target Hours** Creates a target hour schedule from a given date. A weekly schedule uses per weekday hours and a monthly one uses a monthly target, and the working day flags are separate from the hour values because a day can be a working day with zero planned hours. - **Update Target Hours** Changes an existing target hour schedule. Clockodo requires the type and start date on every update even when neither is changing. - **Delete Target Hours** Deletes a target hour schedule. The co-worker falls back to whichever other dated schedule covers the period, or to the company default. ### Holiday and overtime balances 20 - **List Holiday Quotas** Returns the holiday allowances granted to co-workers. A quota is dated by year range, so a changed allowance is several records. - **Get Holiday Quota** Returns one holiday quota with the co-worker, the years it covers, and the number of days. - **Create Holiday Quota** Grants a co-worker a holiday allowance from a given year onward. Leaving the end year empty makes it open ended, which is the usual case. - **Update Holiday Quota** Changes a holiday allowance record's years, day count, or note. There is no field for moving the record to a different co-worker. - **Delete Holiday Quota** Deletes a holiday allowance record. The co-worker falls back to whichever other quota covers the year, or to the company default. - **List Holiday Carryovers** Returns holiday days carried over into a year from the one before, which Clockodo keeps separate from the quota so allowance and leftover stay distinguishable. - **Get Holiday Carryover** Returns one holiday carryover record. - **Create Holiday Carryover** Records holiday days carried into a year. Clockodo accepts only whole and half days here. - **Update Holiday Carryover** Changes a holiday carryover's year, day count, or note, again in whole and half days only. - **Delete Holiday Carryover** Deletes a holiday carryover record, removing those days from the co-worker's balance for that year. - **List Overtime Carryovers** Returns overtime hours carried into a year for each co-worker, which is where a flextime balance starts from. - **Get Overtime Carryover** Returns one overtime carryover record. - **Create Overtime Carryover** Records the overtime balance a co-worker starts a year with. A negative figure is valid and means they begin the year owing hours. - **Update Overtime Carryover** Changes an overtime carryover's year, hours, or note. - **Delete Overtime Carryover** Deletes an overtime carryover record, so the co-worker's balance for that year starts from zero instead. - **List Overtime Reductions** Returns overtime reductions, which record hours paid out or written off rather than taken as time in lieu. They are what stops a flextime balance growing forever. - **Get Overtime Reduction** Returns one overtime reduction record. - **Create Overtime Reduction** Writes hours off a co-worker's overtime balance on a given date, for example because they were paid out. Hours taken as time off belong in an absence of the corresponding type instead. - **Update Overtime Reduction** Changes an overtime reduction's date, hours, or note. - **Delete Overtime Reduction** Deletes an overtime reduction, returning those hours to the co-worker's balance. ### Public holiday calendars 16 - **List Non-Business Groups** Returns the public holiday calendars in the account. Each group is a set of non-business days, and co-workers are assigned to one so teams in different countries get their own holidays. - **Get Non-Business Group** Returns one public holiday calendar. - **Create Non-Business Group** Creates a public holiday calendar, optionally pre-filled from one of Clockodo's regional presets. Without a preset it starts empty. - **Update Non-Business Group** Renames a public holiday calendar. Its days are managed separately. - **Delete Non-Business Group** Deletes a public holiday calendar and the days inside it. Co-workers assigned to it fall back to the company default calendar. - **List Non-Business Days** Returns the public holidays and other non-working days in a calendar for a year. Clockodo resolves moving feasts, so a recurring day comes back on the date it actually falls. - **Get Non-Business Day** Returns one non-business day, resolved into a given year when it recurs. - **Create Non-Business Day** Adds a non-working day to a calendar. The type decides how the date is expressed: a yearly recurrence, a one-off in a named year, or one of Clockodo's own moving feasts selected by identifier. - **Update Non-Business Day** Changes a non-business day's name, type, date, or half day flag. There is no field for moving the day to a different calendar. - **Delete Non-Business Day** Removes a day from a calendar, so it becomes an ordinary working day for everyone assigned to it. - **List User Non-Business Days** Returns the non-business days that actually apply to each co-worker in a year, after calendar assignment is resolved. This is the read to use when a flow needs to know whether a specific person is off on a specific date. - **List User Calendar Assignments** Returns which public holiday calendar each co-worker follows and from when. The assignment is dated, so a relocation is two records rather than one edited one. - **Get User Calendar Assignment** Returns one calendar assignment record. - **Assign User Calendar** Puts a co-worker on a public holiday calendar from a given date. Leaving the end date empty makes it open ended. - **Update User Calendar Assignment** Changes which calendar an assignment points at, or the dates it covers. - **Remove User Calendar Assignment** Deletes a calendar assignment, so the co-worker falls back to the company default calendar for that period. ### Recorded work times and change requests 6 - **List Work Times** Returns one co-worker's recorded presence: when they clocked in and out each day, as distinct from what they booked time against. All three parameters are required, so this route always reads one person over one range. - **List Work Time Change Requests** Returns requests co-workers have made to correct their recorded presence, with their status. An approval scope returns only the ones this key can act on. - **Create Work Time Change Request** Asks for a co-worker's recorded presence on one day to be corrected. There can be only one pending request per co-worker per day, and creating a second silently replaces the first, so existing requests are worth reading first. - **Approve Work Time Change Request** Approves a pending correction, writing the proposed presence blocks onto the co-worker's record for that day. - **Decline Work Time Change Request** Declines a pending correction, leaving the recorded presence unchanged. A declined request can no longer be deleted, so declining is final in a way that deleting a pending one is not. - **Delete Work Time Change Request** Withdraws a pending correction request. It only works while the request is still pending. ### Favorites 5 - **List Favorites** Returns the saved favorites a co-worker can start the clock from, each carrying its own customer, project, service, billable flag, and description. - **Get Favorite** Returns one favorite with everything the clock would be started with. - **Create Favorite** Saves a one-click clock start. Clockodo requires the name, customer, service, color, and position, so all five are mandatory even though several look cosmetic. - **Update Favorite** Changes what a favorite starts the clock on, or how it is presented. Only supplied fields are written. - **Delete Favorite** Removes a saved clock start. Time already tracked through it is untouched. ### Access groups and individual access 20 - **List Access Groups** Returns the access groups that decide what co-workers may see and do, each with its members and its customer, project, and service permissions. - **Get Access Group** Returns one access group with its members. - **Create Access Group** Creates an access group and optionally fills it. A new group starts with no access to anything; permissions are set afterwards. - **Update Access Group** Renames an access group or sets its membership. The member list replaces the stored one rather than adding to it. - **Delete Access Group** Deletes an access group. Its members lose whatever it granted them and fall back to their individual access. - **Get Access Group Customer And Project Access** Returns which customers and projects an access group reaches, and at what level. - **Set Access Group Customer Access** Sets one access group's permission on one customer. The permission and the level are two separate axes, and a custom level defers to the per project settings. - **Set Access Group General Customer Access** Sets an access group's blanket permission across all customers, which is the fallback when no per customer setting applies. - **Set Access Group Project Access** Sets one access group's permission on one project. A project permission has only full access or none, because there is no further level to defer to. - **Get Access Group Service Access** Returns which services an access group may book time against. - **Set Access Group Service Access** Sets one access group's permission on one service. Only the data entry permission exists for services, because there is nothing to report on at that level. - **Set Access Group General Service Access** Sets an access group's blanket permission across all services. - **Get Individual Customer And Project Access** Returns one co-worker's individual customer and project overrides, as distinct from what their access groups give them. - **Set Individual Customer Access** Sets one co-worker's individual permission on one customer, overriding their access groups. - **Set Individual General Customer Access** Sets one co-worker's blanket individual permission across all customers. - **Set Individual Project Access** Sets one co-worker's individual permission on one project. - **Get Individual Service Access** Returns one co-worker's individual service overrides. - **Set Individual Service Access** Sets whether one co-worker may book time against one service, overriding their access groups. - **Set Individual General Service Access** Sets one co-worker's blanket individual permission across all services. - **Clear Individual User Access** Removes every individual override from one co-worker, so their permissions come entirely from their access groups again. It is the reset for when overrides have accumulated and nobody can tell what a person can actually see. ### Reports and account 3 - **List User Reports** Returns Clockodo's per co-worker yearly report: target hours against hours worked, overtime, holidays taken, and remaining. The detail level controls how deep the breakdown goes, and asking for more than a flow needs makes the response very large. - **Get User Report** Returns the yearly report for one co-worker, with the same detail levels. - **Get Subscription** Returns the account's plan, seat count, and which paid modules are switched on. It is worth reading before a flow relies on a feature, because a route can exist and still refuse when the module is not booked. ## Frequently Asked Questions ### What can FlowRunner do with Clockodo? FlowRunner agents can run Get Running Clock, Start Clock, and Change Running Clock in Clockodo, plus 143 more actions. ### Does connecting Clockodo to FlowRunner require OAuth? No. Clockodo connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Clockodo trigger a FlowRunner workflow automatically? Clockodo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Clockodo?** This integration exposes Clockodo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/clockodo. Site index: https://flowrunner.ai/llms.txt