Timely

Timely is the automatic time tracking platform. Agents create and import time entries, control the running timer, manage projects, clients, tags, and planned tasks, approve and lock time for billing, pull reports, and react to time entry events in real time.

Verified 1 trigger 72 actions OAuth available

Timely website Platform Documentation Capability data verified 2026-08-24

The month closes and the timesheet review window opens on a schedule

Filter Reports returns the rows behind the period, grouped the way the reporting screen groups them

Get Compliance Metrics and List Capacities show who is short of the hours they were expected to log

The agent separates genuinely missing time from time that was logged against the wrong project

Each person with a gap receives their own rows and the specific days that are unaccounted for

Corrections that come back inside the window are written with Update Time Entry

The finance owner reviews what is still unresolved and authorizes Lock Days for the period

What This Integration Enables

Timely records what happened rather than what somebody remembered, capturing activity in the background and turning it into time entries. What makes it an interesting system to automate is not the capture, though: it is that Timely's API is built around an approval state machine. A state carries two flags that mean something specific. Billed means the entries count as invoiced. Locked means the entries cannot be edited by anyone, including the person who logged them. Set State Permissions decides who may move an entry between states, and without it the states are only colors.

So a FlowRunner agent working in Timely is working inside a controlled ledger, not a scratchpad. Agents create and correct time entries, drive the running timer, run both bulk import routes, keep projects, clients, tags and planned tasks in step with the systems that own them, and read the compliance and capacity numbers that say who is behind. The operations that close a period are treated differently from the ones that fill it, which is where FlowRunner's human-in-the-loop design does its work: the agent assembles the case for closing, and a person closes.

Without FlowRunner

Chasing timesheets by hand The week before close goes on reminders, spreadsheets and follow-up messages

Gaps found after the numbers ship A missing day surfaces when a client queries an invoice, not before it is sent

Periods closed on trust Nobody is certain a closed month is actually closed to edits

With FlowRunner

Gaps chased automatically Each person is asked about their own missing days, with the days named

Exceptions arrive before close What is still unaccounted for is a short reviewed list, not a discovery

Closing is a decided act Locking a period is a call somebody makes on the evidence, and the lock is real

Use Case Scenarios

The period closes with the gaps already chased

Toward the end of the month the agent runs Filter Reports for the period and reads Get Compliance Metrics and List Capacities to find who is short of their expected hours. Instead of one message to a channel, each person gets their own list: the days with no time on them, and the days where the total sits well under capacity. Replies that name a project become Create Time Entry or Update Time Entry calls. What is still open by the deadline goes to the finance owner as a short list with names, days and amounts, which is the evidence behind the lock decision rather than a summary of it.
Two systems, one truth about a project

When a project is opened in the CRM or the delivery board, the agent calls Create Project in Timely and Create Client if the client does not exist yet, so time can be logged against it from the first day. Rate and budget changes flow the same way through Update Project. When the engagement closes, the agent stops using Delete Project and switches the project to non-billable instead, because the history matters more than the tidiness. Totals from Get Report Totals, which returns hours, cost and revenue for a period, reconcile against the invoice lines in Xero or QuickBooks Online, and a discrepancy posts to Slack with the project and the delta named.
Automatic capture becomes reviewable time

Timely offers two bulk import routes that are easy to confuse and are not the same thing. Bulk Import Time Entries writes logged time. Bulk Import Events feeds Timely's memory side, the automatic tracking stream its suggestions are built from. An agent pulling raw activity out of another system, a support desk, a build pipeline, a phone log, should use the second one, so the material arrives as suggestions a person turns into time rather than as time nobody chose to log. The same discipline applies to planned work: Create Task sets an estimate over a date range, and Get Task Summaries is the planned-against-actual read behind an honest "are we on plan" answer.

Human-in-Loop Highlight

Lock Days closes a period, and Timely means it. A locked day refuses every time edit for the named users, including their own corrections to their own entries, and turning Locked on for a state applies to every entry already sitting in it. That is the point of the operation. It is also why an agent must never call it on a schedule. So the closing flow stops one step short: it posts to the finance owner "October is ready to lock for 24 people. Two are still unresolved: J. Okafor has 6 hours with no project on the 14th and 15th, and the Northwind retainer is 11 hours over its estimate with no note. Lock October now, lock everyone except those two, or hold?" The owner answers, and the agent calls Lock Days with exactly the scope it was given. Reopening is possible by passing Locked off, but by then the numbers have usually left the building, which is the whole reason the decision is worth a person's attention rather than a cron expression.

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

72 actions

Account and People

Get Current User Returns the person the token belongs to along with the accounts it can reach, so a flow can discover its own account rather than having it hard coded.
List Users Lists the people in the account.
Search Users Finds people by search term rather than paging the full list.
Get User Returns one person's profile.
Invite User Invites somebody into the account.
Update User Changes a person's details or role in the account.
Delete User Removes a person from the account.
Get User Permissions Returns what one person may do, which is the read that explains a refused write before it happens.
Get Current User Permissions Returns what the connected person may do.
List Roles Lists the roles the account defines.
Get User Capacities Returns one person's expected hours, which is the denominator behind any "is anyone behind" question.
List Capacities Lists expected hours across the account.
Get Compliance Metrics Returns Timely's own measure of how completely time has been logged. The read that finds the gaps before a period is closed.

Time Entries

List Time Entries Lists entries over a range with filters. The core read behind reconciliation and reporting flows.
Get Time Entry Returns one entry.
Create Time Entry Logs time. Timely wraps a time entry's write body in its own key rather than the one the product uses, and the connector handles that, which is the single most likely thing to get wrong against this API by hand.
Update Time Entry Corrects an existing entry, provided the day and the state it sits in still allow edits.
Start Timer Starts a running entry. A running timer in Timely is an ordinary time entry that has not ended yet.
Stop Timer Ends the running entry.
Delete Time Entry Removes an entry.
Bulk Import Time Entries Writes a set of entries as logged time. The route to use when the time is already decided.
Bulk Import Events Feeds Timely's memory side, the automatic tracking stream its suggestions are built from. The route to use when a person should still turn the raw activity into time.

Projects and Clients

List Projects Lists the account's projects.
Get Project Returns one project with its rate, budget and billable settings.
Create Project Creates a project so time can be logged against it.
Update Project Changes a project, including its rate, budget and whether it is billable.
Delete Project Removes a project. Making a finished project non-billable usually preserves more than deleting it does.
List Clients Lists the account's clients.
Get Client Returns one client.
Create Client Creates a client to hang projects from.
Update Client Changes a client's details.

Tags and Tasks

List Tags Lists the account's tags. Timely calls a tag a label on the wire; the connector uses the product's word.
Get Tag Returns one tag.
Create Tag Creates a tag.
Update Tag Changes a tag, which changes it everywhere it is used.
Delete Tag Removes a tag.
List Tasks Lists planned work. A Timely task is planned effort with a date range and an estimate, not a to-do.
Get Task Returns one planned task with its estimate and range.
Create Task Plans work with an estimate over a date range, optionally with per-person estimates when several people share it.
Update Task Changes a planned task. It is closed by setting a completion timestamp rather than a done flag.
Delete Task Removes a planned task.
Get Task Summaries Returns planned against actual, which is the read behind an honest progress answer rather than a hopeful one.

Teams

List Teams Lists the account's teams.
Search Teams Finds teams by search term.
Get Team Returns one team with its membership.
Create Team Creates a team.
Update Team Replaces a team, including its membership, so send the whole list rather than the additions.
Patch Team Changes a team's name or color without touching its membership. The safer call when membership is not the point.
Delete Team Removes a team.

Approval States and Day Locking

List States Lists the approval states time entries move through, each carrying its own billed and locked flags.
Create State Creates an approval state.
Update State Changes a state. Turning Locked on applies to every entry already sitting in it, not just the ones that arrive afterwards.
Delete State Removes an approval state.
Set State Permissions Decides who may move an entry into or out of a state. Without it the states carry no authority at all.
Delete State Permission Removes a state permission.
List Time Entry States Lists the same approval states through Timely's second route onto the records, which it publishes alongside the first.
Create Time Entry State Creates an approval state through that second route.
Update Time Entry State Changes an approval state through that second route.
Delete Time Entry State Removes an approval state through that second route.
List Day Properties Returns the per-day properties for a range, including which days are already locked.
Lock Days Closes a period against all time edits for the named people, including their own corrections. The operation this page's human gate exists for.
Update Day Properties Changes other properties on a day without closing it.

Reports

Get Report Totals Returns hours, cost and revenue for a period. The summary read behind a reconciliation.
Filter Reports Returns the rows behind those totals, filtered and grouped the way Timely's own reporting screen does.

Connection and Access

Get Token Info Reports the current token's scopes, owner and expiry. A cheap connection health check.
List Authorized Applications Lists what has access to the connected person's account, which is the starting read for a periodic access review.
Revoke Application Authorization Withdraws an application's access. Revoking this connection's own application ends the connection.

Webhooks

List Webhooks Lists the account's webhook subscriptions, which is how a flow audits what is calling out.
Get Webhook Returns one subscription.
Create Webhook Registers a subscription, for delivering somewhere other than FlowRunner.
Update Webhook Changes a subscription.
Delete Webhook Removes a subscription.

Triggers

1 triggers

Event Triggers

On Timely Event Fires on a Timely webhook, for one chosen event or for all twelve, covering created, updated and deleted across time entries, projects, tags and planned tasks. Set a signing secret on the trigger and every delivery is verified against Timely's own HMAC signature with a timing-safe comparison, and anything that does not match is refused. Without a secret, deliveries are accepted unverified, which is a choice worth making deliberately when the payload will start a flow that writes.

Frequently Asked Questions

What can FlowRunner do with Timely?

FlowRunner agents can run Get Current User, List Users, and Search Users in Timely, plus 69 more actions.

Does connecting Timely to FlowRunner require OAuth?

Yes. Timely connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Timely trigger a FlowRunner workflow automatically?

Yes. Timely supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Timely

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us