Resources · Make integration

Timing Make integrationAutomate Timing with Make.

Your time tracking can fill itself in when work happens elsewhere. The Timing Make integration gives you 13 modules: 11 actions and 2 searches on projects, time entries and timers. This guide connects your account and walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Timing Make integration do?

The Timing Make integration links your Timing account to Make so other tools can create, read, change and delete your projects and time entries, or start and stop a timer. You build a scenario, the automation Make runs for you, out of modules, each one a single step such as Create a Project.

A project ready as soon as a deal closes. When your CRM marks a deal as won, Create a Project opens the matching project in Timing, so nobody has to type the client name twice.

A timer that follows your calendar or your task board. A card moved to “In progress” in another app can call Start a Timer, and moving it to “Done” calls Stop a Timer. The hours land where they belong without a click in Timing.

Tracked hours sent to the rest of your stack. Search Time Entries pulls the entries you need and hands them to a spreadsheet, an invoicing tool or a report, one item at a time.

Know the gaps before you start. Timing has no trigger in Make, so Make cannot watch Timing and react when you log time there; the scenario has to start from another app or from a schedule. Make also notes that its Timing documentation is AI-generated and may contain mistakes, so check anything important against Timing itself. If you also look at n8n, the n8n vs Make comparison lays out the differences, and the Make training covers scenario building from scratch. For help with a larger setup, see the Make agency.

Connect

How do you connect Timing to Make?

  1. 01

    Generate an API key in Timing

    You need an active Timing account. In the Timing web application, open the API Keys section, click the button that generates a new key, then copy the key shown on screen. Keep it in your clipboard for the next step.

  2. 02

    Add a Timing module and open the connection

    In your Make scenario, add any Timing module, for example Create a Project, and click Create a connection. A connection is your Timing account linked to Make once, then reused by every Timing module.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several accounts coexist. Paste the API key you copied, or follow the instructions on screen, and save. Make can now read your Timing projects.

First scenario

Build your first scenario with Timing

GoalWhen a new client appears in another app, Make creates the matching project in Timing.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your new clients show up, such as your CRM or a form tool.

  2. 02

    Add Create a Project

    Click the + on the right of that first module, search for Timing and pick Create a Project. Choose the connection you made with your API key, or click Create a connection now.

  3. 03

    Map the client data

    Fill the module fields by mapping data from the first module, the client or company name for instance. Each item that flows between modules is a bundle: here, one bundle equals one new client.

  4. 04

    Test with Run once

    Click Run once, then create a test client in the source app. Read the bundles each module received, and check that the project appears in Timing.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default), then switch the scenario on. Each module run counts as an operation, the unit Make bills on your plan.

Modules

What can Make do in Timing?

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

Timing1

Create a Project

ActionIn the docs only

Gives every new client or job its own project in Timing, created from data that already lives in another tool. Your time tracking stays aligned with the work you actually signed.

When to use it
right after a signed quote or a won deal, so the team can log hours against the project on day one.
Watch out
run Search Projects first if the source app can send the same client twice, or you end up with duplicate projects.
Timing2

Create a Time Entry

ActionIn the docs only

Writes a finished block of work straight into Timing, without running a live timer. Useful when the time was already measured somewhere else and only needs to be recorded.

When to use it
a meeting ends in your calendar tool, or a support ticket closes, and you want that slot logged against the right project.
Watch out
map the project carefully, since an entry filed under the wrong one skews every report built on it.
Timing3

Delete a Project

ActionIn the docs only

Removes a project from Timing when it no longer has a reason to exist, keeping the project list clean for everyone who picks a project to log time.

When to use it
a deal is cancelled before any work starts and the project was created automatically.
Watch out
treat the deletion as permanent and add a filter before this module, so only projects you really meant to drop reach it.
Timing4

Delete a Time Entry

ActionIn the docs only

Erases one time entry, the fix for a slot that should never have been logged. It acts on a single entry at a time.

When to use it
an event gets cancelled in the source app after your scenario had already turned it into an entry in Timing.
Watch out
you need the exact entry to target, usually found with Search Time Entries first, and a wrong match removes real hours.
Timing5

Get a Project

ActionIn the docs only

Fetches one Timing project you already know, so later modules can reuse its details. Think of it as reading a single card, not browsing a list.

When to use it
you stored the project reference earlier in the scenario, or in another tool, and need its current details before an update or a report.
Watch out
it returns one project only; to find projects by name, reach for Search Projects instead.
Timing6

Get a Time Entry

ActionIn the docs only

Reads back one specific time entry from Timing, handy to confirm what was logged before another tool relies on it.

When to use it
your scenario created an entry earlier and a later step, such as a client notification, needs its final content.
Watch out
without a known entry to point at, this module has nothing to read; Search Time Entries is the way to locate entries first.
Timing7

Make an API Call

ActionIn the docs only

Opens the rest of the Timing API to your scenario, using the same connection as the other modules. Any endpoint the 12 ready-made modules leave out becomes reachable.

When to use it
you need something the listed modules do not offer and Timing documents it in its API.
Watch out
you write the request yourself, so keep the Timing API reference open while you build it.
Timing8

Search Projects

SearchIn the docs only

Looks through your Timing projects and returns every match, which lets a scenario check whether a project already exists before creating another one.

When to use it
a new deal arrives and you want to reuse the client project if it is already in Timing.
Watch out
the result can hold zero, one or many bundles, and each bundle runs the next modules once, so add a filter when only one match matters.
Timing9

Search Time Entries

SearchIn the docs only

Pulls a set of logged entries out of Timing so you can total them, copy them to a sheet or feed an invoice. This is how your hours leave Timing.

When to use it
a project closes and you want its entries sent to your billing tool.
Watch out
every entry found becomes its own bundle and uses operations downstream; group them with an aggregator if you want one line per project.
Timing10

Start a Timer

ActionIn the docs only

Starts a running timer in Timing from an event in another app, so the clock is already going when the work begins.

When to use it
a task moves to “In progress” on your board, or a call begins in your phone tool, and you would otherwise forget to press start.
Watch out
pair it with Stop a Timer in a second scenario, or the timer keeps counting long after the work ended.
Timing11

Stop a Timer

ActionIn the docs only

Ends the timer that is currently running in Timing, so nobody has to open the app to press stop.

When to use it
the task that started the clock is marked done, or the call hangs up, in the tool that drives your day.
Watch out
test with Run once while a timer really runs, otherwise the module has nothing to stop and the result tells you little.
Timing12

Update a Project

ActionIn the docs only

Changes an existing Timing project so it keeps matching the source of truth, for example a renamed client or a project that moves to a new stage.

When to use it
the account name changes in your CRM and the Timing project should follow without a manual edit.
Watch out
find the right project first with Search Projects or Get a Project; updating the wrong one silently rewrites someone else's work.
Timing13

Update a Time Entry

ActionIn the docs only

Corrects an entry that is already in Timing instead of deleting it and creating a new one, so reports built on it stay consistent.

When to use it
a meeting in your calendar gets moved or renamed after your scenario logged it, and the entry has to match.
Watch out
map only the values that changed and test with Run once on a sample entry.
Need help

Need help automating Timing with Make?

A person reads every message.

FAQ

Timing and Make: common questions

01Is the Timing Make integration free?
Yes, on the Make side. Timing is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, meaning operations, per month. Your Timing subscription is a separate matter, covered on the Timing pricing page.
02What do you need to connect Timing to Make?
An active Timing account and an API key. You generate the key in the API Keys section of the Timing web application and copy it from the screen. In Make, add any Timing module, click Create a connection, give the connection a name if you want to, and paste the key. That single connection then serves all 13 Timing modules in every scenario you build, so the setup happens once.
03Does the Timing Make integration react in real time?
No, because Timing has no trigger in Make: none of its 13 modules can start a scenario. Your scenario starts from another app, for example an instant trigger of your CRM that fires through a webhook as soon as something happens, or from a schedule on the first module, every 15 minutes by default. A scheduled scenario can open with Search Time Entries to pick up entries logged in Timing and pass them on.
04What if a Timing module is missing in Make?
It depends on what you need. The 13 modules cover projects, time entries and timers. For anything else the Timing API offers, use Make an API Call: it reaches any endpoint of the API with the connection you already have. Check the Timing API reference before building, since Make flags its own Timing documentation as AI-generated and possibly wrong. If the API has no such endpoint, another app in your stack will have to hold that data.
05Should you use Make or n8n for Timing?
It depends on the tool your team already runs. This page covers Make, where Timing brings 13 modules and a connection by API key. Many apps also have an n8n node, so check whether Timing has one before choosing and compare the modules each tool offers for your use case. Pick the platform where your other scenarios already live: one tool is easier to maintain than two, and the comparison page on the site sets out both approaches.