Resources · Make integration

Timeular Make integrationAutomate Timeular with Make.

Your hours can log themselves while you work. The Timeular Make integration gives you 25 modules: 3 triggers, 18 actions and 4 searches. This guide is for anyone who tracks time in Timeular and wants it to talk to other tools, with a first scenario built step by step.

Try the Timeular integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Timeular Make integration do for you?

The Timeular Make integration links your Timeular account to Make, a visual tool where you build a scenario: a chain of modules that runs on its own. Each module is one brick, like a trigger that notices a new time entry or an action that starts a tracking. No code, only blocks you click together.

Hours that land where they are billed. Watch Time Entries picks up every new entry, and the next module can copy it into a spreadsheet or an invoicing app. The team stops retyping timesheets.

Tracking that follows your work. When a task moves in another tool, List Activities finds the right Timeular activity and Start a Tracking launches the clock. Stop a Tracking closes it when the task is done.

A clean activity list. Create an Activity, Update an Activity and Archive an Activity keep Timeular aligned with the projects you manage elsewhere, and Create a Tag or Create a Mention adds the labels your reports rely on.

Make marks its documentation for this app as limited. Expect fewer explanations than for bigger apps, and test each module before you rely on it. When a module is missing, Make an API Call reaches the rest of the Timeular API with the same connection. The Make review tells you what to expect from the platform, and Make pricing explains how operations are counted. Many apps also exist on n8n; the n8n vs Make comparison lays out both tools side by side.

Connect

How do you connect Timeular to Make?

  1. 01

    Add a Timeular module

    In your scenario, click the +, type Timeular and pick any module. Make then asks for a connection, which is simply your Timeular account linked to Make once. Click Create a connection.

  2. 02

    Name the connection

    Give it a name you will recognize later, such as your work account. This step is optional, but it helps when several people or several Timeular accounts share the same Make organization.

  3. 03

    Authorize and save

    Approve access on the Timeular page that opens, or paste the key Timeular gives you if Make asks for one. Click Save. Every Timeular module in your scenarios can now reuse this connection.

First scenario

Build your first Timeular scenario in Make

GoalWhen a task starts in another app, Make finds the matching Timeular activity and starts tracking it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. The first module comes from the tool where your tasks start, for example your project board or your form app.

  2. 02

    Add List Activities

    Click the + on the right of that first module, search Timeular and pick List Activities. Create the connection. This search returns your activities as bundles, one item per activity.

  3. 03

    Add Start a Tracking

    Add Start a Tracking next. Map the activity found by the previous module into it, so the clock runs on the right project. Make shows the data it can reuse once the connection works.

  4. 04

    Test with Run once

    Click Run once, then trigger a real task in your other app. Open each module's bubble to read the bundles it received and check that Timeular shows a running tracking.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Switch the scenario on and let it work.

Triggers

What starts a Timeular scenario

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

Timeular1Watch for Time Entry Events

Watch for Time Entry Events

Instant trigger

In Make“Triggers when an event given in its type parameter occurs.”

This trigger wakes your scenario whenever something happens to a time entry, and you choose which event through its type setting. It suits flows that must react to changes, not just to new entries.

How it fires
instant. Timeular calls Make through a webhook as soon as the event happens, so there is no schedule to wait for.
When to use it
a finished entry should reach your billing sheet right away, before anyone edits the week.
Watch out
the type setting decides what reaches you, so check it with Run once and a real change in Timeular before you switch the scenario on.
Timeular2Watch for Tracking Events

Watch for Tracking Events

Instant trigger

In Make“Triggers when an event given in its type parameter occurs.”

Here the scenario reacts to the live timer rather than to saved entries, and the event type you select decides which tracking event wakes it. It links the timer people actually use to the rest of your tools.

How it fires
instant. Timeular calls Make through a webhook the moment the event occurs.
When to use it
set your chat status to busy when a focus activity starts, and clear it when it stops.
Watch out
this trigger follows the running timer; to react to saved time entries, pick Watch for Time Entry Events.
Timeular3Watch Time Entries

Watch Time Entries

Scheduled trigger

In Make“Triggers when a new time entry is created.”

Watch Time Entries brings every newly created time entry into your scenario as a bundle, one entry per bundle, ready to be copied or reported elsewhere. It is the simplest way to start, since it needs no event choice.

How it fires
scheduled. Make checks Timeular on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans.
When to use it
feeding a spreadsheet or reporting tool that does not need to react instantly.
Watch out
it only sees new entries, so edits to older entries go unnoticed; switch to the event trigger for those.
Modules

Everything Timeular can do in Make

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

Timeular1

Archive an Activity

Action

In Make“Archives an activity. It does not affect existing time entries and this activity will still be available in analytics.”

Archiving hides an activity from daily use while keeping its history: past time entries stay untouched and the activity still shows in analytics. That makes it the safe way to retire a project.

When to use it
a project is marked as closed in your project tool and should vanish from the Timeular picker.
Watch out
despite its internal key, it archives rather than deletes, so reports keep the old hours.
Timeular2

Create a Mention

Action

In Make“Creates a mention within the given space and scope (timeular is default).”

You get a new mention in a Timeular space, a label your team can pick when it describes its time. The scope defaults to Timeular unless you set another one.

When to use it
a new client appears in your CRM and should be available when people describe their time.
Watch out
pick the right space first, or the mention lands where nobody sees it.
Timeular3

Create an Activity

Action

In Make“Creates a new activity. It should have a name, a space and a color.”

This module adds a fresh activity to Timeular, the thing your team tracks time against. Each one needs a name, a space and a color, which you can map from the previous module.

When to use it
a signed deal or a new project in another app should immediately become something people can track.
Watch out
run List Activities before it if the same project could arrive twice, to avoid duplicates.
Timeular4

Create a Tag

Action

In Make“Creates a tag within the given space and scope (timeular is default).”

A new tag appears inside the space you choose, giving your entries one more label for filtering reports. The scope is Timeular by default.

When to use it
your team adds a new category of work, such as a billable phase, and reports must group hours by it.
Watch out
tags live per space, so creating one in the wrong space leaves your colleagues without it.
Timeular5

Create a Time Entry

Action

In Make“Creates a new time entry. The time entry will be created even if it overlaps with other time entries – in result existing time entries will be split or deleted in such manner, that new one will fit without overlapping.”

Creating a time entry writes hours into Timeular without anyone touching the timer, for work logged elsewhere such as a meeting in your calendar.

When to use it
a calendar event ends and its duration should count against a client activity.
Watch out
the entry is saved even if it overlaps others, and Timeular then splits or deletes the existing entries to make room. Test with Run once on a quiet slot first.
Timeular6

Delete a Mention

Action

In Make“Deletes the given mention.”

Removing a mention cleans up labels that no longer mean anything, such as a client you stopped working with. It works on one mention at a time, identified by the previous module.

When to use it
a contact is archived in your CRM and should disappear from Timeular too.
Watch out
a delete cannot be undone from Make, so add a filter that checks you have the right mention.
Timeular7

Delete a Tag

Action

In Make“Deletes the given tag.”

Delete a Tag removes one tag from your Timeular setup for good, which keeps the tag list short and readable for people picking one.

When to use it
a category of work was merged into another and the old tag only causes wrong choices.
Watch out
Make cannot bring the tag back, so run List Tags first and check its bundle with Run once before you activate the scenario.
Timeular8

Delete a Time Entry

Action

In Make“Deletes a time entry.”

This action erases one time entry from Timeular. It is useful when entries are generated automatically and some of them turn out to be wrong.

When to use it
a meeting is cancelled in your calendar after an entry was already created for it.
Watch out
hours deleted here vanish from your reports; archiving the activity is the gentler option when you only want to hide something.
Timeular9

Get a Time Entry

Action

In Make“Finds a time entry by its ID.”

Give it the ID of an entry and Get a Time Entry returns that one entry with its details, ready for the next module to read.

When to use it
an instant trigger hands you an entry ID and you need the full record before updating an invoice line.
Watch out
it only finds by ID; to look across a period, Search Time Entries is the better fit.
Timeular10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules covers your need, Make an API Call lets you reach any endpoint of the Timeular API, reusing the connection you already created.

When to use it
you need something the 25 modules do not expose and you have the Timeular API reference open next to you.
Watch out
you write the request yourself, so check the response with Run once before relying on it.
Timeular11

Show Current Tracking

Action

In Make“Shows current tracking.”

Show Current Tracking tells your scenario what is running right now in Timeular, if anything, so the next modules can decide what to do.

When to use it
before starting a new tracking, check whether one is already running, and stop it first if needed.
Watch out
it reflects the moment the module runs, so a scheduled scenario may read a tracking that has already changed.
Timeular12

Start a Tracking

Action

In Make“Starts a new tracking.”

This action starts the Timeular timer on an activity, so time starts counting without anyone clicking anything.

When to use it
a support ticket is assigned or a call begins in another tool, and time should count from that moment.
Watch out
pair it with Show Current Tracking, because an already running tracking may need to be stopped first.
Timeular13

Stop a Tracking

Action

In Make“Stops the current tracking.”

Stop a Tracking ends whatever tracking is currently running, so the time turns into a finished entry you can report on.

When to use it
a ticket is closed or a call ends in another app, and the clock should stop with it.
Watch out
it acts on the current tracking only, so if nothing is running the scenario has nothing to stop; test that case with Run once.
Timeular14

Update a Mention

Action

In Make“Creates new mention label.”

Updating a mention gives it a new label while keeping the same mention, so you rename it instead of creating a second one.

When to use it
a client changes its company name in your CRM and Timeular should follow.
Watch out
fetch the mention with List Mentions first, so you update the right one rather than a lookalike.
Timeular15

Update an Activity

Action

In Make“Updates the name and color of the activity.”

With this module you change the name and color of an existing activity, while its tracked hours stay where they are.

When to use it
a project is renamed in your project tool, or you color activities by status and the status changes.
Watch out
only the name and color change here; to retire the activity, use Archive an Activity.
Timeular16

Update a Tag

Action

In Make“Creates a new label for the tag.”

Update a Tag sets a new label on an existing tag, so the tag keeps its place and only its wording changes.

When to use it
your naming convention changes and old tags must match the new category names.
Watch out
run List Tags before it and filter on the old label, otherwise you may rename the wrong tag in a crowded space.
Timeular17

Update a Time Entry

Action

In Make“Updates an existing time entry. Please note, that both the new and old activity attached to the time entry has to belong to the same integration.”

You correct a saved time entry here, including the activity it belongs to, without deleting and recreating it.

When to use it
a meeting was moved in your calendar after its hours were logged, and the entry should follow.
Watch out
the old and the new activity must belong to the same integration; check this before mapping a new activity.
Timeular18

Update a Tracking

Action

In Make“Edits the current tracking.”

Update a Tracking edits the tracking that is running right now, so you can fix it before it becomes a saved entry.

When to use it
someone started the timer on the wrong activity and another app signals the right one.
Watch out
it only touches the current tracking; once stopped, the time is an entry and you need Update a Time Entry instead.
Timeular19

List Activities

Search

In Make“Lists all activities.”

This search returns all your Timeular activities, each one as its own bundle, so later modules can pick the one they need.

When to use it
matching a project name from another app to the Timeular activity before starting a tracking or creating an entry.
Watch out
every activity comes out, so add a filter after it or the next module runs once per activity and uses operations.
Timeular20

List Mentions

Search

In Make“Lists all mentions.”

List Mentions pulls every mention from Timeular, one bundle each, which gives you the reference list of people and clients your team uses.

When to use it
checking whether a client already has a mention before Create a Mention adds a duplicate.
Watch out
the search can return zero, one or many bundles; plan a filter for each case.
Timeular21

List Tags

Search

In Make“Lists all tags.”

All your tags come back from this search, one bundle per tag, ready to be compared, copied or cleaned up by the next modules.

When to use it
syncing your categories of work into a reporting sheet, or finding a tag before renaming or deleting it.
Watch out
anything placed after it runs once per tag, so filter early to save operations.
Timeular22

Search Time Entries

Search

In Make“Returns time entries in a given range.”

Search Time Entries returns the entries recorded within a date range you set, one bundle per entry, which is what a timesheet export needs.

When to use it
a project closes and you want all its hours in a spreadsheet or an invoice.
Watch out
a wide range means many bundles and many operations downstream; add an aggregator if one row per period is enough.
Need help

Need help automating Timeular with Make?

A person reads every message.

FAQ

Timeular and Make: common questions

01Is the Timeular Make integration free?
Yes. Timeular is a standard app in Make, available from the Free plan. The Free plan gives you 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one per module run on one bundle. Your Timeular subscription is a separate matter this page does not cover.
02What does it take to connect Timeular to Make?
A Timeular account and a Make account are enough, and the Make documentation lists no other prerequisite. You add any Timeular module, click Create a connection, optionally name it, then authorize Make on the Timeular page or paste the key Timeular provides, and save. That connection is created once and reused by every Timeular module in all your scenarios. Since the official documentation for this app is marked as limited, testing a small scenario with Run once is the quickest way to see what the modules return.
03Does the Timeular trigger in Make react in real time?
It depends on which one you pick. Watch for Time Entry Events and Watch for Tracking Events are instant triggers: Timeular calls Make through a webhook as soon as the event happens. Watch Time Entries is scheduled: Make checks Timeular on the scenario's schedule, every 15 minutes by default, 15 minutes at the shortest on the Free plan and 1 minute on paid plans. For timer changes, go instant. For a steady feed of new entries into a sheet, the scheduled trigger is simpler and does the job.
04What if a Timeular module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Timeular API with the connection you already have, so you are not limited to the 25 listed modules. You write the request yourself, which means reading the Timeular API reference and testing the response with Run once before you rely on it. Keep in mind that Make marks the documentation of this app as limited, so some details of the listed modules may also need a quick test before you build on them.
05Make or n8n for Timeular: which one fits?
It depends on the tool your team already uses and is comfortable with. On Make, Timeular comes with 25 modules, including 2 instant triggers and Make an API Call for anything else, and it runs from the Free plan. Many apps also have an n8n node, so check whether Timeular has one and what it covers before deciding. The comparison of both platforms linked higher on this page lays out the criteria side by side, without declaring a winner for every case.
Same platform

Other docs you might need on this stack.

Browse all integrations