FlowRunner
PricingContact
Theme
Start Free

TimeCamp

Productivity

Connect AI agents to TimeCamp. Agents read and write time entries across a date range, build timesheets filtered by user, keep the project and task hierarchy in sync, and start or stop the live timer from event-driven flows.

10 actions API key available
TimeCamp website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
The weekly billing run starts Monday morning for the prior week
List Time Entries pulls the week's entries across the team, and List Users maps entries to people
The agent flags anomalies: entries with no task, durations over twelve hours, days with zero tracked time for active projects
Clean entries aggregate by client and project into the draft timesheet
The operations lead reviews the flagged entries with their owners and approves corrections before anything reaches an invoice
Approved corrections apply through Update Time Entry, and the finalized totals flow to the invoicing system
The billing summary posts to the finance channel with hours by client and the corrections log

What This Integration Enables

Tracked time is the raw material of every services invoice and most payroll, and its quality is set by how it gets captured, corrected, and reported. FlowRunner agents work all three stages. Capture: entries are created from the systems that actually witnessed the work, calendars, tickets, deploy logs, with durations in seconds and notes attached. Correction: updates and deletions are structured, evidenced, and gated. Reporting: entries flow into timesheets, payroll sheets, and per-client billing on schedule. The live timer rounds it out, started and stopped by event-driven flows so real-time tracking survives contact with a busy day. - Build timesheets and reports by pulling entries across any date range, filtered by user - Log completed meetings and finished work as entries automatically, against the right task - Keep the project and task hierarchy synced with the project tool via List Tasks and Create Task - Drive the live timer from events: start on the shift ticket, stop at the handoff - Route every correction and deletion of logged time through a human

Without FlowRunner

Timesheet Friday The week ends with everyone reconstructing where their hours went, from memory, under deadline
Untracked meetings Half the calendar never reaches the timesheet, and the client pays for a fraction of the attention they got
Corrections at invoice time Bad entries surface when the client questions the invoice, which is the most expensive moment to find them

With FlowRunner

Time logs itself from the systems that saw it Completed meetings and events become entries with durations, tasks, and notes, created as they happen
The hierarchy stays synced Projects and tasks mirror the project tool, so entries always have a valid home to land in
Anomalies caught Monday, not month-end The billing sweep flags the suspect entries and a person settles them days before an invoice exists

Use Case Scenarios

The calendar that files its own timesheet

Each evening, an agent reads completed events from [Google Calendar](/integrations/google-calendar), converts durations to seconds, resolves each meeting to its project task, and writes entries with Create Time Entry, meeting title in the note. Client calls stop leaking out of the billable record, and the consultant's Friday reconstruction ritual disappears because the week already filed itself.

Hours to invoice without the export step

On the first of the month, the agent pulls the prior month's entries with List Time Entries, aggregates by client through the task hierarchy, and drafts per-client invoices in [QuickBooks Online](/integrations/quickbooks) with a line per project. The draft invoices and the underlying hours post to [Slack](/integrations/slack) for the operations lead's approval before anything sends. Billing lag drops from weeks to a morning.

The timer that follows the on-call shift

When an engineer picks up an incident ticket, the workflow calls Get Timer Status, then Start Timer against the incident task; when the ticket resolves, Stop Timer finalizes the entry. Incident response time, historically the least-tracked and most-argued-about category, becomes a clean record nobody had to remember to keep, feeding both the client report and the on-call load review.

Human-in-Loop Highlight

Delete Time Entry permanently erases a block of tracked time, and in this connector that is not housekeeping, it is destroying a billing record. An entry feeds an invoice, a payroll calculation, or a utilization number, and once deleted it cannot be restored: the hours are simply gone from every report that would have counted them, with nothing left to flag the absence. A dedup routine with a loose matching rule, two real half-day entries on the same task read as one duplicate, deletes revenue. So FlowRunner agents never delete tracked time on their own conclusion. The workflow presents the entry's full detail, owner, task, duration, date, note, alongside the reason it looks wrong, and the operations lead confirms each deletion individually. Update Time Entry passes the same review when the change touches duration or task on an already-invoiced period, because editing billed history is a decision with an audit trail, not a data cleanup.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

10 actions

Time Entries

4
  • List Time Entries Retrieves entries within a start and end date, optionally filtered by user IDs, with each entry's duration in seconds, task, note, and start and end times. The backbone of timesheets, billing runs, and audits.
  • Create Time Entry Creates a completed block of tracked time with duration in seconds, an associated task, a note, and optional explicit start and end times. The capture operation for after-the-fact logging and imports.
  • Update Time Entry Updates an entry by ID, changing only the provided fields: duration, task, note, date, or times. Corrections on invoiced periods pass this page's review gate.
  • Delete Time Entry Permanently deletes an entry by ID, with no undo. The operation this page's human gate exists for.

Tasks and Projects

2
  • List Tasks Retrieves the account's tasks and projects, a hierarchy linked via parent_id, normalized into an array for iteration. The mapping layer that gives every entry a valid home.
  • Create Task Creates a task or project, optionally nested under a parent, returning the ID used when logging time. The sync operation that mirrors the project tool's structure.

Users

1
  • List Users Retrieves all account users with ID, display name, email, and role. The resolution step for per-person timesheets and entry attribution.

Live Timer

3
  • Get Timer Status Returns the authenticated user's current timer state: whether one is running, against which task, the entry ID, and elapsed time. The check that runs before any start or stop.
  • Start Timer Starts the live timer against a specific task; starting a new timer typically stops the previous entry first, which is why the status check precedes it.
  • Stop Timer Stops the running timer and finalizes its entry. The bookend that event-driven flows call at handoff, resolution, or shift end.

Frequently Asked Questions

What can FlowRunner do with TimeCamp?

FlowRunner agents can run List Time Entries, Create Time Entry, and Update Time Entry in TimeCamp, plus 7 more actions.

Does connecting TimeCamp to FlowRunner require OAuth?

No. TimeCamp connects to FlowRunner with an API key, no OAuth flow required.

Can TimeCamp trigger a FlowRunner workflow automatically?

TimeCamp doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with TimeCamp

$100 in credits. No card required. Connect in minutes.