Zum Hauptinhalt springen

Zapier

Zapier connects Timesheet to thousands of other apps, so an event in Timesheet can trigger an action somewhere else (and the other way around) without any code. For example, a new time entry can create a Google Calendar event, or a closed deal in your CRM can create a Timesheet project.

Pro plan

The Zapier integration requires a Pro plan or above. See the Plans page for the full comparison. A Zapier account is also needed; Zapier offers a free tier.

How it works

A Zap is an automated workflow with two parts:

  • A trigger: an event that starts the Zap, such as a new time entry in Timesheet.
  • An action: what happens in response, such as adding a row to Google Sheets.

You can add filters so an action only runs when a condition is met, and chain several actions together.

Before you start

  • A Timesheet Pro plan.
  • A Zapier account.
  • A Timesheet API key. Create one in the web app under Integrations > API Keys (see API keys). The key is shown only once, so copy it before you leave the page.

Connect Timesheet to Zapier

Open the Timesheet app on Zapier. You can also reach it from the Integrations page in the web app, on the Timesheet Zapier card.

The Timesheet app page on Zapier

  1. In Zapier, create a Zap and choose Timesheet as the trigger or action app.
  2. When Zapier asks you to sign in to Timesheet, paste your API key.
  3. Zapier confirms the connection, and you can reuse it in any future Zap.
Beta

The Timesheet app on Zapier is in beta. The available triggers and actions may change. The Zapier app page always shows the current list.

Build a Zap

The steps are the same for any workflow:

  1. Choose a trigger. Pick the Timesheet event (or the event in the other app) that starts the Zap.
  2. Choose an action. Pick what should happen in response.
  3. Map the fields. Tell Zapier which Timesheet values fill each field in the action, such as project name, duration, or description.
  4. Test it. Zapier runs the Zap once with sample data so you can check the result.
  5. Turn it on. Publish the Zap, then create a real entry in Timesheet to confirm it works.

For the full set of Timesheet triggers and actions, and ready-made templates, see the Timesheet app page on Zapier.

Tips

  • Start with one simple Zap and test it before building more complex ones.
  • Give each Zap a clear name, so you can tell at a glance what it does.
  • Use a filter to keep a Zap focused, for example to run only for billable entries.

Troubleshooting

The Zap does not run. Check that the Zap is turned on, that the trigger event actually happened, and that no filter is blocking it.

Authentication fails. Your API key may have been deleted or have expired. Create a new key in Integrations > API Keys and reconnect Timesheet in Zapier.

Fields are empty in the action. Open the Zap and confirm each action field is mapped to a Timesheet value.

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

See also

  • Integrations: API keys, webhooks, and the Integration Marketplace.
  • MCP server: control Timesheet from AI assistants.
  • Plans: compare what each plan includes.