Employee Time Tracker with AI Reports

Time Tracking Automation Agent Setup Guide

What This Agent Does

This comprehensive Time Tracking Automation Agent streamlines employee time management by automating clock-in/out logging, break tracking, and generating intelligent time reports. The workflow captures real-time attendance data via webhooks, maintains accurate records in a spreadsheet, sends daily reminders to employees who haven't clocked in, and delivers monthly summaries to management—all without manual intervention.

Key benefits include:

• Eliminates manual time entry by automating clock-in/out and break logging
• Saves 5+ hours monthly on administrative time tracking tasks
• Reduces errors with AI-powered status analysis and automated reminders
• Improves accountability through daily reminders and comprehensive monthly reports
• Provides actionable insights with AI-generated summaries for management decision-making

Ideal for: HR departments, remote team management, freelance operations, and organizations requiring precise attendance tracking and compliance reporting.

Who Is It For

This agent is designed for:

• HR Managers who need to track employee attendance without manual data entry
• Team Leads managing distributed or remote teams
• Payroll Administrators requiring accurate time records for compensation
• Compliance Officers needing audit trails and monthly summaries
• Organizations of any size seeking to automate time tracking workflows

Required Integrations

Spreadsheet Integration

Why it's needed: The spreadsheet serves as your centralized database for storing all time tracking records, including clock-in times, clock-out times, break durations, and historical data for analysis.

Setup steps:

1. Choose your spreadsheet platform (Google Sheets, Microsoft Excel Online, or Airtable)

2. Create a new spreadsheet with the following columns:

   • Employee_ID (unique identifier)
   • Employee_Name (full name)
   • Date (YYYY-MM-DD format)
   • Clock_In_Time (HH:MM:SS format)
   • Clock_Out_Time (HH:MM:SS format)
   • Break_Duration_Minutes (numeric value)
   • Total_Hours_Worked (calculated field)
   • Status (Active/Inactive)

3. Share the spreadsheet with your TaskAGI service account email

4. Copy the spreadsheet ID from the URL (appears between /d/ and /edit)

5. Note the sheet name (default is "Sheet1")

How to obtain credentials:

• For Google Sheets: Use your Google account; TaskAGI will request permission to access your sheets
• For Excel Online: Use your Microsoft 365 account credentials
• For Airtable: Generate an API token from your account settings

Configuration in TaskAGI:

• Navigate to Integrations → Spreadsheet
• Select your platform and authenticate
• Enter the spreadsheet ID and sheet name
• Test the connection by clicking Verify Connection

OpenAI Integration

Why it's needed: OpenAI's GPT-4 model powers intelligent analysis of time tracking data, generating personalized reminder messages and comprehensive monthly summaries that identify patterns and provide actionable insights.

Setup steps:

1. Create an OpenAI account at platform.openai.com
2. Navigate to API Keys in your account settings
3. Click "Create new secret key" and copy the generated key immediately
4. Store the key securely (you won't be able to view it again)
5. Set up billing in your OpenAI account to enable API usage
6. Choose your model: This workflow uses gpt-4o for superior analysis quality

How to obtain API keys:

• Log into your OpenAI account
• Go to Settings → API Keys
• Click + Create new secret key
• Name it descriptively (e.g., "TaskAGI Time Tracking")
• Copy and save immediately

Configuration in TaskAGI:

• Go to Integrations → OpenAI
• Paste your API key in the authentication field
• Select model: gpt-4o
• Set temperature to 0.7 for balanced creativity and consistency
• Test by clicking Send Test Request

Gmail Integration

Why it's needed: Gmail delivers automated daily clock-in reminders to employees and sends monthly time tracking summaries to management, ensuring stakeholders stay informed without manual email composition.

Setup steps:

1. Use your Gmail account (personal or organizational)
2. Enable 2-Factor Authentication (required for API access)
3. Generate an App Password:
   • Go to myaccount.google.com → Security
   • Find "App passwords" (only visible with 2FA enabled)
   • Select "Mail" and "Windows Computer"
   • Google generates a 16-character password
4. Copy the App Password (not your regular password)
5. Configure in TaskAGI:
   • Go to Integrations → Gmail
   • Enter your full Gmail address
   • Paste the App Password (not your regular password)
   • Click Authenticate

How to obtain credentials:

• Gmail Address: Your full email (e.g., hr@company.com)
• App Password: Generated through Google Account Security settings
• Never use your regular password with TaskAGI

Configuration in TaskAGI:

• Verify the sender email address matches your Gmail
• Test by sending a test email to yourself
• Confirm delivery before deploying the workflow

Configuration Steps

Phase 1: Webhook Setup (Clock-In/Out Trigger)

Node 4: Track Time Webhook

• This is your entry point for time tracking requests
• Webhook URL will be generated automatically once you save the workflow
• Method: Accepts POST requests
• Expected payload structure:

{
  "employee_id": "EMP001",
  "employee_name": "John Doe",
  "action": "clock_in|break_start|break_end|clock_out",
  "timestamp": "2024-01-15T09:00:00Z"
}

Node 5: Route by Method

• Directs requests to appropriate processing path based on action value
• Case 0: clock_in → Insert Start Time
• Case 1: break_start → Query Today's Record (Break)
• Case 2: clock_out → Query Today's Record (End)

Phase 2: Clock-In Processing

Node 6: Insert Start Time

• Spreadsheet: Select your configured spreadsheet
• Sheet: Select the sheet containing time records
• Data to insert:
  • Employee_ID: [[nodes.4.employee_id]]
  • Employee_Name: [[nodes.4.employee_name]]
  • Date: [[nodes.4.timestamp]] (extract date portion)
  • Clock_In_Time: [[nodes.4.timestamp]] (extract time portion)

Node 7: Start Recorded Message

• Message content: "✓ Clock-in recorded for [[nodes.4.employee_name]] at [[nodes.4.timestamp]]"
• This confirms successful entry to the webhook caller

Phase 3: Break Tracking

Node 8: Query Today's Record (Break)

• Query: Find today's entry for the employee
• Filter: Date = TODAY() AND Employee_ID = [[nodes.4.employee_id]]
• Purpose: Retrieve existing record to update with break information

Node 9: Check Today's Entry (Break)

• Condition: IF record_found == true
• True path: Proceed to set break duration
• False path: Send error message (employee hasn't clocked in)

Node 10: Set Break Duration

• Calculate: Time between break_start and break_end
• Formula: break_end_time - break_start_time
• Store in: Break_Duration_Minutes field

Node 11: Update Break Time

• Action: UPSERT (update if exists, insert if not)
• Update fields: Break_Duration_Minutes, Last_Updated
• Match on: Employee_ID and Date

Node 12: Break Recorded Message

• Message: "✓ Break logged: [[nodes.10.duration]] minutes"

Node 13: Break Error Message

• Message: "✗ Error: No clock-in found for today. Please clock in first."

Phase 4: Clock-Out Processing

Node 14: Query Today's Record (End)

• Query: Retrieve today's complete record
• Filter: Date = TODAY() AND Employee_ID = [[nodes.4.employee_id]]

Node 15: Check Today's Entry (End)

• Condition: IF record_found == true
• Validates: Employee has clocked in before attempting clock-out

Node 16: Set End Time

• Field: Clock_Out_Time
• Value: [[nodes.4.timestamp]]
• Calculate: Total_Hours_Worked = (Clock_Out_Time - Clock_In_Time - Break_Duration) / 60

Node 17: Update End Time

• Action: UPSERT
• Fields: Clock_Out_Time, Total_Hours_Worked, Status
• Set Status: "Completed" when clock-out recorded

Node 18: End Recorded Message

• Message: "✓ Clock-out recorded. Total hours: [[nodes.16.total_hours]]"

Node 19: End Error Message

• Message: "✗ Error: No active clock-in session found."

Node 20: Respond to Webhook

• Response body: Combines all possible messages from the workflow
• HTTP Status: 200 (success) or 400 (error)
• Returns: Confirmation message to the calling system

Phase 5: Daily Reminder Flow

Node 22: Every Day at 10 AM

• Trigger type: Schedule (recurring)
• Time: 10:00 AM in your timezone
• Frequency: Daily
• Timezone: Set to your organization's primary timezone

Node 23: Get All Time Entries

• Query: Retrieve all records from today
• Filter: Date = TODAY()
• Purpose: Identify employees who haven't clocked in

Node 24: Analyze Clock-In Status

• Model: gpt-4o
• Prompt:

Analyze these time entries from today. Identify employees who haven't clocked in yet. 
Generate a personalized, friendly reminder message for each employee.
Format: "Hi [Name], just a reminder to clock in for today!"

• Temperature: 0.7 (balanced tone)

Node 25: Email to Employee

• To: [[nodes.23.employee_email]]
• Subject: "SCHEDULE - Clock-In Reminder"
• Body: [[nodes.24.content]]
• Send time: Automatically at 10 AM daily

Phase 6: Monthly Summary Flow

Node 27: Every Month

• Trigger type: Schedule (recurring)
• Frequency: Monthly
• Day: First day of month at 9:00 AM
• Timezone: Your organization's timezone

Node 28: Get Monthly Data

• Query: Retrieve all records from previous month
• Filter: Date >= FIRST_DAY_LAST_MONTH AND Date <= LAST_DAY_LAST_MONTH
• Include: All employees, hours worked, breaks, attendance patterns

Node 29: Analyze Monthly Summary

• Model: gpt-4o
• Prompt:

Analyze the time tracking data for last month. Provide:
1. Total hours per employee
2. Attendance rate percentage
3. Patterns or anomalies
4. Recommendations for management
Format as a professional executive summary.

• Temperature: 0.5 (more formal, consistent)

Node 30: Email to Management

• To: [[management_email_list]]
• Subject: "SCHEDULE - Monthly Time Tracking Summary"
• Body: [[nodes.29.content]]
• CC: HR department
• Attachment: Optional CSV export of raw data

Testing Your Agent

Test 1: Clock-In Functionality

Steps:

1. Obtain your webhook URL: Save the workflow and copy the webhook URL from Node 4
2. Send a test clock-in request using Postman or curl:

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "TEST001",
    "employee_name": "Test Employee",
    "action": "clock_in",
    "timestamp": "2024-01-15T09:00:00Z"
  }'

What to verify:

• ✓ Webhook returns 200 status code
• ✓ Confirmation message appears in response
• ✓ New row appears in spreadsheet with clock-in time
• ✓ Clock_In_Time field populated correctly

Expected result: "✓ Clock-in recorded for Test Employee at 2024-01-15T09:00:00Z"

Test 2: Break Tracking

Steps:

1. Send break_start request:

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "TEST001",
    "employee_name": "Test Employee",
    "action": "break_start",
    "timestamp": "2024-01-15T12:00:00Z"
  }'

2. Send break_end request (30 minutes later):

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "TEST001",
    "employee_name": "Test Employee",
    "action": "break_end",
    "timestamp": "2024-01-15T12:30:00Z"
  }'

What to verify:

• ✓ Break duration calculated as 30 minutes
• ✓ Break_Duration_Minutes field updated in spreadsheet
• ✓ Confirmation message received for both actions
• ✓ No error messages appear

Expected result: "✓ Break logged: 30 minutes"

Test 3: Clock-Out Functionality

Steps:

1. Send clock-out request:

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "TEST001",
    "employee_name": "Test Employee",
    "action": "clock_out",
    "timestamp": "2024-01-15T17:00:00Z"
  }'

What to verify:

• ✓ Clock_Out_Time recorded correctly
• ✓ Total_Hours_Worked calculated (8 hours - 0.5 break = 7.5 hours)
• ✓ Record status changed to "Completed"
• ✓ Confirmation message includes total hours

Expected result: "✓ Clock-out recorded. Total hours: 7.5"

Test 4: Error Handling

Steps:

1. Send clock-out without clock-in:

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "INVALID001",
    "employee_name": "Invalid Employee",
    "action": "clock_out",
    "timestamp": "2024-01-15T17:00:00Z"
  }'

What to verify:

• ✓ Workflow returns error message
• ✓ No erroneous data added to spreadsheet
• ✓ Error message is user-friendly and actionable

Expected result: `"✗ Error: No active clock-in