Start free
ActionTimeCampUpdated June 2026

How do I pull TimeCamp entries for a date range?

Short answer: You can list time entries in TimeCamp by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the TimeCamp List Time Entries action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Time Entries in TimeCamp — start free All 2 TimeCamp actions
List Time Entries in TimeCamp — start free
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
From (YYYY-MM-DD)
from
stringRequired–
To (YYYY-MM-DD)
to
stringRequired–
Sample request
{
  "from": "{{trigger.from}}",
  "to": "{{trigger.to}}"
}
Returns
[
  {
    "id": "e_abc",
    "date": "2026-05-11",
    "task_id": 99,
    "duration": 3600,
    "description": "Built feature"
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Time Entries.

Any of these apps can fire this action as part of a workflow.

Gmail → TimeCamp
1 Gmail triggers
Slack → TimeCamp
13 Slack triggers
Google Sheets → TimeCamp
2 Google Sheets triggers
HubSpot → TimeCamp
18 HubSpot triggers
FAQ

Questions about List Time Entries.

What does the List Time Entries action do in TimeCamp?
Lists TimeCamp time entries between two dates, scoped to the connected user or the whole team. Used for invoicing, reporting, and timesheet exports.
What inputs does List Time Entries require?
Required: From (YYYY-MM-DD), To (YYYY-MM-DD). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if TimeCamp returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does List Time Entries support batch operations?
Yes. Run List Time Entries inside a Loop node to process arrays. TinyCommand handles TimeCamp's rate limits automatically so you don't have to throttle manually.
More actions

Other TimeCamp actions.

Action
Create Time Entry
Logs a time entry in TimeCamp against a task with a start/end (or duration) and optional note. Use it to convert calendar events or external tickets into billable time automatically.
List Time Entries in TimeCamp — start free