Overview
Create a new time entry in your workspace using the Zapier integration API. This endpoint allows you to add time entries with comprehensive information including project associations, task assignments, and tag categorization.This endpoint is designed for Zapier integrations but can be used with any application that needs to create time entries programmatically.
Authentication
All requests require a valid API key in the Authorization header:Create Time Entry
Request Body
The UUID of the workspace where the time entry will be created.Example:
"w1b2c3d4-e5f6-7890-abcd-ef0987654321"The start time of the time entry. Must be a valid ISO 8601 datetime string.Example:
"2024-01-15T09:00:00.000Z"The end time of the time entry. Must be a valid ISO 8601 datetime string and after the start time.Example:
"2024-01-15T17:00:00.000Z"Whether this time entry is billable to the client.Example:
trueThe date when the time entry occurred. If not provided, defaults to the date from start_time.Example:
"2024-01-15T10:00:00.000Z"Description of the work performed during this time entry.Example:
"Development work on new feature"Duration of the time entry in seconds. If not provided, calculated from start_time and end_time.Example:
28800Whether this time entry was entered manually (true) or tracked automatically (false).Example:
trueThe UUID of the team member who performed the work. Must be a valid team member in the workspace.Example:
"tm1a2b3c4-d5e6-7890-abcd-ef1234567890"The UUID of the project associated with this time entry. Must be a valid project in the workspace.Example:
"p1a2b3c4-d5e6-7890-abcd-ef1234567890"The UUID of the task associated with this time entry. Must be a valid task in the specified project.Example:
"t1a2b3c4-d5e6-7890-abcd-ef1234567890"Array of tag UUIDs to associate with this time entry. All tags must exist in the workspace.Example:
["tag1a2b3c4-d5e6-7890-abcd-ef1234567890", "tag2b3c4d5-e6f7-8901-bcde-f23456789012"]Response
Success Response
Returns the created time entry object with all associated data:Response Fields
Unique time entry identifier (UUID format)
Date when the time entry occurred (ISO 8601 format)
Description of the work performed
Start time of the time entry (ISO 8601 format)
End time of the time entry (ISO 8601 format)
Duration of the time entry in seconds
Duration of the time entry in hours (calculated from seconds)
Whether the time entry is billable
Whether the time entry was entered manually
Associated workspace identifier
Associated workspace name
Associated team member identifier
Associated team member name
Associated team member email
Associated team member role
Associated project identifier
Associated project name
Associated project status
Associated client identifier (if project has a client)
Associated client name (if project has a client)
Associated task identifier
Associated task name
Associated task status
Associated timesheet identifier
Associated timesheet status
Array of associated tags
Total number of tags associated with this time entry
ISO 8601 timestamp when time entry was created
ISO 8601 timestamp when time entry was last modified
Error Responses
400 Bad Request - Validation Error
400 Bad Request - Validation Error
Solution: Check the request body and ensure all required fields are provided with valid values
400 Bad Request - Invalid Time Range
400 Bad Request - Invalid Time Range
Solution: Ensure end_time is after start_time
400 Bad Request - Invalid Team Member
400 Bad Request - Invalid Team Member
Solution: Verify the team member ID and ensure they belong to the workspace
400 Bad Request - Invalid Project
400 Bad Request - Invalid Project
Solution: Verify the project ID and ensure it belongs to the workspace
400 Bad Request - Invalid Task
400 Bad Request - Invalid Task
Solution: Verify the task ID and ensure it belongs to the specified project
400 Bad Request - Invalid Tags
400 Bad Request - Invalid Tags
401 Unauthorized
401 Unauthorized
500 Internal Server Error
500 Internal Server Error
Solution: Retry the request or contact support if the issue persists
Zapier Integration
Zapier Action Configuration
When using this endpoint in Zapier:- Workspace Selection: Use the dynamic dropdown to select the target workspace
- Required Fields:
workspace_id,start_time,end_time, andbillableare required - Team Member Selection: Optionally select a team member from the dynamic dropdown
- Project Association: Optionally select a project and task
- Tag Assignment: Optionally select tags for categorization
Sample Zapier Usage
1
Trigger Setup
Set up a trigger (e.g., calendar event, form submission) that provides time entry information
2
Action Configuration
Configure the “Create Time Entry” action with:
- Workspace: Select your target workspace
- Start Time: Map from trigger data
- End Time: Map from trigger data
- Billable: Set billing status
3
Association Setup
Configure associations:
- Team Member: Select from available team members
- Project: Select from available projects
- Task: Select from available tasks (if project selected)
- Tags: Select relevant tags for categorization
4
Test & Activate
Test the Zap with sample data, then activate for live use
Use Cases
Calendar Integration
Calendar Integration
Meeting Time Tracking: Automatically create time entries when calendar events are created, ensuring all meetings and appointments are tracked for billing and reporting.
Project Management
Project Management
Task Completion Tracking: Create time entries when tasks are completed in project management tools, maintaining accurate project time records.
Client Billing
Client Billing
Automated Billing: Create billable time entries based on client work activities, ensuring accurate client billing and invoicing.
Team Productivity
Team Productivity
Activity Tracking: Create time entries for different types of work activities, providing insights into team productivity and time allocation.
Time Entry Best Practices
Time Format Guidelines
- ISO 8601 Format: Always use ISO 8601 datetime format for consistency
- Timezone Handling: Include timezone information in datetime strings
- Duration Calculation: Let the system calculate duration from start/end times when possible
Description Standards
- Clear Descriptions: Use descriptive text that explains what work was performed
- Consistent Format: Follow consistent description patterns across your team
- Context Information: Include relevant context about the work performed
Tagging Strategy
- Work Type Tags: Use tags to categorize different types of work
- Project Phase Tags: Tag entries by project phase or milestone
- Client-Specific Tags: Use tags for client-specific work categorization
Important Notes
Duration Calculation: If duration is not provided, it’s automatically calculated from start_time and end_time. The calculation is in seconds.
Best Practices:
- Always provide clear, descriptive text for time entries
- Use consistent tagging strategies across your team
- Validate time ranges before sending requests
- Associate time entries with appropriate projects and tasks
- Test with sample data before implementing in production
- Handle error responses gracefully in your application
- Consider timezone implications when working with distributed teams
Rate Limits
- Rate Limit: 100 requests per minute per API key
- Burst Limit: 10 requests per second
- Daily Limit: 10,000 requests per day
Rate limits are applied per API key and workspace combination. Contact support if you need higher limits for your use case.