Make

Make connects Timesheet to other apps in visual workflows called scenarios. A scenario can start when something happens in Timesheet, such as a new time entry, or act in Timesheet when something happens elsewhere, such as a closed ticket that should close its to-do.

Pro plan

The Make integration requires a Pro plan or above. See the Plans page for the full comparison. The absence modules also need an organization on the Business or Enterprise plan. A Make account is needed too; Make offers a free plan.

Before you start

• A Timesheet Pro plan or above.
• A Make account.

Connect Timesheet to Make

1. Add the Timesheet app to your Make account with the Timesheet app link on the Make integration page.
2. In a Make scenario, add any Timesheet module and create a connection. Keep Timesheet account as the connection type.
3. Sign in to Timesheet in the window that opens and select Allow access.

Make names the connection after your Timesheet email address. You can reuse the connection in all your scenarios. The sign-in lasts one year. After that, reauthorize the connection under Connections in Make.

Connect with an API key instead

1. In the web app, open Integrations, go to API Keys, and select New API Key. Give the key a name, select Generate Key, and copy the key. It is shown only once.
2. In Make, create a connection, select Timesheet API key as the connection type, and paste the key.

What you can use

In Make, time entries are called tasks, as in the Timesheet API.

• Events: Watch events starts a scenario when the timer starts, stops, pauses, or resumes, or when a task, project, to-do, team, tag, or rate is created or updated.
• Timer: start, stop, pause, resume, update, or read the running timer.
• Tasks: create, update, get, delete, and duplicate tasks, search them, and get time totals (duration, breaks, earnings, expenses, and mileage) for a filter.
• Notes, expenses, and breaks: add them to a task, and search notes and expenses.
• Projects and to-dos: create, update, get, delete, and list them.
• Tags, teams, and rates: create, update, delete, and list tags, and list teams and rates.
• Exports: generate an Excel, CSV, or PDF report as a download link, or send it by email.
• Absences: create, update, get, delete, search, approve, reject, and cancel absences in an organization.
• Make an API call: call any endpoint of the Timesheet API with the same connection. Enter the path without the version, for example /tasks/search.

Pick values from lists

Fields such as project, to-do, tag, rate, team, report, or absence type show a list of your items, so you do not need to copy IDs. Some lists depend on another field:

• The To-do list shows the open to-dos of the selected project. Select the project first.
• The Employee and Absence type lists load for the selected organization. Select the organization first.

The lists show active projects, tags, and rates, and open to-dos. To use an archived item, map its ID from an earlier module instead.

React to events

1. Add Watch events as the first module of a scenario.
2. Create a webhook and select the event, for example Task created.
3. Save the scenario and turn it on.

Timesheet registers the webhook when you create it in Make and removes it when you delete it there. Each trigger listens for one event, so add one scenario per event.

There are no delete events. Deleting a task or to-do fires its updated event.

Build a scenario

1. Start with a trigger. Use Watch events, a trigger from another app, or a schedule.
2. Add Timesheet modules. Pick what should happen, for example Create a task or Email an export.
3. Map the fields. Fill each field with a value from an earlier module or pick one from the list.
4. Test it. Select Run once and check the result in Timesheet.
5. Turn it on. Save the scenario and switch on scheduling.

Tips

• Dates use the time zone of your Make scenario.
• The download link of Generate an export works for 10 minutes. Download the file in the same scenario, for example with the Get a file module of the HTTP app.
• If you connect with an API key and set an expiry date on it, renew the key before that date.

Troubleshooting

A module fails with [401]. Reauthorize the connection under Connections in Make. For an API key connection, check that you copied the whole key and that the key is not deleted or expired. Your Timesheet plan must be Pro or above.

An absence module fails with [403]. The organization needs the Business or Enterprise plan, and you can only manage absences of yourself and of the people you manage.

Watch events does not fire. Check that the scenario is on, that the trigger listens for the right event, and that your plan is still Pro or above. The webhook is listed under Integrations > Webhooks in the web app.

The To-do or Employee list is empty. Select the project or organization first.

For scenario-specific help, see the Make help center. For account questions, contact support@timesheet.io.

See also

• Integrations: API keys, webhooks, and the Integration Marketplace.
• Zapier: connect Timesheet to thousands of apps with Zapier.
• MCP server: control Timesheet from AI assistants.
• Plans: compare what each plan includes.