Resources · Make integration

TMetric Make integrationAutomate TMetric with Make.

Tired of retyping tasks and hours into TMetric by hand? The TMetric Make integration gives you 10 modules: 1 trigger, 7 actions and 2 searches. This guide is for ops leads and freelancers who track time in TMetric, and it walks you from the connection to a scenario that runs on its own.

Try the TMetric integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TMetric Make integration automate?

The TMetric Make integration links your TMetric account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Once linked, Make can spot new tasks, create or clean up tasks, log time entries and drive the timer, without you opening TMetric.

Tasks that show up where your team already works. Put Watch New Tasks at the start of a scenario and every task created in TMetric can be announced in your team chat or copied to your project board, so nobody has to check TMetric to know what landed.

A time report you do not rebuild by hand. List Time Entries pulls the entries out of TMetric, and Make can push each one into a spreadsheet or a base. The Airtable Make integration is a common landing spot for that kind of report.

Client requests that become tasks. When a deal moves or a form comes in, Create a Task adds the matching TMetric task, and Create a Time Entry can log the time already spent on it.

What the listed modules do not cover, you can still reach with Make an API Call, using the same connection. Keep in mind that the official Make doc for TMetric is flagged as AI-generated, so check the details that matter with TMetric itself. And if you are weighing Make against n8n for this job, the n8n vs Make comparison sets out the criteria side by side.

Connect

How do you connect TMetric to Make?

  1. 01

    Copy your TMetric API token

    In TMetric, click the profile icon in the top right corner, then Profile Settings in the menu. Click Get new API token and copy the token that appears on screen. Keep it somewhere safe until the next step.

  2. 02

    Add a TMetric module in Make

    In your Make scenario, add any TMetric module and click Create a connection. The connection is your TMetric account linked to Make once, then reused by every TMetric module. The Connection name field is optional, but a clear name helps when you run several accounts.

  3. 03

    Paste the token and save

    Paste the API token you copied from TMetric into the connection window and confirm. Make can now read your tasks and time entries, and every other TMetric module you add will offer this connection in its list.

First scenario

Your first scenario: turn incoming requests into TMetric tasks

GoalWhen a new request lands in another app you already use, Make creates the matching task in TMetric.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first module is the app where requests arrive: a form tool, your CRM or a shared inbox.

  2. 02

    Set up the source module

    Pick the module that watches new requests in that app and connect its account. Each new request becomes a bundle, one item that travels from one module to the next.

  3. 03

    Add Create a Task

    Click the + on the right of the first module, search for TMetric and choose Create a Task. Select the TMetric connection you made earlier, or create it now with your API token.

  4. 04

    Map the request to the task

    Fill the task fields by clicking the data from the first module, such as the request title or the client name. Make shows what it can read from TMetric once the connection exists.

  5. 05

    Test with Run once

    Send yourself a test request, then click Run once. Open the bundles each module received and check that the new task shows up in TMetric with the right details.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.

Triggers

What starts a TMetric scenario?

1 module starts a scenario when something happens in TMetric. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by TMetric as soon as it happens.

TMetric1Watch New Tasks

Watch New Tasks

Scheduled trigger

In Make“Triggers when a new task is created.”

Watch New Tasks hands your scenario every task created in TMetric, so whatever follows (a chat message, a row in a sheet, a card on a board) starts from fresh tasks only.

How it fires
it is a scheduled trigger, so Make checks TMetric on the scenario's schedule, every 15 minutes by default, and picks up the tasks created since the last check.
When to use it
your team creates tasks in TMetric and the rest of the company needs to hear about them without opening the app.
Watch out
tasks do not arrive the second they are created; they wait for the next scheduled check.
Modules

What can Make do in TMetric?

TMetric gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

TMetric1

Create a Task

Action

In Make“Creates a task”

Create a Task gives you a new TMetric task built from data coming out of another module, so requests stop being copied over by hand.

When to use it
a client request, a deal or a support ticket needs its own task in TMetric before anyone logs time against it.
Watch out
each bundle it receives becomes a task, so check with Run once that the same request does not end up as two tasks.
TMetric2

Create a Time Entry

Action

In Make“Creates a time entry”

Create a Time Entry writes worked time straight into TMetric, which keeps your timesheet complete even when the work was tracked somewhere else.

When to use it
a call, a meeting or a finished job is recorded in another tool and should also count as time in TMetric.
Watch out
each run adds an entry, so a test repeated with Run once leaves extra entries to clean up.
TMetric3

Delete a Task

Action

In Make“Deletes a task”

Delete a Task removes a task from TMetric, which keeps your task list in line with the tool where the work is really managed.

When to use it
a request is cancelled in your CRM or your help desk and its TMetric task no longer has a reason to exist.
Watch out
treat a deletion as final and test it on a dummy task before letting it run on real ones.
TMetric4

Edit/Delete a Time Entry

Action

In Make“Edits or deletes a time entry”

Edit/Delete a Time Entry fixes a wrong time entry for you: the same module either edits an existing entry or removes it.

When to use it
an entry was logged against the wrong task, or a duplicate slipped in, and the fix has to follow a rule instead of a manual review.
Watch out
the same module can delete, so double check which option is selected before switching the scenario on.
TMetric5

Get a Task

Action

In Make“Gets a single task”

Get a Task fetches one task you already know, so later modules can use its details without searching through the whole list.

When to use it
you stored a TMetric task reference in another tool and now need the task itself to update a report or send a message.
Watch out
it returns a single task; to go through many, use List Tasks instead.
TMetric6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Make an API Call reaches any part of the TMetric API from your scenario, with the connection you already set up, when no listed module does the job.

When to use it
you need something outside the other nine modules, for example data TMetric exposes in its API but not in Make.
Watch out
you write the request yourself, so keep the TMetric API documentation open while you build it.
TMetric7

Update a timer

Action

In Make“Updates, starts and stops a timer”

Update a timer starts, stops or changes the running TMetric timer, so time gets tracked from events rather than from someone remembering to click.

When to use it
a ticket switches to in progress, or a call begins and ends, and the timer should follow along.
Watch out
if your scenario starts the timer, plan the step that stops it too.
TMetric8

List Tasks

Search

In Make“List all tasks for an account.”

List Tasks returns the tasks of your TMetric account, each one as a separate bundle that the next modules process one by one.

When to use it
you want to copy tasks into a sheet, compare them with another tool or build a status overview for a client.
Watch out
a search can return zero, one or many tasks, and every following module then counts an operation per task.
TMetric9

List Time Entries

Search

In Make“Lists all time entries”

List Time Entries pulls your logged hours out of TMetric so a report, an invoice draft or a dashboard can be filled without exporting anything.

When to use it
a project closes and you need every entry sent to a spreadsheet or to your billing tool.
Watch out
each entry comes out as its own bundle, so place an aggregator after it if you want one total.
Need help

Need help automating TMetric with Make?

A person reads every message.

FAQ

Questions people ask about TMetric and Make

01Is the TMetric Make integration free?
Yes, as far as Make goes. TMetric is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, runs no closer than 15 minutes apart, up to 5 minutes of run time, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. You still need an active TMetric account, which is billed by TMetric.
02What do you need to connect TMetric to Make?
Two things: an active TMetric account and an API token from it. To get the token, open TMetric, click the profile icon in the top right corner, go to Profile Settings and click Get new API token, then copy it. In Make, add any TMetric module, click Create a connection, give it a name if you like and paste the token. That single connection then serves all 10 TMetric modules in every scenario you build.
03Does the TMetric trigger in Make fire in real time?
No. Watch New Tasks is a scheduled trigger, not an instant one. Make checks TMetric on the scenario's schedule, every 15 minutes by default, and collects the tasks created since the previous check. On the Free plan 15 minutes is the shortest gap; paid plans can go down to 1 minute. For most task follow-up this is enough, but if a step must happen the moment a task appears, expect that delay in your design.
04What if a TMetric module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the TMetric API through the connection you already have, so whatever falls outside the 9 listed actions and searches stays within reach. You write the request yourself, using the TMetric API documentation. Also note that Make flags its TMetric doc as AI-generated content that may contain mistakes, so confirm any detail that matters directly with TMetric before relying on it.
05Should you use Make or n8n for TMetric?
It depends on how you like to build. On Make, TMetric comes with 10 ready modules, a visual editor and a connection that takes only an API token, which suits teams that want a working scenario without code. Many apps also have an n8n node, so check whether TMetric does and which operations it covers before choosing. Compare the modules each tool offers for your exact use case, then how each one counts usage on its plans.
Same platform

Other docs you might need on this stack.

Browse all integrations