FlowRunner
By team All teams DevelopersSecurity & ITFinance & OperationsRevOpsSupport & CXData & Platform By industry All industries HealthcareFinancial ServicesLogistics By use case All use cases Invoice validationApproval routingClient intakePrior authorizationData reconciliationComplaint triage
All Integrations AI & LLMsDatabases & WarehousesIdentity & SecurityCRM & SalesCommunication & MessagingFinance & Accounting
Pricing
ConceptsCompareGuidesSolution libraryBlog
Theme

Toggl Track

Productivity

Track time in Toggl Track from your flows: start and stop timers, log entries, and keep projects, clients, and tags in sync. Agents track routine work and gate bulk corrections that move billing behind a person.

28 actions available
A task is assigned in another tool, or a period closes on a schedule
Agent reads the project, client, and duration for the work
Agent confirms the entry maps to a real project and client
Agent checks the current running entry to avoid a double log
Agent starts a timer or logs a completed entry
Agent posts the tracked total to the team for the period
A bulk correction across many entries is routed for a person to approve

What This Integration Enables

FlowRunner agents use Toggl Track to run tracking and cleanup as decisions, not manual entry. An agent can start and stop timers when work begins and ends, log completed entries into the right project and client, and keep projects, clients, and tags in sync with a CRM or task manager. It can pull entries on a schedule for reporting, invoicing, or timesheet exports, and check the current running entry to avoid double-logging. The routine tracking runs on its own. The sweeping correction, reassigning many entries or flipping their billable status at once, is where the agent stops to ask, because it changes what a period will bill.

Without FlowRunner

Manual time logging People start and stop timers by hand, or forget to
Miscategorized entries Work gets logged to the wrong project and never gets fixed
Unreviewed corrections A bulk edit to billable status runs with no one checking the impact

With FlowRunner

Time logs itself Timers start and stop as work begins and ends in another tool
Consistent categorization Entries land against the right project and client the same way each time
Reviewed corrections A person approves a bulk edit before it rewrites a period's entries

Use Case Scenarios

Timer From a Task Tool

A task is assigned in another tool. The agent checks the current running entry to make sure nothing is already tracking, then calls Start Timer against the matching project. When the task closes, it stops the timer with Stop Timer. Time is tracked without anyone remembering to start it.

Scheduled Timesheet Export

On a schedule, the agent pulls the period's entries with List Time Entries and appends each into a timesheet spreadsheet. The team gets a current export for reporting or invoicing without assembling it by hand.

Bulk Recategorization with an Approval Gate

A review finds that a batch of entries was logged to the wrong project or marked billable in error. The agent lists the affected entries and prepares an Update Time Entry correction for each. Before it rewrites billable status or project across many entries at once, it pauses for a manager to approve the batch, because those entries feed billing.

Human-in-Loop Highlight

When an agent finds a batch of miscategorized entries and is about to run Update Time Entry across all of them, it does not just apply the fix. Reassigning entries or flipping their billable status in bulk changes what a period will invoice, and the previous values are overwritten. The agent pauses and routes to the workspace manager through their preferred channel: "Found [N] entries logged to [wrong project] or marked billable in [period]. Ready to reassign them to [right project] and set billable to [value]. Approve the batch or review the list first?" The manager decides, and the agent applies the corrections only on approval. Routine tracking runs on its own; a bulk edit that moves billing reaches a person first.

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

28 actions

Time Entries

8
  • Create Time Entry Creates a time entry with a start time and duration, optionally a running entry, in a workspace. Used to log completed or running work.
  • Start Timer Starts a running entry using Toggl's running-entry convention. Used to begin tracking when work starts.
  • Stop Timer Stops a running entry and computes its final duration. Used to close out tracking.
  • Get Current Running Entry Returns the entry currently running for the user, or null. Used to avoid double-logging before starting a timer.
  • Get Time Entry Retrieves a single entry with its timing, project, tags, and billable status. Used to read an entry before acting.
  • List Time Entries Lists the user's entries with an optional date range. Used to pull hours for reporting or export.
  • Update Time Entry Updates an entry's fields, changing only the ones provided. Used to correct an entry, gated behind a human approval for bulk edits.
  • Delete Time Entry Permanently deletes an entry from a workspace. Used to remove an erroneous log.

Projects

5
  • List Projects Lists projects with an active filter. Used to resolve which project to track against.
  • Get Project Retrieves a project with its client, color, and billable status. Used to inspect a project.
  • Create Project Creates a project with a client, color, and billable flags. Used to provision a project on demand.
  • Update Project Updates a project's fields or archives it. Used to keep project settings in sync.
  • Delete Project Permanently deletes a project; associated entries lose the link. Used in cleanup.

Clients

4
  • List Clients Lists the clients in a workspace. Used to resolve which client a project belongs to.
  • Create Client Creates a client with a name. Used to onboard a client for tracking.
  • Update Client Renames a client. Used to keep client records in sync.
  • Delete Client Permanently deletes a client; associated projects lose the link. Used in cleanup.

Tags

4
  • List Tags Lists the tags in a workspace. Used to resolve which tags to attach to entries.
  • Create Tag Creates a tag with a name. Used to build a tagging scheme.
  • Update Tag Renames a tag. Used to maintain the tagging scheme.
  • Delete Tag Permanently deletes a tag and removes it from entries. Used in cleanup.

Tasks

4
  • List Tasks Lists the tasks in a project (a paid-plan feature). Used to resolve which task to track against.
  • Create Task Creates a task in a project with an estimate. Used to provision a sub-unit of work.
  • Update Task Updates a task's name, estimate, or active status. Used to keep tasks in sync.
  • Delete Task Permanently deletes a task from a project. Used in cleanup.

Workspace and User

3
  • Get Me Returns the authenticated user's profile and default workspace, optionally with related data. Used to discover the workspace ID for other operations.
  • List Workspace Users Lists workspace members with their names and admin status. Used to route entries to the right person.
  • Get Workspace Retrieves a workspace with its plan and default settings. Used to inspect the workspace.

Other Productivity integrations

IntegrationClockify25 actionsIntegrationCoda22 actionsIntegrationFireflies.ai6 actions

Start building with Toggl Track

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

Start Building Free Talk to us