Resources · Make integration

TrackingTime Make integrationAutomate TrackingTime with Make.

What if new clients, projects and logged hours in TrackingTime moved on their own? The TrackingTime Make integration gives you 17 modules: 5 triggers, 9 actions and 3 searches. This guide shows how to link your account and build a first working scenario without writing code.

Try the TrackingTime integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TrackingTime Make integration do for you?

The TrackingTime Make integration links your TrackingTime account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, finds or updates something. TrackingTime brings 17 of those bricks, so tasks, projects, customers and time entries can react to what happens elsewhere.

Projects that open themselves. When Watch customers spots a new client in TrackingTime, Add a project creates the matching project right away, so nobody has to remember that setup step.

Tasks born from your other tools. A signed deal or a support ticket in another app can become a TrackingTime task through Add a task, with the right project found first by Search a project.

Hours that travel to your other tools. Watch time entries and Watch completed tasks pass each new entry or finished task to the next module, for a report, a sheet or a message to the client lead.

Keep the limits in mind: the listed modules cover customers, projects, services, tasks and time entries. For anything else, Make an API call reuses the same connection. n8n often has a node for the same app too; the n8n vs Make comparison helps you choose, and the Make review and Make training pages go further on the tool itself.

Connect

How do you connect TrackingTime to Make?

  1. 01

    Generate an app password in TrackingTime

    In your TrackingTime account settings, open Apps and Integrations, find App Passwords and generate a new one. Copy it as soon as it shows on screen, since this is the credential Make will ask for.

  2. 02

    Add a TrackingTime module in Make

    In your scenario, click the + and search for TrackingTime. Pick any module, then click Create a connection. A connection is your TrackingTime account linked to Make once and reused by every TrackingTime module.

  3. 03

    Name the connection and paste your credentials

    The Connection name field is optional, but a clear name helps when several people share the workspace. Paste the credentials you copied from TrackingTime, or follow the on-screen instructions, and save.

First scenario

Your first scenario: a project for every new customer

GoalWhen a new customer appears in TrackingTime, Make creates a project for that customer.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the editor to add the first module.

  2. 02

    Add Watch customers

    Search for TrackingTime, pick Watch customers and click Create a connection (or pick the one you already made). This module is the trigger: it starts the scenario whenever it finds a new customer.

  3. 03

    Add Add a project

    Click the + on the right of the trigger and pick Add a project. Map the customer coming from the previous module into the project, so each project lands under the right client.

  4. 04

    Test with Run once

    Create a test customer in TrackingTime, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the new project before going live.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default, which is also the shortest gap on the Free plan), then switch the scenario on.

Triggers

What can start a TrackingTime scenario?

5 modules start a scenario when something happens in TrackingTime. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by TrackingTime as soon as it happens.

TrackingTime1Watch completed tasks

Watch completed tasks

triggerIn the docs only

Gives your scenario a signal each time a task gets marked as done in TrackingTime, so the finish line of a piece of work can set off whatever comes next: a note to the client, a status change elsewhere, a line in a delivery log.

How it fires
scheduled. Make checks TrackingTime on the scenario's schedule and picks up the tasks completed since the last check.
When to use it
when closing a task should tell someone outside TrackingTime that the work is ready for review.
Watch out
like the other triggers, its type is deduced from its name in the doc, so run it once on a test task before relying on it.
TrackingTime2Watch customers

Watch customers

triggerIn the docs only

Hands you each new customer record from TrackingTime as a bundle, meaning one item passed to the next module, which makes client onboarding the easiest place to start automating.

How it fires
scheduled. On each run of the schedule, Make asks TrackingTime for customers it has not seen yet.
When to use it
when a new client should get a project, a folder or a CRM record without anyone copying the name across.
Watch out
customers created between two checks arrive together on the next run, and each one becomes its own bundle with its own operations counted on your plan.
TrackingTime3Watch projects

Watch projects

triggerIn the docs only

Lets the rest of your tools learn about a project the moment Make picks it up from TrackingTime, so a kickoff checklist or a shared channel can follow without a manual step.

How it fires
scheduled. Make polls TrackingTime on the scenario's schedule for projects that are new since the previous run.
When to use it
when your team opens projects directly in TrackingTime and other apps need to mirror them.
Watch out
if the same scenario also creates projects with Add a project, it will see its own creations on the next run, so keep those two in separate scenarios.
TrackingTime4Watch tasks

Watch tasks

triggerIn the docs only

Sends every newly created TrackingTime task into your scenario, which is how you keep a to-do list, a calendar or a teammate informed as soon as work gets planned.

How it fires
scheduled. Make checks TrackingTime at the interval set on the first module and collects the new tasks.
When to use it
when a task assigned in TrackingTime should also show up where the assignee actually works.
Watch out
this module reacts to new tasks, not finished ones; for the end of a task, pick Watch completed tasks instead.
TrackingTime5Watch time entries

Watch time entries

triggerIn the docs only

Turns each hour block someone records in TrackingTime into data you can reuse, the natural source for billing sheets, client reports or a budget alert on a project.

How it fires
scheduled. Make queries TrackingTime on the scenario's schedule and returns the time entries added since the last run.
When to use it
when finance or a project lead needs logged hours in a spreadsheet without exporting them by hand.
Watch out
a busy team logs many entries, and each one costs operations downstream, so filter early if you only need some projects.
Modules

What can Make do in TrackingTime?

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

TrackingTime1

Add a customer

ActionIn the docs only

Creates a client in TrackingTime from data that lives elsewhere, so a deal won in your CRM or a signed form turns into a customer ready to hold projects.

When to use it
at the start of a flow that then builds the project and first tasks for that client.
Watch out
there is no search module for customers, so check your source first, since adding the same client twice leaves you with duplicates to merge by hand.
TrackingTime2

Add a project

ActionIn the docs only

Opens a new project in TrackingTime without anyone filling a form, which keeps project names and client links consistent from one job to the next.

When to use it
right after a new customer shows up, or when a quote gets accepted in another tool.
Watch out
map the customer from the earlier module, otherwise the project lands without a client and your reports split.
TrackingTime3

Add a service

ActionIn the docs only

Adds a service to your TrackingTime account, the kind of work your team logs time against, so a new offer is available to everyone as soon as it exists in your catalog.

When to use it
when your list of offers is kept in a sheet or a database and TrackingTime should follow it.
Watch out
no module searches services, so check your list before adding one, or the same service ends up twice.
TrackingTime4

Add a task

ActionIn the docs only

Puts a task on a TrackingTime project from an event in any other app, a support ticket or a form reply for example, so people can start logging hours on it straight away.

When to use it
when requests arrive outside TrackingTime and someone currently retypes them.
Watch out
the task needs the right project; place Search a project before it to find the project first.
TrackingTime5

Add a time entry

ActionIn the docs only

Records hours in TrackingTime on behalf of your scenario, useful when time is already captured in a calendar, a call tool or a spreadsheet and should not be typed a second time.

When to use it
when a meeting or a call logged somewhere else should count on a task or project.
Watch out
test with Run once on a single item first, because a wrong mapping can fill timesheets with entries you then have to delete.
TrackingTime6

Make an API call

ActionIn the docs only

Reaches any endpoint of the TrackingTime API with the connection you already set up, which covers the cases the other modules leave out.

When to use it
when you need an object or an operation that no listed module offers, such as something beyond customers, projects, services, tasks and time entries.
Watch out
you shape the request yourself, so keep the TrackingTime API documentation open while you build it.
TrackingTime7

Search a project

SearchIn the docs only

Finds existing TrackingTime projects so later modules can work on the right one, instead of creating a new project each time the scenario runs.

When to use it
before Add a task or Update a project, when your input only carries a name.
Watch out
a search can return zero, one or several projects as separate bundles; plan for the empty case and for more than one match.
TrackingTime8

Search a task

SearchIn the docs only

Looks up tasks already in TrackingTime, so your scenario can check whether the work exists before adding it or pick the task it has to change.

When to use it
as the step that prevents duplicate tasks when the same request can arrive twice from another tool.
Watch out
several matching tasks come back as several bundles, and every module after the search then runs once per task.
TrackingTime9

Search a time entry

SearchIn the docs only

Pulls matching time entries out of TrackingTime on demand, which suits a report built when you ask for it rather than one fed by every new entry.

When to use it
when a project closes and you want its logged hours gathered for an invoice or a recap.
Watch out
a large result means many bundles and many operations; narrow the search before sending the results onward.
TrackingTime10

Update a project

ActionIn the docs only

Changes a project that already exists in TrackingTime, so its details stay in line with what your CRM or project board says without a manual edit.

When to use it
when a deal or a job changes status elsewhere and the project should reflect it.
Watch out
it needs the exact project, so pair it with Search a project or a trigger that passes the project along.
TrackingTime11

Update a task

ActionIn the docs only

Edits a TrackingTime task from your scenario, handy for keeping it aligned with the ticket or card it came from as that item evolves.

When to use it
when the source request gets reassigned or renamed and the task should follow.
Watch out
it needs the exact task, so find it first with Search a task or take it from a trigger that passes it along.
TrackingTime12

Update a time entry

ActionIn the docs only

Corrects a time entry already saved in TrackingTime, so a fix made in the source, a moved meeting for instance, carries over to the timesheet.

When to use it
when entries come from Add a time entry and their origin can still change afterwards.
Watch out
find the entry first with Search a time entry, since updating the wrong one silently changes someone's hours.
Need help

Need help automating TrackingTime with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the TrackingTime Make integration free?
Yes, TrackingTime is a standard app in Make, so it works from the Free plan. That plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the limit on active scenarios and count usage in credits, meaning operations, each month. You still need your own TrackingTime subscription, whose price this page does not cover.
02What do you need to connect TrackingTime to Make?
You need a TrackingTime account and an app password. In TrackingTime, go to Apps and Integrations in your account settings, open App Passwords, generate a new one and copy it. In Make, add any TrackingTime module, click Create a connection, give it a name if you like, and paste the credentials. The connection is then shared by every TrackingTime module in your scenarios, so you only do this once per account.
03Does the TrackingTime Make integration react in real time?
No. Judging by their names (the doc does not state their type), all 5 TrackingTime triggers are scheduled: Make checks TrackingTime on the scenario's schedule instead of being called the moment something changes. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans allow 1 minute. Whatever happened between two checks, such as several new time entries, comes through together on the next run as separate bundles, each one processed by the modules that follow.
04What if a TrackingTime module is missing in Make?
Use Make an API call. It sends a request to any endpoint of the TrackingTime API with the connection you already have, so you are not limited to the listed modules and their scope of customers, projects, services, tasks and time entries. You write the request yourself, with the TrackingTime API documentation at hand. Also note that the Make doc for this app is flagged as AI-generated from the vendor documentation, so verify important details with TrackingTime.
05Should you use Make or n8n for TrackingTime?
It depends on the tool your team already runs. n8n often offers a node for the same app, so check it there before deciding. On the Make side, you get 17 ready modules covering customers, projects, services, tasks and time entries, 5 scheduled triggers and an API call module for the rest, all usable from the Free plan. If your other automations already live in one of the two, keeping TrackingTime there avoids splitting your workflows across tools.
Same platform

Other docs you might need on this stack.

Browse all integrations