Resources · Make integration

Time Doctor Make integrationAutomate Time Doctor with Make.

Can Make keep your Time Doctor projects, tasks and hours in order for you? The Time Doctor Make integration gives you 15 modules: 1 trigger, 11 actions and 3 searches. This guide is for ops leads and team managers, and it walks you from the connection to a working scenario.

Try the Time Doctor integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Time Doctor Make integration do for you?

The Time Doctor Make integration links your Time Doctor account to Make, a visual tool where you build a scenario: the automation itself, made of modules placed one after the other. Each module is one brick, such as a trigger that watches Time Doctor or an action that creates a task. You set it up once, and Make runs it for you.

Every new hire gets a first task. Watch Users spots a user added to your Time Doctor company, then Create a Task opens an onboarding task so the newcomer has something to log hours against on day one.

Projects mirror the tools where work is sold. When a deal is won in your CRM, Create a Project opens the matching Time Doctor project, and Update a Project renames it when the scope changes. The Agile CRM Make integration shows the CRM side of that flow.

Tracked hours land in a report. List Time Entries pulls the logged time, and a spreadsheet or database module stores it, for example through the Airtable Make integration.

What Make does not do here: the documentation gives no connection prerequisites and no numeric limits, and only one trigger exists, on new users. For anything the 15 modules miss, Make an API Call reaches the rest of the Time Doctor API. If you also weigh n8n for this kind of work, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Time Doctor to Make?

  1. 01

    Add a Time Doctor module

    Open a scenario, click the +, search for Time Doctor and pick any of its modules. In the module panel, click Create a connection. A connection is your Time Doctor account linked to Make once, then reused by every Time Doctor module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the company it belongs to. Then follow the Time Doctor window that opens to authorize Make, or paste the key Time Doctor gives you if that is what the screen asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, Make can now read your account and offer the projects and tasks it finds, so you pick them from a list instead of typing IDs by hand.

First scenario

Your first scenario: a task for every new Time Doctor user

GoalWhen a user is added in Time Doctor, Make creates an onboarding task for them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module. This first module decides when everything else runs.

  2. 02

    Add Watch Users

    Search for Time Doctor, choose Watch Users and select your connection, or click Create a connection if you have not linked the account yet.

  3. 03

    Add Create a Task

    Click the + on the right of Watch Users and pick Create a Task. Fill its fields by mapping the user data that Watch Users hands over, so each task clearly belongs to one newcomer.

  4. 04

    Test with Run once

    Add a test user in Time Doctor, then click Run once. Open the bubble above each module to read the bundles it received: one bundle is one item passed along, here one user.

  5. 05

    Schedule and switch it on

    Click the clock on Watch Users to set the schedule, every 15 minutes by default, then switch the scenario on. Make now checks Time Doctor for new users at that pace.

Triggers

What starts a Time Doctor scenario

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

Time Doctor1Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is added.”

Watch Users hands your scenario every person newly added to your Time Doctor company, one bundle per user, so the setup that follows a hire can start without anyone remembering to do it.

How it fires
it is a scheduled trigger, marked with a clock badge. Make checks the app on the scenario's schedule, every 15 minutes by default, and at most every 15 minutes on the Free plan.
When to use it
when a new team member should get an onboarding task, a project or a welcome message elsewhere as soon as their account exists.
Watch out
it only reacts to new users; changes to existing users do not start it.
Modules

Every Time Doctor module in Make

Time Doctor gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Time Doctor1

Create a Project

Action

In Make“Creates a new project.”

Create a Project opens a fresh project in Time Doctor from data arriving in the scenario, so people can start tracking hours on it right away.

When to use it
when a signed deal or a new client in another app should give your team a place to log its time.
Watch out
each run makes a new project, so a scenario that fires twice on the same deal gives you two of them.
Time Doctor2

Create a Task

Action

In Make“Creates a new task.”

Create a Task puts the work in Time Doctor for you, so nobody retypes it and the team can start logging time on it.

When to use it
when a ticket, a form or a new hire should turn into a trackable piece of work.
Watch out
each run adds one task, so a trigger that fires twice on the same event leaves you with a duplicate to clean up.
Time Doctor3

Create a Time Entry

Action

In Make“Creates a new time entry.”

This module writes hours into Time Doctor for you: a block of worked time added from another source instead of a timer someone started.

When to use it
when time logged in a calendar, a helpdesk or a spreadsheet should also count in Time Doctor.
Watch out
test with Run once on a single bundle before switching on, since duplicated entries inflate the hours your reports show.
Time Doctor4

Delete a Project

Action

In Make“Deletes a project by ID.”

Delete a Project removes a Time Doctor project once you give it the project ID, which keeps the list your team picks from short and current.

When to use it
when a contract is cancelled in another tool and its project should disappear too.
Watch out
treat every deletion as final. Place a filter before the module so only the projects you really mean to remove get through.
Time Doctor5

Delete a Task

Action

In Make“Deletes a task by ID.”

Tasks that no longer make sense leave Time Doctor through this module, which works from the task ID and clears them without a manual pass.

When to use it
when a ticket closed as a duplicate elsewhere should not stay open for time tracking.
Watch out
the ID usually comes from List Tasks or Get a Task earlier in the scenario, so check it maps the right task before the first real run.
Time Doctor6

Delete a Time Entry

Action

In Make“Deletes an existing time entry.”

Delete a Time Entry takes an existing block of logged time out of Time Doctor, which helps when hours were recorded twice or by mistake.

When to use it
as the clean-up step of a scenario that first spots bad entries with List Time Entries.
Watch out
removed hours vanish from Time Doctor's totals, so run the scenario once in test and read each bundle before letting it act.
Time Doctor7

Get a Project

Action

In Make“Gets a single project by ID.”

Get a Project returns the details of one Time Doctor project from its ID, handing the rest of the scenario the facts it needs without a broad search.

When to use it
when you already hold the ID, say from a previous module, and want the project's current state before updating or reporting on it.
Watch out
without an ID, reach for List Projects instead.
Time Doctor8

Get a Task

Action

In Make“Gets a single task by ID.”

You get one task back, fully described, as soon as you pass its ID to this module, so later steps can read it before acting.

When to use it
to confirm a task still exists and see its details before Update a Task or Delete a Task touches it.
Watch out
it reads one task only; to go through several, List Tasks is the module that returns them all.
Time Doctor9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any part of the Time Doctor API the other modules leave out, using the connection you already created.

When to use it
when you need something the 15 modules do not offer, and the Time Doctor API has a request that does it.
Watch out
you write the request yourself, so keep the Time Doctor API reference open while you build it.
Time Doctor10

Update a Project

Action

In Make“Updates a project by ID.”

Update a Project changes an existing Time Doctor project, found by its ID, so it keeps matching what the rest of your stack says about that client.

When to use it
when a deal is renamed or its scope shifts in your CRM and the project name should follow.
Watch out
the ID must come from somewhere earlier in the flow, often Get a Project or List Projects.
Time Doctor11

Update a Task

Action

In Make“Updates a task by ID.”

Edits made elsewhere reach Time Doctor through Update a Task, which rewrites an existing task identified by its ID instead of creating a second one.

When to use it
when the ticket behind a task changes in your helpdesk and the task people track against should reflect it.
Watch out
map the ID from Get a Task or List Tasks, and test with Run once to see exactly which task changed.
Time Doctor12

List Projects

Search

In Make“Lists all projects by company ID.”

List Projects returns the projects of a Time Doctor company, found by its company ID, one bundle each, so the next modules can work through all of them.

When to use it
to keep a project inventory in a spreadsheet. Need the ID for an update or a deletion? Start here.
Watch out
every project becomes a bundle, and each following module then uses one operation per bundle, which adds up on your plan.
Time Doctor13

List Tasks

Search

In Make“Lists all tasks.”

This search brings back all the tasks in Time Doctor, zero, one or many, so you can review or sync them in one pass.

When to use it
to copy the task list into a board your managers already read, or to spot tasks that need an update.
Watch out
an empty result simply stops the modules after it, so a run with nothing to show is not an error.
Time Doctor14

List Time Entries

Search

In Make“Retrieves all existing time entries.”

List Time Entries retrieves the hours logged in Time Doctor, one bundle per entry, which is the raw material of any timesheet or billing report.

When to use it
when tracked time should feed a spreadsheet, an invoice draft or a dashboard outside Time Doctor.
Watch out
add an aggregator after it when you want totals, otherwise every following module runs once per entry.
Need help

Need help automating Time Doctor with Make?

A person reads every message.

FAQ

Time Doctor and Make: common questions

01Is the Time Doctor Make integration free?
Yes, Time Doctor is a standard app in Make, so it works on the Free plan. That plan allows 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 cap on active scenarios and allow runs of up to 40 minutes. Make counts usage in operations, one per module per bundle, so a busy scenario uses more of your plan.
02What does the Time Doctor Make integration need to connect?
A Time Doctor account and a Make account are the starting point; the Make documentation for Time Doctor lists no other prerequisite. You add any Time Doctor module, click Create a connection, optionally name it, authorize Make in the window Time Doctor opens or paste the key it gives you, then click Save. That connection is created once and reused by all 15 Time Doctor modules, so later scenarios skip this step entirely.
03Does the Time Doctor trigger in Make fire instantly?
No. Watch Users is a scheduled trigger: Make checks Time Doctor for new users on the scenario's schedule rather than being called by Time Doctor the moment someone is added. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. So a new user reaches your scenario at the next check, not the second the account is created. It is the only trigger in the app, and it covers new users only.
04What if a Time Doctor module is missing in Make?
Use Make an API Call. It sends any request the Time Doctor API accepts, with the same connection as the other modules, so you are not limited to the 11 actions and 3 searches listed. It is the natural route when the listed modules stop short of what your process needs. The Make documentation gives no numeric limits for Time Doctor, so there is no documented quota to plan around, but you do need to write the request yourself from the Time Doctor API reference.
05Make or n8n for Time Doctor automation?
It depends on the tool your team already builds in. Make offers 15 Time Doctor modules, including Make an API Call, and a visual editor where you test each step with Run once. The same app often has an n8n node as well, so check that side before deciding. Pick the platform that already runs your other automations, since keeping them in one place is easier to maintain. The n8n vs Make comparison on this site sets out the criteria side by side, without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations