Resources · Make integration

TimeCamp Make integrationAutomate TimeCamp with Make.

Can Make keep TimeCamp in step with the rest of your stack? The TimeCamp Make integration offers 16 modules: 2 triggers, 11 actions and 3 searches. It is written for teams that track hours in TimeCamp, and it walks you from the connection to a working first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the TimeCamp Make integration let you automate?

The TimeCamp Make integration links your TimeCamp account to Make, a no-code tool where you build a scenario: the automation itself, made of modules, each one a single brick such as a trigger, an action or a search. Make can then spot new projects and tasks, create or edit them, and log time entries for you.

Every new client project starts with the right tasks. Watch Projects notices the project, and Create a Task adds the kickoff task under it, so nobody has to rebuild the same structure by hand for each account an agency signs.

Hours land in TimeCamp without retyping. When a job is closed in another tool, Create a Time Entry writes the matching record, and Update a Time Entry corrects it if the job changes later.

Reports pull fresh data. List Projects, List Tasks and List Time Entries hand the current records to a spreadsheet or a dashboard, one bundle per item.

Both TimeCamp triggers are scheduled: Make checks for new items on the scenario's schedule, it is not alerted at the moment they appear. The doc gives no numbered limit for the app. If a module is missing, Make an API Call reaches any endpoint of the TimeCamp API with the same connection. To see how Make fits your wider tooling, the Make review covers the editor, and Make pricing explains what counts on a plan. Many apps also have an n8n node; n8n vs Make sets the two side by side.

Connect

How do you connect TimeCamp to Make?

  1. 01

    Copy your TimeCamp API token

    In TimeCamp, click your avatar in the top-right corner, open Profile Settings and copy the API token shown at the bottom of the page. You need an active TimeCamp account for this token to exist.

  2. 02

    Add a TimeCamp module in Make

    Open your scenario, add any TimeCamp module and click Create a connection. The Connection name field is optional; a clear name helps when several people share the same Make team.

  3. 03

    Paste the token and save

    Paste the token you copied, or follow the on-screen instructions, then confirm. The connection is now stored once and reused by every TimeCamp module you add to any scenario.

First scenario

Build your first TimeCamp scenario

GoalWhen a new project appears in TimeCamp, Make adds a kickoff task to it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to place your first module.

  2. 02

    Pick Watch Projects

    Search for TimeCamp, choose Watch Projects and click Create a connection to link the account with your API token. This trigger will start the scenario.

  3. 03

    Add Create a Task

    Click the + to the right of the trigger, pick Create a Task, then map the project from the trigger's output so the new task lands in the right place.

  4. 04

    Test with Run once

    Create a test project in TimeCamp, then click Run once. Open the bubble above each module to read the bundles it received and check the task in TimeCamp.

  5. 05

    Schedule and switch on

    Click the clock on Watch Projects to set the schedule (every 15 minutes by default, never below that on the Free plan) and turn the scenario on.

Triggers

What can start a TimeCamp scenario?

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

TimeCamp1Watch Projects

Watch Projects

Scheduled trigger

In MakeTriggers when a new project is created.

Watch Projects hands each newly created TimeCamp project to your scenario, so everything that should follow a new project can happen without a reminder. Every project arrives as its own bundle, the unit that flows from one module to the next.

How it fires
scheduled. Make checks TimeCamp on the scenario's schedule, which is every 15 minutes by default for a new scenario.
When to use it
when a new client or internal project should trigger setup work, such as a starter task, a channel message or a row in a tracking sheet.
Watch out
it only reacts to new projects, so an edit to an existing one will not start the scenario.
TimeCamp2Watch Tasks

Watch Tasks

Scheduled trigger

In MakeTriggers when a new task is created.

Every task freshly added in TimeCamp reaches your scenario through Watch Tasks, which is handy when work planned in TimeCamp must show up somewhere else. Each task travels as one bundle, and each module that processes it uses one operation, the unit Make counts on your plan.

How it fires
scheduled. Make queries TimeCamp at the interval set on the scenario, 15 minutes at minimum on the Free plan and down to 1 minute on paid plans.
When to use it
when a new task should reach a to-do app, notify its owner or be copied to a client-facing board.
Watch out
a batch of tasks created at once arrives as several bundles in one run, and every later module runs once per task.
Modules

What can Make do in TimeCamp?

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

TimeCamp1

Create a Project

Action

In MakeCreates a new project.

With Create a Project, a signed deal or a new client record becomes a TimeCamp project that is ready for time tracking, without anyone opening TimeCamp to set it up.

When to use it
right after a deal is marked won in your CRM, so the team can start logging hours on day one.
Watch out
run a List Projects search first if the same client might already have a project, or you will end up with duplicates.
TimeCamp2

Create a Task

Action

In MakeCreates a new task.

Adding work items to TimeCamp from another tool is the job of Create a Task, which gives your team something concrete to track time against as soon as the request exists.

When to use it
when a support ticket, a form request or a new project from Watch Projects needs a matching task.
Watch out
map the target project from an earlier module rather than typing it, so each task lands under the right project.
TimeCamp3

Create a Time Entry

Action

In MakeCreates a new time entry.

Hours recorded elsewhere reach your timesheets through Create a Time Entry, which writes a new entry in TimeCamp so billing and reports stay complete.

When to use it
when a job is closed in a field service app or a meeting ends in your calendar and that time should count in TimeCamp.
Watch out
test with Run once on a single record before switching on, since every source item will produce its own entry.
TimeCamp4

Delete a Project

Action

In MakeDeletes an existing project.

Delete a Project removes a TimeCamp project straight from your scenario, which keeps your project list tidy when work is cancelled upstream.

When to use it
when a deal is lost or a project request is withdrawn before any hours were logged against it.
Watch out
treat the deletion as final and place a filter before this module so only the projects you really mean to remove ever reach it.
TimeCamp5

Delete a Task

Action

In MakeDeletes an existing task.

Stale tasks vanish from TimeCamp with Delete a Task, so people stop tracking time against work that no longer exists and your reports stay readable.

When to use it
when the matching item is closed as not needed in your issue tracker or project tool.
Watch out
a task pulled from a search can be one of many bundles, so check with Run once that only the intended task is removed.
TimeCamp6

Get a Project

Action

In MakeGets a project's info.

You get the full details of one TimeCamp project from Get a Project, which is useful when a later module needs more than the project reference you already have.

When to use it
in the middle of a scenario, when an email, an invoice line or a report must show the project's information.
Watch out
it reads a single known project; to browse or find several, reach for List Projects instead.
TimeCamp7

Get a Task

Action

In MakeGets task's info.

Get a Task returns the information stored on one specific task, giving the next modules clean data to work with instead of a bare reference.

When to use it
after Watch Tasks or a time entry, when you want the task's own details before sending a notification or updating another app.
Watch out
it needs the task identified up front, usually mapped from a trigger or a List Tasks search earlier in the flow.
TimeCamp8

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call is the escape hatch: it reaches any endpoint of the TimeCamp API with the connection you already set up, so you can cover what the other modules leave out.

When to use it
when the operation you need has no dedicated module in the list above.
Watch out
you describe the request yourself, so keep the TimeCamp API documentation open and test with Run once before relying on it.
TimeCamp9

Update a Project

Action

In MakeUpdates an existing project.

Changes made in your CRM or planning tool can flow into TimeCamp through Update a Project, which edits an existing project so both systems tell the same story.

When to use it
when a client is renamed or a project's details change in the tool where your team actually manages the account.
Watch out
the project must already exist, so map it from Watch Projects, Get a Project or List Projects rather than guessing.
TimeCamp10

Update a Task

Action

In MakeUpdates an existing task.

Keeping a TimeCamp task aligned with its twin in another app is what Update a Task does, editing the existing task instead of creating a second one.

When to use it
when a ticket or card is edited in your issue tracker and the linked task should reflect the change.
Watch out
store the TimeCamp task reference somewhere in the other app, otherwise the scenario cannot tell which task to update.
TimeCamp11

Update a Time Entry

Action

In MakeUpdates an existing time entry.

Corrections reach your timesheets through Update a Time Entry, which edits an entry already in TimeCamp so a fix made at the source does not leave a wrong line behind.

When to use it
when a job's hours are adjusted after the fact in the app that first created the entry.
Watch out
pair it with List Time Entries to find the right entry, and keep track of which source record it came from.
TimeCamp12

List Projects

Search

In MakeList all projects.

For a full picture of your workspace, List Projects returns every TimeCamp project, each one as a separate bundle the next modules can use.

When to use it
to fill a reporting sheet, to check whether a project exists before creating it, or to loop over projects for a bulk update.
Watch out
a search can return zero, one or many bundles, and each module after it runs once per project, which adds operations.
TimeCamp13

List Tasks

Search

In MakeList all tasks.

List Tasks brings back all TimeCamp tasks so you can review, copy or match them against items in another tool.

When to use it
when you sync TimeCamp with a project board and need to know which tasks already exist before creating new ones.
Watch out
the search can come back empty, so run it once with Run once and check how the next modules behave when no task is returned.
TimeCamp14

List Time Entries

Search

In MakeGets time entry info.

Tracked hours become usable data outside TimeCamp with List Time Entries, which retrieves time entry information for invoices, payroll sheets or dashboards.

When to use it
when you prepare a client invoice or a utilization report from the hours logged in TimeCamp.
Watch out
it is a search, so it can hand over many bundles; add an aggregator if you need one total rather than one line per entry.
Need help

Need help automating TimeCamp with Make?

A person reads every message.

FAQ

TimeCamp and Make: frequently asked questions

01Is the TimeCamp Make integration free?
Yes, on the Make side. TimeCamp is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Each module run on a bundle is one operation, and operations are what Make counts against your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active TimeCamp account, whose subscription is described on the TimeCamp pricing page.
02What do you need to connect TimeCamp to Make?
Two things: an active TimeCamp account and its API token. In TimeCamp, click your avatar in the top-right corner, go to Profile Settings and copy the token shown at the bottom of the page. In Make, add a TimeCamp module, click Create a connection, give it a name if you like, and paste the token. That connection is saved once and every TimeCamp module in every scenario can reuse it, so you will not repeat this step for each new automation.
03Do TimeCamp triggers in Make fire in real time?
No. Both TimeCamp triggers, Watch Projects and Watch Tasks, are scheduled, which means Make checks TimeCamp on the scenario's schedule rather than being alerted the moment something changes. A new scenario runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. New projects or tasks created between two checks are picked up together at the next run, each as its own bundle.
04What if a TimeCamp module is missing in Make?
Use Make an API Call. It is part of the TimeCamp app in Make and can reach any endpoint of the TimeCamp API with the connection you already created, so nothing new has to be authorized. You write the request yourself, which asks for a look at the TimeCamp API documentation, and then test it with Run once. The Make doc for TimeCamp lists no numbered limit for the app, so the practical constraints are the ones of your Make plan.
05Should you use Make or n8n for TimeCamp?
It depends on which tool your team already works in. In Make, TimeCamp comes with 16 ready modules covering projects, tasks and time entries, plus Make an API Call for anything else, and it is available from the Free plan. Many apps also have an n8n node, so check whether one exists for TimeCamp and whether it covers the same operations you need. Compare the two on the actions you actually plan to automate rather than on the brand.