Resources · Make integration

Timely Make integrationAutomate Timely with Make.

Stop typing the same Timely events by hand. The Timely Make integration gives you 8 modules: 7 actions and 1 search to create, update and time events. This guide walks you through the connection and a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Timely Make integration do for you?

The Timely Make integration links your Timely account to Make, a visual tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick. Here, those bricks create, read, change, search and time events in Timely without you opening it.

Events that write themselves. A task closed in your project tool or a form filled by a client can feed Create an Event, so the entry lands in Timely instead of waiting for someone to remember them.

Timers that follow the work. When a support ticket moves to in progress in another app, Start a Timer can begin counting on the matching event, and Stop a Timer ends it when the ticket closes. You find the event first with Search Events or Get an Event.

Clean-up and corrections. Update an Event corrects an existing event when the information changes elsewhere, and Delete an Event removes an entry that should not exist.

What Make does not give you here: Timely has no trigger module, so nothing in Timely can start a scenario on its own. The scenario starts from another app or from Make's own schedule. For anything the listed modules skip, Make an API Call reaches the rest of the Timely API. Before you pick a plan, read the Make pricing guide; if you also weigh the other tool, Timely often has an n8n node too, and the n8n vs Make comparison lays out the differences. Prefer a guided start? The Make training covers these building blocks step by step.

Connect

How do you connect Timely to Make?

  1. 01

    Create an OAuth app in Timely

    As an admin user in Timely, open Settings, then Devs. Give your application a name, paste the callback URI https://www.integromat.com/oauth/cb/timelyapp, and copy the Client ID and Client secret shown on screen.

  2. 02

    Add a Timely module in Make

    In your scenario, add any Timely module and click Create a connection. A connection is your Timely account linked to Make once, then reused by every Timely module. The Connection name field is optional but helps when you have several accounts.

  3. 03

    Paste the credentials and confirm

    Enter the Client ID and Client secret you copied, then follow the on-screen instructions to authorize access. Once the connection is saved, Make can list the Timely objects it reads, so you pick from menus instead of typing IDs.

First scenario

Your first scenario with Timely

GoalWhen a new item arrives in another app, Make creates the matching event in Timely.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Since Timely has no trigger, this first module comes from the app where the work starts.

  2. 02

    Pick the starting app

    Search that app by name, pick its module and connect your account. Each item it returns becomes a bundle: one record that flows to the next module.

  3. 03

    Add Create an Event

    Click the + on the right of the first module, search Timely and choose Create an Event. Select your Timely connection, then map data from the previous module into the event fields Make shows you.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Check in Timely that the event looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default on a new scenario, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What each Timely module does

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

Timely1

Create an Event

Action

In MakeCreates a new event.

Here you get a brand new event in Timely, filled from data another app already holds. Nobody has to open Timely.

When to use it
a task gets closed in your project tool and you want the matching entry recorded in Timely straight away.
Watch out
each run creates a new event, so a scenario that sees the same item twice will log it twice unless you filter first.
Timely2

Delete an Event

Action

In MakeDeletes a specified event.

This one removes a single event from Timely, the one you point it at, and leaves everything else alone.

When to use it
a meeting gets cancelled in your calendar tool and the placeholder event in Timely should disappear with it.
Watch out
a deletion cannot be undone from the scenario, so test with Run once on a throwaway event before switching anything on.
Timely3

Get an Event

Action

In MakeReturns a specified event.

You get the full details of one event you already know, ready to map into the next modules of the scenario.

When to use it
another app stores the event reference and you need its current content before updating it or sending it to a report.
Watch out
it needs the exact event to read; when you only know rough criteria, reach for Search Events instead.
Timely4

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

With this module, any endpoint of the Timely API becomes reachable from your scenario, using the same connection as the other Timely modules.

When to use it
the seven other modules do not cover what you need, for example a Timely object that has no dedicated module.
Watch out
you build the request yourself, so keep the Timely API documentation open and test the call with Run once.
Timely5

Start a Timer

Action

In MakeStarts timer on an event.

Tracking begins automatically: this module starts the timer on an event, so the clock runs from the moment the work actually starts elsewhere.

When to use it
a support ticket switches to in progress in your help desk and the time spent on it should count from there.
Watch out
it acts on an existing event, so create or find that event earlier in the scenario.
Timely6

Stop a Timer

Action

In MakeStops timer on an event.

Closing the loop, this module halts the running timer on an event so the recorded time matches the real end of the task.

When to use it
the ticket or task that started the timer is marked done in the other app.
Watch out
pair it with the scenario that starts the timer and point both at the same event, or a timer may keep running on its own.
Timely7

Update an Event

Action

In MakeUpdates a specified event.

Changes reach an event that already exists instead of creating a duplicate, so Timely stays in line with what changed in your other tools.

When to use it
a client renames a project deliverable and the related event in Timely has to follow.
Watch out
it needs to know which event to change, so place Search Events or Get an Event just before it.
Timely8

Search Events

Search

In MakeSearches for events or lists them all.

Finding events without knowing their references is what this search does: it returns every match, or the whole list, as separate bundles.

When to use it
before an update, a timer or a deletion, to locate the right event from what the other app knows.
Watch out
a search can return zero, one or many bundles, and each later module then runs once per bundle, which adds operations.
Need help

Need help automating Timely with Make?

A person reads every message.

FAQ

Timely and Make: common questions

01Is the Timely Make integration free?
Yes, on the Make side. Timely is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 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 count usage in credits per month. You still need an active Timely account, on the Timely plan of your choice.
02What do you need to connect Timely to Make?
An active Timely account and an OAuth application created by an admin user. In Timely, go to Settings, then Devs, name the application, enter the callback URI given by the Make documentation, and copy the Client ID and Client secret. In Make, add a Timely module, click Create a connection, optionally name it, and paste those credentials. The connection is then reused by every Timely module in your scenarios. Not an admin? Ask one to create the application and pass you the two credentials.
03Can Timely start a Make scenario in real time?
No, because Timely has no trigger module in Make. A scenario that works with Timely has to start elsewhere: from a trigger of another app, such as a form or a project tool, or from Make's own scheduling, which runs a new scenario every 15 minutes by default. From there, the Timely actions and the Search Events module do the work on each run. In practice, pick the app where the work begins and let Timely follow, rather than the other way around.
04What if a Timely module is missing in Make?
Use Make an API Call. It calls any endpoint of the Timely API with the connection you already set up, so you are not limited to the 7 other modules. You write the request yourself, which asks for a look at the Timely API documentation. Note that the Make documentation for this app is flagged as AI-generated from Timely's own docs, so check important details with Timely directly. Test each new call with Run once before switching the scenario on.
05Should you use Make or n8n for Timely?
It depends on the tool your team already works in. On Make, Timely offers 8 modules covering events, timers and a search, plus an open API call, and it runs on the Free plan. Timely often has an n8n node as well, so the choice comes down to which editor you prefer to build and maintain your automations in, rather than to what Timely itself allows. Both can reach the Timely API when a module is missing, so start with the editor your team finds easier to read.