Zapier Integration
Zapier Integration
Connect Working Timer to thousands of apps in Zapier. For example, you can create a work record from a calendar event, form submission, spreadsheet row, or completed task.
The integration uses the Working Timer Public API. You do not need to share your Working Timer password with Zapier.
What You Need
- A Working Timer account with an active Public API plan or trial
- A paid Zapier plan that includes API by Zapier or Webhooks by Zapier
- The ID of the Working Timer profile that will receive the records
Important: Treat your API key like a password. Do not put it in a Zap name, note, URL, or any field that may appear in task history.
1. Create a Working Timer API Key
- Open the Working Timer API portal.
- Select Sign In and log in with your Working Timer account.
- In the API Dashboard, find API Keys and select New Key.
- Enter a recognizable name such as
Zapier, then select Create. - Copy the key immediately. It starts with
wt_ak_and is shown only once.
If you lose the key, revoke it and create a replacement.
2. Find Your Profile ID
Every work record must belong to a Working Timer profile.
- Open the Working Timer API reference.
- Select Authorize and enter your API key in the ApiKey field.
- Open
GET /api/v1/Profile, select Try it out, and then select Execute. - Find the required profile in the response and copy its
id.
The profile ID is a GUID similar to a1b2c3d4-1234-5678-9abc-1234567890ab.
3. Connect Working Timer to API by Zapier
API by Zapier keeps the API key in a reusable connection instead of exposing it in each Zap step.
- In Zapier, open Apps, select Add connection, and choose API by Zapier.
- For Authentication type, select Static Headers (API key).
- Add this header on one line, replacing the example with your key:
X-Api-Key: wt_ak_your_api_key_here
- Set Connection name to
Working Timer. - Set Domain filter to
api.workingtimer.com. - Set Test URL to:
https://api.workingtimer.com/api/v1/Profile?pageSize=1
- Select Yes, Continue to API by Zapier.
API by Zapier is currently a beta Zapier feature. If it is unavailable in your account, use the Webhooks method below.
4. Create Your First Zap
This example creates a Working Timer work record whenever your chosen trigger runs.
- Create a Zap and choose a trigger, such as a new calendar event, completed task, form response, or spreadsheet row.
- Add an action and select API by Zapier.
- Select the API Request action and choose your Working Timer connection.
- Configure the request:
- Method:
POST - URL:
https://api.workingtimer.com/api/v1/WorkRecord - Headers: no authentication header is needed; the connection adds it automatically
- Body: use the JSON below
- Method:
{
"profileId": "YOUR_PROFILE_ID",
"year": 2026,
"month": 7,
"day": 31,
"clockIn": 540,
"clockOut": 1020,
"breakMinutes": 30,
"recordType": "common",
"isPaid": true,
"note": "Created by Zapier"
}
- Replace
YOUR_PROFILE_IDwith the profile ID from step 2. - Map the date, time, and note values from your Zap trigger. Use Formatter by Zapier first if the trigger values need to be converted.
- Select Test step. A successful request returns status
201and the created record. - Check the record in Working Timer, then publish the Zap.
Time Values
clockIn and clockOut are the number of minutes since midnight:
08:00=48009:00=54017:00=102017:30=1050
For overnight shifts, clockOut may be greater than 1440. For example, 02:00 on the following day is 1560.
Alternative: Webhooks by Zapier
If API by Zapier is not available, add Webhooks by Zapier as the action:
- Select the POST event.
- Set URL to
https://api.workingtimer.com/api/v1/WorkRecord. - Set Payload Type to
JSON. - Add the work-record fields shown in the example above to Data.
- Under Headers, add:
X-Api-Key— your Working Timer API keyContent-Type—application/json
- Test the action and confirm that Zapier receives a
201response.
With this method, the key is configured separately in each webhook step. Use API by Zapier when possible so the key is managed through one secure connection.
Other Useful Requests
Use additional API Request steps to read or update Working Timer data:
- List profiles:
GET https://api.workingtimer.com/api/v1/Profile - List work records:
GET https://api.workingtimer.com/api/v1/WorkRecord - Filter records by date: add
fromDateandtoDateas query parameters inYYYY-MM-DDformat - Update a record:
PATCH https://api.workingtimer.com/api/v1/WorkRecord/{id} - Delete a record:
DELETE https://api.workingtimer.com/api/v1/WorkRecord/{id}
See the API reference for projects, activities, notes, work requests, reports, and other available endpoints.
Troubleshooting
- 401 Unauthorized — the API key is missing, incomplete, revoked, or entered under the wrong header name. The header must be exactly
X-Api-Key. - 403 Forbidden — activate or renew the Public API plan or trial in the API Dashboard.
- 400 Bad Request — check that the body is valid JSON and that the date and minute values are numbers rather than formatted time strings.
- Profile was not found — verify the
profileIdbelongs to the same Working Timer account as the API key. - 429 Too Many Requests — the Zap is running too frequently or the account has reached an API limit. Retry later and review usage in the API Dashboard.
- Duplicate records — check Zapier task history and make sure the trigger is not replaying the same item. Use a filter or unique source ID before the Working Timer action when needed.
Revoke or Replace Zapier Access
Open the API Dashboard at api.workingtimer.com, find the Zapier key, and select Revoke. Zaps using that key will stop until you create a new key and update the Zapier connection.