Time Doctor
ProductivityConnect AI agents to Time Doctor. Agents pull worklogs and application or website time-use reports over a date range, sync tracked time into billing and payroll systems, and create projects and discover user and task IDs for downstream automations.
What This Integration Enables
Time Doctor is where tracked hours accumulate, but hours are only useful when they reach the systems that bill clients and pay people. This connector exists for that hand-off. FlowRunner agents pull worklogs and application or website time-use reports over any date range, resolve the user, project, and task IDs that scope those reports, and create projects so the tracking structure keeps pace with the work being sold. The position this page takes: time data should move on a schedule, and a person should see it before it turns into money. Agents handle the pulling, reconciling, and formatting. Managers handle the judgment calls. - Sync worklogs into spreadsheets, timesheets, and billing systems for payroll and client invoicing - Reconcile tracked hours against expectations and route only the exceptions to a manager - Mirror new client projects into Time Doctor the moment work kicks off elsewhere - Pull application and website time-use breakdowns for scheduled productivity reporting - Resolve the user, project, and task IDs that scope every report, without a human looking them up
Without FlowRunner
With FlowRunner
Use Case Scenarios
The payroll timesheet that assembles itself
Every Friday, the agent calls Get Worklog for the closing week and appends each entry to the payroll sheet in [Google Sheets](/integrations/google-sheets): user, project, task, duration, timestamps. It totals per person, compares against contracted hours, and posts a summary to [Slack](/integrations/slack) with anyone under or over threshold called out. The operations manager reviews three exceptions instead of forty rows, corrects one, and the approved sheet feeds the payroll run. The export step nobody enjoyed no longer exists.
Projects that exist before the first hour is tracked
A new client engagement is created in the project tool, or a deal closes in the CRM. The agent calls Create Project in Time Doctor with the engagement name, so when the team starts work on Monday, the project is already there to track against. No more hours logged to "General" because the project was not set up yet, which means billing reports at month end actually match the engagements being billed.
The focus report that names patterns, not people, until a manager decides otherwise
On a schedule, Get Time Use pulls the application and website breakdown for the team. The agent aggregates it: which tools dominate the week, how much time lands in communication apps versus production work, how the mix shifted from last month. The aggregate posts to the leadership channel. Individual-level breakdowns are held back by design and released only when a manager explicitly asks for a named report, because [human-in-the-loop](/concepts/human-in-the-loop) applies to sensitive reads, not just risky writes.
Human-in-Loop Highlight
Get Worklog is a read, but its output is the number on a client's invoice and the amount in an employee's paycheck, and both of those are writes you cannot quietly take back. An invoice built on unreviewed worklogs reaches the client with the dispute already embedded in it; a payroll run on a mislogged week means clawing money back from a person. So FlowRunner agents in this connector never let tracked time flow straight into billing. The agent pulls the worklog, reconciles it against expected hours and active projects, and stops on anything anomalous: a 14-hour day, hours against a closed project, a week of silence from an active contributor. The manager rules on the exceptions, and only the approved timesheet moves downstream. The reconciliation runs at machine speed. The number that reaches the client has a human signature on it.
Agent Capabilities
8 actionsUsers
2- List Users Lists users in the configured Time Doctor company with id, name, email, role, and status. Supports text filtering and pagination. The discovery step behind every per-user report.
- Get User Retrieves a single user's full profile by ID, including timezone and tag assignments. Used to scope reports and resolve who a worklog entry belongs to.
Projects
2- List Projects Lists the company's projects with id, name, and status. Projects group tasks and time entries, so this is the map billing reconciliation runs against.
- Create Project Creates a new project by name. Used to mirror engagements from CRMs and project tools so tracking structure exists before the first hour is logged.
Tasks
1- List Tasks Lists tasks with id, name, and parent project, optionally filtered to a single project. Tasks are the granular items users track time against.
Reports
2- Get Worklog Retrieves tracked time segments for the company within a required date range, each with user, duration, project, task, and timestamps. Optionally scoped to one user. The action this connector's billing workflows are built on.
- Get Time Use Retrieves time-use statistics for a required date range, breaking tracked time down by application and website usage. Optionally scoped to one user. Sensitive by nature; aggregate first, name individuals only on explicit request.
Companies
1- List Companies Lists every Time Doctor company the configured token can access, with id and name. Run first to discover the Company ID the rest of the configuration needs.
Frequently Asked Questions
What can FlowRunner do with Time Doctor?
FlowRunner agents can run List Users, Get User, and List Projects in Time Doctor, plus 5 more actions.
Does connecting Time Doctor to FlowRunner require OAuth?
No. Time Doctor connects to FlowRunner with an API key, no OAuth flow required.
Can Time Doctor trigger a FlowRunner workflow automatically?
Time Doctor doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Time Doctor
$100 in credits. No card required. Connect in minutes.