Skip to main content

Overview

The fallback endpoint provides sample task data for Zapier trigger testing and configuration. When setting up a “New Task” trigger, Zapier uses this endpoint to show users the expected data structure, making it easier to configure workflows before activating live webhook subscriptions.
This endpoint intelligently returns your most recent task data when available, or consistent sample data for testing when your workspace has no tasks yet.

Authentication

All requests require a valid API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY

Get Sample Data

curl -X GET 'https://app.timetracker.in/api/integrations/zapier/triggers/tasks/fallback' \
  -H 'Authorization: Bearer YOUR_API_KEY'

Response

Success Response

Returns an array containing one task object - either your most recent task or sample data:
[
  {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "name": "Implement user authentication",
    "description": "Add user authentication system to the mobile app",
    "project": {
      "id": "456e7890-e89b-12d3-a456-426614174001",
      "name": "Mobile App Development"
    },
    "client": {
      "id": "789e0123-e89b-12d3-a456-426614174002",
      "name": "Acme Corporation",
      "email": "[email protected]",
      "phone": "+1-555-0123",
      "status": "active",
      "type": "enterprise"
    },
    "workspace": {
      "id": "abc12345-e89b-12d3-a456-426614174003",
      "name": "Development Team"
    },
    "teamMembers": [
      {
        "id": "def67890-e89b-12d3-a456-426614174004",
        "name": "John Doe",
        "email": "[email protected]",
        "avatar": "https://example.com/avatar.jpg",
        "designation": "Senior Developer",
        "department": "Engineering",
        "status": "active",
        "role": {
          "id": "ghi11111-e89b-12d3-a456-426614174005",
          "name": "Developer",
          "description": "Software development role"
        },
        "billableRate": 75.0,
        "currency": "USD"
      }
    ],
    "status": "todo",
    "priority": "high",
    "estimatedHours": 16.0,
    "dueDate": "2024-01-25T23:59:59.000Z",
    "createdAt": "2024-01-15T10:00:00.000Z",
    "updatedAt": "2024-01-15T10:00:00.000Z"
  }
]

Data Fields

id
string
Unique task identifier (UUID format)
name
string
Task name
description
string
Task description
project
object
Associated project information
client
object
Associated client information
workspace
object
Associated workspace information
teamMembers
array
Array of team members assigned to the task
status
string
Current task status
  • todo - Task is pending
  • in_progress - Task is currently being worked on
  • completed - Task has been completed
  • cancelled - Task has been cancelled
priority
string
Task priority level
  • low - Low priority
  • medium - Medium priority
  • high - High priority
  • urgent - Urgent priority
estimatedHours
number
Estimated hours to complete the task
dueDate
string
Task due date in ISO 8601 format
createdAt
string
ISO 8601 timestamp when task was created
updatedAt
string
ISO 8601 timestamp when task was last modified

Error Responses

{
  "error": "Unauthorized"
}
Cause: Invalid or missing API key
Solution: Verify your API key is correct and properly formatted
{
  "error": "Failed to fetch tasks"
}
Cause: Server-side error during data retrieval
Solution: Retry the request or contact support if the issue persists

Sample Data Format

When your workspace has no tasks, you’ll receive this consistent sample data:
{
  "id": "123e4567-e89b-12d3-a456-426614174000",
  "name": "Sample Task Implementation",
  "description": "Add sample functionality to the application",
  "project": {
    "id": "456e7890-e89b-12d3-a456-426614174001",
    "name": "Sample Project"
  },
  "client": {
    "id": "789e0123-e89b-12d3-a456-426614174002",
    "name": "Sample Client",
    "email": "[email protected]",
    "phone": "+1-555-0123",
    "status": "active",
    "type": "company"
  },
  "workspace": {
    "id": "abc12345-e89b-12d3-a456-426614174003",
    "name": "Sample Workspace"
  },
  "teamMembers": [
    {
      "id": "def67890-e89b-12d3-a456-426614174004",
      "name": "Sample Developer",
      "email": "[email protected]",
      "avatar": "https://example.com/avatar.jpg",
      "designation": "Developer",
      "department": "Engineering",
      "status": "active",
      "role": {
        "id": "ghi11111-e89b-12d3-a456-426614174005",
        "name": "Developer",
        "description": "Software development role"
      },
      "billableRate": 75.0,
      "currency": "USD"
    }
  ],
  "status": "todo",
  "priority": "medium",
  "estimatedHours": 8.0,
  "dueDate": "2024-01-25T23:59:59.000Z",
  "createdAt": "2024-01-15T10:00:00.000Z",
  "updatedAt": "2024-01-15T10:00:00.000Z"
}

Zapier Integration Workflow

How Zapier Uses This Endpoint

1

Trigger Configuration

When you set up a “New Task” trigger in Zapier, it automatically calls this endpoint to fetch sample data.
2

Data Structure Display

Zapier shows you the returned task data structure, including all available fields and their formats.
3

Field Mapping Setup

You can map specific task fields (like name, description, project.name, client.name) to actions in your workflow.
4

Testing & Validation

Use the sample data to test your workflow logic before activating live webhook notifications.
5

Production Activation

Once configured, Zapier switches to receiving real-time data via webhook subscriptions.
Pro Tip: The data structure shown during setup matches exactly what you’ll receive in live webhook payloads, so you can confidently design your workflows around the sample data.

Use Cases

Primary Use: Zapier automatically calls this endpoint when users configure “New Task” triggers to show them what data will be available.
Development Use: Test your integration logic with consistent, predictable data structures before connecting to live task creation events.
Reference Use: Use the returned data structure to document what fields are available in your task management workflows.
Testing Use: Validate that your automation workflows can handle all the task data fields before going live.

Important Notes

Data Consistency Guarantee: The structure returned by this endpoint exactly matches the webhook payload format, ensuring seamless transition from testing to production.
Workspace Isolation: Only returns real task data from your authenticated workspace. Cross-workspace data access is prevented for security.
Integration Best Practices:
  • Always test your workflows with this sample data first
  • The endpoint returns an array, so access the first element: data[0]
  • All dates use ISO 8601 format for consistent parsing
  • Task IDs are always UUIDs for reliable identification
  • Team member arrays may be empty for tasks with no assigned members
  • Priority and status fields use predefined values
  • Estimated hours use decimal numbers for precision

Testing Your Integration

To test how your application handles task data:
  1. Call the endpoint with your API credentials
  2. Parse the response and extract the first task object
  3. Validate data types match your expected formats
  4. Test field mapping for your specific use case
  5. Handle edge cases like missing optional fields or empty arrays
This ensures your integration works smoothly when real task data starts flowing through webhooks.