Make Integration

Make builds the workflow. Timesheet keeps the hours. Connect the two and a scenario can log time when a ticket closes, start a timer from a form, or email last month's report to your accountant, without anyone retyping numbers.

What you can automate

Triggers

• Watch events fires when something happens in Timesheet: the timer starts, stops, pauses, or resumes, or a time entry, project, to-do, team, tag, or rate is created or updated

Timer

• Start the timer on a project, stop, pause, or resume it, change the running entry, or read it

Time entries

• Create, update, get, duplicate, and delete time entries, with project, to-do, start and end, description, tags, billable status, and rate
• Search time entries by text, date range, project, tag, to-do, team, or billing status
• Get the totals for any filter: duration, breaks, earnings, expenses, and mileage
• Add notes, expenses, and breaks to a time entry, and search notes and expenses

Projects, to-dos, and tags

• Create, update, get, delete, and list projects and to-dos, for example to close a to-do when its ticket is done
• Create, rename, archive, delete, and list tags, and list your teams and rates

Reports

• Generate an Excel, CSV, or PDF report and get a download link, or have Timesheet email it

Absences

• Request, update, approve, reject, cancel, and delete absences in an organization, and search them by employee, type, status, or dates

In Make, time entries are called tasks, as in the Timesheet API: look for Create a task or Search tasks.

Make an API call reaches any endpoint of the Timesheet API with the same connection, for the cases the ready-made modules do not cover.

Ideas to start with

• Calendar to timesheet: for every new event in a work calendar, create a time entry on the matching project.
• Monthly report: on the first of each month, email last month's PDF report to your accountant.
• Ticket done, to-do closed: when an issue is resolved in your tracker, close the matching to-do in Timesheet.
• Timer from anywhere: start or stop the timer from a Make webhook or a form submission.
• Absences in the team chat: every morning, search pending absence requests and post them to the managers' channel.
• Projects in sync: when a project is created in Timesheet, create the same client or deal in your CRM.

Before you start

• A Make account.
• A Timesheet Pro plan or above. The 30-day trial includes it. See plans and pricing.
• For the absence modules, an organization on the Business or Enterprise plan, or in its trial.

Connect it

1. Add the Timesheet app to your Make account through the Timesheet app link.
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 shows your Timesheet email address on the connection.

Prefer an API key? In the Timesheet web app, open Integrations, go to API Keys, and select New API Key. Give it a name, select Generate Key, and copy the key right away: it is shown only once. In Make, choose Timesheet API key as the connection type and paste the key.

Fields such as project, to-do, tag, rate, team, or absence type are lists to pick from. When one list depends on another, pick the first one first: the to-do list shows the to-dos of the chosen project, and the employee and absence type lists load for the chosen organization.

To react to events, add Watch events, create a webhook, and pick the event. Timesheet registers the webhook on its side automatically and removes it when you delete the webhook in Make. Each trigger listens for one event, so add one trigger per event you care about.

Good to know

• There are no delete events. Deleting a time entry or to-do fires its updated event, so check the item in your scenario if that matters.
• Events cover what your account can see. If you manage a project, a trigger can also fire for a teammate's entries in it.
• The lists show active projects, tags, and rates, and open to-dos. To use an archived item, map its ID from an earlier module.
• A report's download link works for 10 minutes, so download the file in the same scenario, for example with the HTTP app.
• Events reach Make only while your plan is Pro or above, or in its trial. If it lapses, scenarios stop receiving events until the plan is active again.
• A sign-in connection lasts one year. After that, reauthorize it under Connections in Make.
• If you connect with an API key and give it an expiry date, renew it before then, or the scenario stops working.
• Deleting the connection in Make, or the API key it uses, stops Make's actions. Webhooks belong to your account, so also delete them under Integrations > Webhooks if you want events to stop.

Prefer Zapier? Timesheet connects there too: see the Zapier integration. Questions about a scenario? Write to support@timesheet.io.