Everhour
ProductivityTrack time in Everhour from your flows. Agents create tasks in the right project, log time when work completes elsewhere, start and stop live timers, and pull team wide time records for a date range to feed reporting, billing, or payroll.
What This Integration Enables
Time tracking fails socially, not technically: the people doing the work have better things to do than describe it in a second tool. Everhour's API lets FlowRunner remove the social problem. When work completes in the delivery tool, agents mirror the task into the right project, log the duration in seconds against it, and attribute it to the right person. Live timers start and stop from workflow events. And because the records are complete and structured, the month-end pull for billing and payroll becomes an aggregation problem instead of an archaeology project. - Create tasks in the right project and section as work items arrive from other tools - Log fixed durations against tasks, dated, attributed, and commented, with time always in seconds - Start and stop live timers from workflow events, so tracked time follows actual work - Pull team-wide time records for any date range to feed reporting, billing, and payroll - Resolve projects, tasks, and team members to the IDs every other step needs - Read billing rates and budgets per project for reconciliation before invoicing
Without FlowRunner
With FlowRunner
Use Case Scenarios
Delivery work that tracks itself
New work items land in [Asana](/integrations/asana). The agent mirrors each into the matching Everhour project with Create Task, placed in the right section. When an item completes, Add Time logs the effort against the mirrored task with a comment linking back to the source. The engineers never open Everhour, the project's tracked totals stay current, and the budget view in Get Project reflects reality instead of whoever remembered to log.
From tracked seconds to a client invoice
At month end, the agent runs List Team Time for the client project's date range, aggregates the records by task, and converts durations to billable hours against the project's rate. The draft, hours, amounts, and flagged exceptions, goes to the finance owner for review. On approval, the invoice is created in [QuickBooks Online](/integrations/quickbooks) and the backing detail archives to [Google Sheets](/integrations/google-sheets). The client gets an invoice whose every line traces to a named task, a person, and a date, which is also exactly what makes rate disputes short.
The payroll export nobody assembles by hand
Every other Friday, the agent pulls List Team Time for the pay period and List Team Users for roles and cost rates, then builds the per-person timesheet: total hours, project breakdown, and anomalies like fourteen-hour days or zero-hour weeks flagged for a check-in rather than silently processed. The reviewed export feeds payroll, and the anomaly flags occasionally catch something more important than a typo: a burnout pattern the numbers saw first.
Human-in-Loop Highlight
Add Time is a financial write wearing a productivity costume. A record attributed to a teammate on a billable project becomes, a few steps downstream, a line on a client invoice and an input to payroll, and this connector lets an agent write those records for any user by ID. The failure mode is quiet: a duration mapped from the wrong field, milliseconds where seconds belonged, or hours attributed to the wrong person do not error, they just become money. So FlowRunner draws the gate at the point where time becomes billing: bulk Add Time runs attributed to other users, and any month-end total bound for an invoice, stop for the finance owner's review with the reconciliation attached. "Retainer project as:482913: 61.5 hours across 4 people, budget 60, two records missing comments. Approve for invoicing?" The person resolves the overage before the client ever sees it. Logging time is cheap to correct. Un-invoicing a client is not.
Agent Capabilities
11 actionsProjects
2- List Projects Lists projects visible to the authenticated account, filterable by name search, returning each project's ID, name, workspace, status, and billing and budget details. The starting point that resolves the project IDs every other step needs.
- Get Project Retrieves a single project's full details by ID, including name, workspace, status, billing rate, budget, and user assignments. The reconciliation source before invoicing.
Tasks
2- List Tasks Lists a project's tasks with each task's ID, name, section, completion status, and tracked-time totals. The lookup behind time attribution and progress reporting.
- Create Task Creates a new task inside a project, optionally placed under one or more sections, returning the generated task ID for use with Add Time and Start Timer. The mirroring step that keeps Everhour aligned with the delivery tool.
Time
2- Add Time Adds a logged time record to a task, with the duration in seconds, an optional date, user attribution, and a comment. The financial write this page's human gate reviews when it feeds billing.
- List Team Time Retrieves logged time records across the whole team for a required From and To date range, each with user, task, date, duration in seconds, and comment. The engine behind billing, payroll, and reporting pulls.
Timers
3- Get Current Timer Returns the authenticated user's currently running timer with the tracked task, start time, and elapsed seconds, or a stopped status. The state check before timer operations.
- Start Timer Starts a live timer on a specified task for the authenticated user, stopping any timer already running, with an optional comment. The live-tracking path when work starts from a workflow event.
- Stop Timer Stops the authenticated user's running timer and returns the resulting time record with total tracked seconds. The closing step that turns a session into a record.
Users
2- List Team Users Lists all team members with ID, name, email, role, status, and default billing and cost rates. The attribution and payroll-rate source.
- Get Current User Returns the authenticated user's profile, ID, name, email, role, and workspace context. The credentials check that also identifies who automated time will be logged as.
Frequently Asked Questions
What can FlowRunner do with Everhour?
FlowRunner agents can run List Projects, Get Project, and List Tasks in Everhour, plus 8 more actions.
Does connecting Everhour to FlowRunner require OAuth?
No. Everhour connects to FlowRunner with an API key, no OAuth flow required.
Can Everhour trigger a FlowRunner workflow automatically?
Everhour doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Everhour
$100 in credits. No card required. Connect in minutes.