TMetric

TMetric is the work time tracking platform for teams. Agents control the running timer and time entries, manage tasks, projects, and clients, submit and approve timesheets, handle time off, pull reports, and create invoices and expenses.

Verified 105 actions API key available

TMetric website Platform Documentation Capability data verified 2026-08-24

The billing period closes and the invoice run starts on a schedule

List Timesheets and Get User Timesheet gather what each person submitted for the period

Get Timesheet Settings reports whether approving a sheet will lock the time inside it

List Invoiceable Projects and Get Projects Report reconcile approved hours against what can actually be billed

Create Invoice drafts one invoice per client, with the expense report attached where there is one

The account owner receives each draft with its hours, its rate and the entries standing behind every line

The owner approves each draft before Update Invoice Status turns it into a claim on the client

What This Integration Enables

Most time trackers stop at the timesheet. TMetric carries the whole billing chain in one place: time entries, timesheets and their approval, invoices with attachments and templates, expenses with their receipts, and the accounting system the finished invoice is copied into. That is what makes it worth automating from a finance chair rather than a delivery one. A FlowRunner agent working here is not tidying a tracker, it is moving work along a chain that ends in money leaving somebody's account.

TMetric is unusually honest about where that chain becomes hard to reverse, and the connector leans on the checks it provides. Get Project Related Entities and Get Client Related Entities report whether time entries, tasks or invoices depend on a record before anybody archives it. Create Task takes a dry run flag that returns exactly what would be created without saving. Get Timesheet Settings says whether approval will lock the time inside a period against further editing. There is also one behavior every flow must design around: TMetric's own documentation states that an added time entry overwrites existing entries it overlaps. It does not sit alongside them and it does not refuse, which makes an import over an already tracked day genuinely destructive. Reading the range first is not caution, it is the correct call. Where the chain reaches a client, FlowRunner's human-in-the-loop design puts a person in front of the step that cannot be walked back.

Without FlowRunner

The chain runs on copy and paste Hours are exported, re-totaled in a spreadsheet, and typed into an invoice

Corrections found too late A wrong line is spotted after the invoice is out, when fixing it means a credit note

Receipts arrive separately Expenses reach the client on a different day than the hours they belong to

With FlowRunner

The chain runs end to end Approved time becomes invoice lines without leaving the system that recorded it

Review before the one-way step Each draft is checked against its own entries while it is still a draft

Hours and costs travel together The expense report is attached to the invoice it belongs to before anybody looks at either

Use Case Scenarios

The invoice run that arrives already reconciled

At period close the agent walks the submitted timesheets, resolves what each person logged against List Invoiceable Projects, and compares the totals to Get Projects Report. Where a line looks wrong, an entry with a billable flag on a project that is not billable, an unapproved sheet, a project with no rate, the agent surfaces it rather than quietly excluding it. Drafts are then created with Create Invoice, expense reports attached with Attach Expense Report To Invoice, and each draft goes to its account owner with the entries behind every line linked. Approved invoices are mirrored into QuickBooks Online or Xero with Copy Invoice To External Service, and the PDF is filed wherever the finance team keeps them.
Receipts that reach the right expense

Expense capture in TMetric is a two-step upload for a good reason: Upload Expense Attachment stores the file as a draft held against the user rather than against any expense, and the next Create Expense call picks it up. An agent watching a receipts mailbox or a card feed does exactly that, in order, and it always finishes the pair. A flow that uploads and then fails leaves a dangling draft, so the error path calls Delete Expense Draft Attachment rather than leaving litter behind. Categories are kept in step from the chart of accounts through Create Expense Category and Update Expense Category Status, so a retired category stops appearing without deleting the history filed under it.
Tasks from the delivery system, without the surprises

TMetric distinguishes internal tasks, created in TMetric, from external ones pulled in by an integration with a system like GitHub. Create Task can only make an internal one, which is a useful boundary: a flow that mirrors work from elsewhere should let the integration sync do it and use Sync Integration and List Sync Jobs to watch that it happened. When the flow does create or rename a task, it uses the dry run first, because TMetric applies a task's name, assignee, description and tag changes to every time entry linked to it. That is the point of the route and also the reason a bulk rename gets checked before it runs.

Human-in-Loop Highlight

Update Invoice Status is the step where a draft stops being an internal document and becomes a claim on a client. Everything before it is editable: the lines, the rate, the attachments, even the underlying hours if the sheet has not been approved yet. Everything after it is a correction with a paper trail, and the underlying time is usually already locked, because TMetric's approval locks the entries inside the period when the workspace has that setting on. So the agent builds the entire invoice and stops. It posts to the account owner: "Northwind, October. 138.5 approved hours across 3 projects, 2 rates, plus an expense report of 4 receipts. One line is flagged: 11 hours on Northwind Discovery, which is not marked billable, so it is excluded. Total as drafted excludes it. Send, send including that line, or hold?" The owner answers. Only then does the agent move the status and copy the invoice into the accounting system. The agent did the reconciliation, which is the part people do badly at eleven at night on the last day of the month. It did not decide what to bill a client, which is not a reconciliation problem at all.

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

105 actions

Account

Get Current User Returns the person the token belongs to along with the workspaces it can reach and their ids, so a flow can discover its own workspace rather than having it hard coded.
Update Current User Changes the connected person's own profile.
Get Time Balance Returns the connected person's time balance against their schedule.
Get Individual Schedule Returns the working schedule a person's balance is measured against.

Members

Update Members Changes several workspace members in one call.
Update Member Changes one workspace member, including their role and rate.
List Managed Teams Lists the teams the connected person manages, which is what scopes an approval or escalation flow to the right people.

Time Entries

List Time Entries Lists entries. Leaving the user empty returns the authenticated person's entries rather than the workspace's, so a team report needs either one call per person or the reporting operations.
Get Latest Time Entry Returns the most recent entry. An entry with no end time is the running timer, which is how a flow knows whether anything is being tracked.
Start Timer Starts tracking by creating an entry with no end time. Backdating it makes it destructive in the same way a manual entry is, because TMetric overwrites what it overlaps.
Create Time Entry Files time. TMetric overwrites existing entries this one overlaps, so read the range first when the day may already be tracked.
Update Time Entry Corrects an existing entry, provided the period is not already locked by an approval.
Stop Timer Sets the end time on the running entry, defaulting to now.
Delete Time Entry Removes an entry.
Add Break Records a break against the connected person's day.
List Recent Time Entries Lists the entries a person has used recently, which is what a quick-resume picker is built from.
Pin Recent Time Entry Pins a recent entry so it stays available to resume.
List Project Tags Lists the tags available on a project, so a write uses a tag that exists rather than creating drift.
List Tracking Statuses Reports who is tracking right now and on what. The one call that answers for the whole workspace rather than for one person.

Tasks

List Tasks Lists tasks with filters where zero is a real value: an unassigned assignee, or records with no client, project or tag at all.
Get Task Returns one task.
Create Task Creates an internal task. It takes a dry run flag that returns exactly what would be created without saving anything.
Update Task Changes a task, and applies the same change to every time entry linked to it. That is the purpose of the route and the reason a bulk rename deserves a dry run first.
Delete Task Removes a task. The time entries survive and simply stop being linked to one.
Get Task Changes Returns what has changed on a task, which is the audit read behind a dispute about scope.
List Recent Tasks Lists recently touched tasks.
Get Deleted Task Returns a deleted task, which is what makes the restore below possible.
Restore Deleted Task Brings a deleted task back.

Projects and Clients

List Trackable Projects Lists the projects time can currently be tracked against. TMetric's v3 API publishes no plain project listing, so this is the nearest one and it is what the project picker uses.
Create Project Creates a project. Passing a client name rather than an id creates the client when it does not exist yet, which saves a round trip.
Duplicate Project Copies a project with its settings, which is how a repeating engagement starts without rebuilding it.
Get Project Related Entities Reports whether time entries, tasks or invoices depend on a project and whether it can be deleted. Read it before archiving anything.
List Project Managers Lists who manages a project, which is how an approval flow finds the right approver.
List Clients Lists the workspace's clients.
Get Client Related Entities Reports what depends on a client and whether it can be deleted. The same pre-check as the project version.

Reports

Get Projects Report Returns the project report for a period. With neither date given it covers the current month rather than all time.
Get Profitability Report Returns profitability by project. TMetric marks this experimental in its own specification, so its shape may change.
Get Report Filter Options Returns the filter values the token is allowed to see, so a filter built from it cannot ask for data that comes back refused.

Timesheets

List Timesheets Lists timesheets for a period, which is the starting read for any approval flow.
Get Timesheets Summary Returns the rolled-up view across the workspace's timesheets.
Get User Timesheet Returns one person's timesheet for a period.
Submit User Timesheet Submits a timesheet for approval on a person's behalf.
Change Timesheet Status Moves a timesheet to approved or rejected. Where the workspace locks approved time, this also closes the entries inside the period against further editing.
Change Timesheet Statuses In Bulk Moves several timesheets at once, with the same locking consequence.
Get Timesheet Settings Returns the workspace's approval settings, including whether approval locks the time. The read that tells a flow how reversible its next step is.
Update Timesheet Settings Changes those approval settings, which alters how every subsequent approval behaves.
Get Timesheet History Returns the history behind the workspace's timesheets.
Get User Timesheet History Returns the history behind one person's timesheets, which is the audit trail for a disputed period.
List Timesheet Approvers Lists who may approve, which is exactly who an escalation flow should be notifying.
Delete Timesheet Removes a timesheet.

Time Off

List Time Off Requests Lists time off requests, which is what explains a short period before anybody queries it.
List Time Off Requesters Lists who can be asked about, limited to what the token is allowed to see.
Get Time Off Policy Statistics Returns balances and usage against the workspace's time off policies.

Invoices

List Invoices Lists invoices with their status, which is the read behind any accounts receivable sweep.
Get Invoice Returns one invoice with its lines.
Create Invoice Drafts an invoice from billable work. Everything up to the status change is still editable.
Update Invoice Replaces an invoice record, so read it first and send it back with the changes applied rather than assuming omitted fields are preserved.
Update Invoice Status Moves an invoice out of draft and into a claim on the client. The operation this page's human gate exists for.
Copy Invoice Duplicates an invoice, which is how a recurring bill is raised without rebuilding it.
Get Invoice History Returns what has happened to an invoice, which is where a dispute about what was sent and when gets settled.
List Invoiceable Projects Lists the projects with billable work waiting, which is the correct starting point for an invoice run.
List Invoice Attachments Lists the files attached to an invoice.
Attach File To Invoice Attaches a file to an invoice.
Download Invoice Attachment Retrieves an attached file.
Attach Expense Report To Invoice Attaches the expense report to the invoice its costs belong to, so hours and costs reach the client together.
Delete Invoice Attachment Removes an attachment from an invoice.
Get External Invoice Returns the invoice as the connected accounting system holds it.
Copy Invoice To External Service Pushes the invoice into the connected accounting system, where it becomes an accounting record rather than a draft.
Download External Invoice PDF Retrieves the external system's rendered PDF, which is usually the document a client actually received.
Delete Invoice Removes an invoice.
List Invoice Item Types Lists the item types invoice lines are built from.
Create Invoice Item Type Creates an item type.
Update Invoice Item Type Changes an item type, which changes how future lines are described.
Delete Invoice Item Type Removes an item type.
List Invoice Templates Lists the invoice templates the workspace uses.
Get Invoice Template Returns one template.
Create Invoice Template Creates a template, which is what decides how every invoice built from it will read to a client.
Update Invoice Template Replaces a template record. Read it first and send it back with the changes applied.
Delete Invoice Template Removes a template.

Expenses

List Expenses Lists expenses, which is the read behind reimbursement and client rebilling alike.
Create Expense Records an expense, picking up any draft attachment the connected user has already uploaded.
Update Expense Replaces an expense record, so read it first and send it back with the changes applied.
Delete Expense Removes an expense.
Upload Expense Attachment Stores a receipt as a draft attachment held against the user rather than against any expense. The next expense created picks it up.
Delete Expense Draft Attachment Discards a draft attachment, which is what an error path should call so a failed flow leaves nothing dangling.
Download Expense Attachment Retrieves a stored receipt.
List Expense Categories Lists the expense categories the workspace defines.
Create Expense Category Creates a category.
Update Expense Category Changes a category.
Update Expense Category Status Retires or reactivates a category without deleting what has been filed under it.
Delete Expense Category Removes a category.

Integrations and Notifications

List Integrations Lists the integrations pulling tasks into TMetric from other systems.
Get Integration Returns one integration's configuration.
Create Integration Connects another system so its work appears as external tasks.
Update Integration Replaces an integration record. Read it first and send it back with the changes applied.
Sync Integration Runs a sync, which is how external tasks actually arrive.
List Sync Jobs Lists sync runs and their outcome, so a flow can notice a sync that quietly stopped working.
List Integration Taxes Lists the tax settings an integration carries.
Delete Integration Disconnects an integration.
List Notifications Lists the connected person's notifications.
Count Notifications Returns how many are waiting, which is the cheap poll.
Update Notification Status Marks one notification read or unread.
Update Notification Statuses In Bulk Marks several at once.
Get Notification Settings Returns what the connected person is notified about.
Update Notification Settings Changes what the connected person is notified about.

Frequently Asked Questions

What can FlowRunner do with TMetric?

FlowRunner agents can run Get Current User, Update Current User, and Get Time Balance in TMetric, plus 102 more actions.

Does connecting TMetric to FlowRunner require OAuth?

No. TMetric connects to FlowRunner with an API key, no OAuth flow required.

Can TMetric trigger a FlowRunner workflow automatically?

TMetric doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TMetric

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us