FlowRunner
PricingContact
Theme
Start Free

Toggl Plan

Project Management

Toggl Plan is visual team planning on a timeline, with a backlog for work that has no dates yet. Agents create and schedule tasks, manage projects, milestones and members, and move backlog items onto the timeline when they are committed.

31 actions OAuth available
Toggl Plan website Platform Documentation Capability data verified 2026-08-18
A project is scoped elsewhere and its work arrives as items with no dates yet
List Tasks against the backlog view reads everything waiting to be committed
List Members and List Groups resolve who is actually available, including placeholder people with no account yet
List Milestones confirms no holiday already blocks the days being proposed
Create Project groups the work and gives it a shared color on the timeline
Agent posts the proposed schedule with each person's dates and the tasks it would move
The delivery lead approves before Update Task writes dates and assignees onto the timeline

What This Integration Enables

Toggl Plan draws a line most planning tools blur. A task with no dates sits in the backlog. A task with dates sits on the timeline, in a named person's week, where everyone can see it. Even the API keeps the distinction: the view is part of the path, so a workflow asks for backlog work or timeline work and gets exactly that. Nothing about a task changes except its dates, and that alone moves it from something the team might do to something a person has been committed to.

FlowRunner agents are useful on both sides of that line and behave differently on each. On the backlog side they can create, group, tag and prune freely, because nothing there is a promise. On the timeline side they prepare rather than decide: they resolve availability, check for holidays that block a group's days, plan work against placeholder members for people who have not been invited yet, and assemble the schedule. Then a person commits it. That is not a limitation the platform imposes, it is what makes the timeline worth trusting, and it is the plain form of human-in-the-loop that this connector calls for.

Without FlowRunner

Committed and uncommitted work look alike A list of tasks does not say which ones somebody has actually promised to do
Reschedules quietly lose people A bulk update names one assignee and the others simply stop being on the task
Time off invisible to the plan Leave is approved in one system and the timeline keeps offering those days

With FlowRunner

The line between wish and promise is explicit Backlog work has no dates, timeline work does, and moving between them is a decision
Reschedules are reviewed as a diff The agent shows what the assignee list would become before it writes it
Approved leave blocks the day Time off becomes a holiday milestone, and the group's availability changes with it

Use Case Scenarios

  • Backlog work becomes a week somebody has agreed to

    Scope arrives from wherever the project was shaped, perhaps a plan in ClickUp or a signed statement of work. The agent creates the tasks with no dates, so they land in the backlog and nobody is committed yet. It then does the arithmetic: List Members for who is active, List Groups for which team the work belongs to, and List Milestones for holidays already blocking the proposed days. It assembles a schedule and posts it. Only after a person approves does Update Task write the dates and the assignee list, which is the moment the work appears on the timeline and in somebody's week.

  • Planning around people who do not have accounts yet

    A contractor is confirmed but not yet invited, and the work still has to be planned. Create Placeholder Member creates a member with no Toggl Plan account, so their capacity exists on the timeline before their login does. The agent plans against that placeholder and keeps it current with Update Placeholder Member, which is a separate route from the one that updates real members. When the contractor is finally invited, the linking is a deliberate step rather than something the agent guesses at, and the planned work is already sitting there waiting for them.

  • Approved time off changes what the timeline offers

    Leave is approved somewhere else, in an HR system or a shared calendar such as Google Calendar. The agent turns each approval into a milestone marked as a holiday for the right group, which blocks those days rather than merely annotating them. Any task already scheduled across a newly blocked day is collected and reported to Slack rather than silently moved, because moving somebody else's committed work is a scheduling decision with a person behind it. When leave is canceled, Delete Milestone releases the day and the availability comes back.

Human-in-Loop Highlight

The costly operation here is not the obvious one. Delete Task is unrecoverable, since Toggl Plan has no archive and no trash for tasks, and that alone justifies a review before a backlog prune. But the write that does real damage while looking like it worked is Update Task. Supplying assignees replaces the entire list, and supplying tags replaces the entire set, so a reschedule agent that computes new dates and names the one person it knows about removes everyone it did not name. The task still exists. It still has dates. It is simply no longer anybody else's work, nothing errors, and the first person to find out is whoever was quietly taken off it. So the reschedule agent renders a diff and stops: "Sprint slip moves 9 tasks out by four days. On 3 of them the update would set assignees to Priya alone, dropping Marco and Dana who are currently on them. Apply as shown, keep the existing assignees, or hold the three?" A person answers in the channel, the agent writes exactly that, and posts what changed. The agent did the scheduling. The commitment stayed with a human.

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

31 actions

Profile

2
  • Get My Profile Returns the connected person's profile with the workspaces they belong to. It is the only call that does not need a workspace, so it is how a workflow finds the identifiers everything else needs.
  • Update My Profile Changes the connected person's own name or initials. It cannot change anyone else's.

Members

6
  • List Members Returns the people in a workspace, including placeholder members who have no account yet.
  • Get Member Returns one member with their role, working hours and whether they are still active.
  • Update Member Changes a member's name, initials, color or timeline weight. Their role and email belong to the account rather than the membership and cannot be changed here.
  • Remove Member Removes somebody from a workspace. Their tasks stay behind unassigned rather than being deleted with them.
  • Create Placeholder Member Creates a member with no Toggl Plan account, so work can be planned against somebody before they are invited.
  • Update Placeholder Member Changes a placeholder member who is not yet linked to a real account. A separate route from the one that updates real members.

Tasks

5
  • List Tasks Returns a workspace's tasks. The view is part of the request: backlog returns unscheduled work, timeline returns dated work, and asking for neither returns both.
  • Get Task Returns one task with its dates, assignees, estimate and tags.
  • Create Task Creates a task. Dates are what decide where it appears: no dates puts it in the backlog, dates put it on the timeline.
  • Update Task Changes a task. Assignees and tags are each replaced wholesale rather than merged, which is why this page gates reschedules.
  • Delete Task Deletes a task. There is no archive and no trash, so a prune is permanent.

Milestones

5
  • List Milestones Returns a workspace's milestones, which are single dated markers rather than spans of work.
  • Get Milestone Returns one milestone.
  • Create Milestone Creates a milestone on a date. Marking it a holiday blocks the day for the group it belongs to, which changes what the timeline shows as available.
  • Update Milestone Changes a milestone's name, date, group or completion. Turning completion off reopens it.
  • Delete Milestone Deletes a milestone. If it was a holiday, the day becomes available again.

Projects

5
  • List Projects Returns a workspace's projects, including archived ones, with the tags each carries.
  • Get Project Returns one project.
  • Create Project Creates a project, which groups tasks and gives them a shared color on the timeline.
  • Update Project Changes a project's name, color or archived state. Archiving hides it without deleting its tasks, and it is reversible.
  • Delete Project Deletes a project. Archiving through an update is the reversible alternative and is usually the right call.

Groups

8
  • List Groups Returns a workspace's groups with their memberships attached. A group is a team on the timeline and is also what a holiday milestone applies to.
  • Get Group Returns one group with its memberships.
  • Create Group Creates a group and puts people in it in a single call.
  • Update Group Renames a group or resets who is in it. Supplying members replaces the whole membership, so anyone left out is removed.
  • Delete Group Deletes a group. Its members keep their workspace accounts and only the grouping goes.
  • List Group Members Returns the memberships of one group. A membership carries its own identifier, which is what a removal needs.
  • Add Group Member Adds one person to a group without disturbing the rest, which a group update would.
  • Remove Group Member Takes one person out of a group. It needs the membership identifier rather than the person's user identifier, so the membership is read first.

Frequently Asked Questions

What can FlowRunner do with Toggl Plan?

FlowRunner agents can run Get My Profile, Update My Profile, and List Members in Toggl Plan, plus 28 more actions.

Does connecting Toggl Plan to FlowRunner require OAuth?

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

Can Toggl Plan trigger a FlowRunner workflow automatically?

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

Start building with Toggl Plan

Free plan, no card required. Connect in minutes.