edit_time_entry¶

Modify existing time entries with flexible field updates for precise time tracking corrections.

Summary¶

The edit_time_entry tool allows you to update any aspect of an existing time entry in EARLY. You can change the start/end times, switch to a different activity, update the description, or modify any combination of these fields.

Key Features: - Update any field individually or in combination - Flexible time modification (start time, end time, or both) - Activity reassignment to different projects - Description updates for better tracking accuracy - Real-time integration with EARLY API v4

Parameters¶

Update Patterns¶

1. Time Adjustment¶

Update just the timing without changing activity or description:

{
  "timeEntryId": "te_abc123",
  "startTime": "2025-10-14T09:00:00Z",
  "endTime": "2025-10-14T10:30:00Z"
}

2. Activity Reassignment¶

Move time entry to a different project/activity:

{
  "timeEntryId": "te_abc123",
  "activityId": "proj_new_project_456"
}

3. Description Update¶

Improve or correct the time entry description:

{
  "timeEntryId": "te_abc123",
  "description": "Updated: Client meeting and project planning session"
}

4. Comprehensive Update¶

Change multiple fields simultaneously:

{
  "timeEntryId": "te_abc123",
  "startTime": "2025-10-14T14:00:00Z",
  "endTime": "2025-10-14T16:00:00Z", 
  "activityId": "proj_client_work_789",
  "description": "Extended client consultation and requirements gathering"
}

Behavior¶

Update Process¶

1. Entry Validation: Verifies the time entry exists and is accessible
2. Parameter Validation: Checks that at least one update field is provided
3. Authentication: Confirms API credentials with EARLY
4. Field Updates: Applies changes to specified fields only
5. API Synchronization: Updates the entry via EARLY API v4
6. Response Confirmation: Returns updated entry details

Field Update Logic¶

• Partial Updates: Only specified fields are modified
• Unchanged Fields: Non-specified fields retain their original values
• Time Validation: Start time must be before end time if both are updated
• Activity Validation: New activity ID must exist and be accessible

Time Entry Identification¶

To get time entry IDs for editing:

1. Use get_time_entries to list recent entries
2. Note the id field in the response
3. Use that ID in the timeEntryId parameter

Examples¶

Extend Meeting Duration¶

A meeting ran longer than originally logged:

{
  "timeEntryId": "te_meeting_123",
  "endTime": "2025-10-14T11:30:00Z"
}

Response:

Time entry updated successfully:

ID: te_meeting_123
Updated fields: endTime

Entry details:
{
  "id": "te_meeting_123",
  "activity": {
    "name": "Client Work",
    "id": "proj_client_456"
  },
  "duration": {
    "startedAt": "2025-10-14T10:00:00",
    "stoppedAt": "2025-10-14T11:30:00"
  },
  "note": {
    "text": "Weekly client check-in"
  }
}

Fix Incorrect Project Assignment¶

Time was logged to the wrong project:

{
  "timeEntryId": "te_wrongproject_456", 
  "activityId": "proj_correct_789",
  "description": "Development work - moved from wrong project"
}

Comprehensive Meeting Update¶

Update all details of a meeting entry:

{
  "timeEntryId": "te_meeting_789",
  "startTime": "2025-10-14T09:30:00Z",
  "endTime": "2025-10-14T11:00:00Z",
  "activityId": "proj_strategy_planning",
  "description": "Q4 strategy planning session with leadership team"
}

Adjust Start Time Only¶

Meeting started 15 minutes late:

{
  "timeEntryId": "te_standup_123",
  "startTime": "2025-10-14T09:15:00Z"
}

Common Use Cases¶

Time Corrections¶

• Meeting overruns: Extend end time when meetings run long
• Late starts: Adjust start time for delayed beginnings
• Break adjustments: Modify times to account for breaks

Project Management¶

• Task reassignment: Move time entries between projects
• Client billing: Ensure time is assigned to correct billable activities
• Category corrections: Fix misclassified time entries

Documentation Improvements¶

• Detail additions: Enhance descriptions with more context
• Clarity improvements: Make notes more specific for reporting
• Standardization: Align descriptions with team conventions

Error Scenarios¶

Common Errors and Solutions¶

Example Error Response¶

{
  "content": [{
    "type": "text",
    "text": "Operation failed: At least one field must be provided to update\n\nDebug info:\n- API Key: Present\n- API Secret: Present\n- Base URL: https://api.early.app\n\nProvided arguments: {\"timeEntryId\": \"te_123\"}"
  }]
}

Related Tools¶

Complementary Functionality¶

• get_time_entries - Get time entry IDs and current values
• create_time_entry - Create new entries instead of editing
• list_activities - Get valid activity IDs for reassignment
• start_timer / stop_timer - Real-time tracking alternative

Workflow Integration¶

graph LR
    A[get_time_entries] --> B[edit_time_entry]
    C[list_activities] --> B
    B --> D[get_time_entries]

    E[create_time_entry] -.-> A

Typical Editing Workflow: 1. get_time_entries → Find entries to modify 2. list_activities → Get valid activity IDs (if reassigning) 3. edit_time_entry → Apply updates 4. get_time_entries → Verify changes

Best Practices¶

Before Editing¶

• Always use get_time_entries to get current entry details
• Verify time entry IDs are correct and entries exist
• Check that new activity IDs are valid with list_activities

Time Modifications¶

• Ensure start time is before end time when updating both
• Consider time zone implications for timestamp updates
• Validate that time ranges don't create impossible durations

Batch Updates¶

• Edit entries individually rather than attempting bulk operations
• Maintain audit trail by updating descriptions to note changes
• Consider creating new entries instead of editing if changes are major

Error Prevention¶

• Always provide at least one field to update beyond timeEntryId
• Double-check activity IDs before reassigning time entries
• Use descriptive error messages to troubleshoot authentication issues