--- title: "Toodledo Integration" description: "Toodledo is the long-running task, note, outline, and list manager. Agents add and edit tasks with folders, contexts, goals, and locations, write notebook entries, maintain outlines and custom lists, and use account timestamps for incremental sync." url: https://flowrunner.ai/integrations/toodledo date_modified: 2026-09-04T14:52:04-07:00 --- # Toodledo [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Toodledo is the long-running task, note, outline, and list manager. Agents add and edit tasks with folders, contexts, goals, and locations, write notebook entries, maintain outlines and custom lists, and use account timestamps for incremental sync. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 42 actions · OAuth · available [Toodledo website](https://www.toodledo.com/) · [Platform Documentation](https://api.toodledo.com/3/) · Capability data verified 2026-08-24 1. A scheduled sync run opens against the connected Toodledo account 2. Get Account Info returns a timestamp per resource, and the task timestamp has moved 3. List Tasks pulls only the records changed since the last run, naming the fields the flow needs 4. List Deleted Tasks reports which ids disappeared, because a deleted task simply stops appearing 5. Agent reconciles the changed and vanished records against the team's mirror 6. Edit Tasks writes back the completions and dates that came from the other side 7. The owner confirms the deletions before the flow propagates any of them ## What This Integration Enables Toodledo is built for people who never wanted a team board. It is a personal system of record with folders, contexts, goals and saved locations, and it has outlasted a decade of tools that tried to replace it. What makes it interesting to [Orchestration as a Service](https://flowrunner.ai/concepts/orchestration-as-a-service) is not the task list. It is that Toodledo exposes a per-resource change timestamp and a separate feed of what was deleted, for tasks, notes, outlines, custom lists and rows alike. Most personal tools give you neither. That pair is exactly what a two-way sync needs in order to be correct rather than approximate. FlowRunner agents use that structure the way Toodledo's own clients do. An agent reads Get Account Info first, downloads nothing when nothing has moved, pulls only what changed, and asks the deleted-item feed what vanished. It writes back in batches of up to fifty records and checks each record's own result rather than trusting the HTTP status. Every one of these operations is built and verified against Toodledo's official API, which is why the page below describes behavior rather than possibilities. What FlowRunner adds on top is the part a raw API cannot supply: judgment about which of those writes a person should see before they happen. ### Without FlowRunner **Two lists, one person**: Personal work lives in Toodledo and team work lives elsewhere, and the person is the sync **Deletions go unnoticed**: A task removed in one system stays alive in the other until somebody spots it **Full pulls every time**: Without a change signal, keeping a mirror current means reading the whole account on a schedule ### With FlowRunner **One list, kept honest**: Agents move changes both ways so the person plans in the tool they actually use **Disappearances are visible**: The deleted-item feed tells the mirror what went, and a person decides whether it should go there too **Reads scoped to changes**: The account timestamps decide whether there is anything to download at all ## Use Case Scenarios ### The personal list that stays current without anyone maintaining it An operations lead runs their own week out of Toodledo while the team runs out of a shared board. On a schedule, an agent calls Get Account Info, notices the task timestamp has moved, and pulls the changes with List Tasks. Anything assigned to that person in [ClickUp](https://flowrunner.ai/integrations/clickup) or [Asana](https://flowrunner.ai/integrations/asana) arrives through Add Tasks with the right folder, context and goal already set. Completions made in Toodledo travel the other way. Because Edit Tasks can reschedule a repeating task and its subtasks in the same call, recurring work stays recurring instead of quietly stopping at the first completion. ### Meeting notes and reference material that land where the work is A meeting summary produced upstream needs somewhere durable. The agent writes it through Add Notes, files the action items as tasks against the goal they serve, and leaves the reference structure in an outline through Add Outlines so the detail is nested rather than flattened. When the same document is revised later, Edit Outlines carries the version the flow read, so an edit made on the phone in the meantime is refused rather than overwritten. The flow discovers the conflict and routes it, instead of silently winning. ### A custom list used as a small operational table Toodledo's custom lists have typed columns, which makes them a usable place for a short operational register: on-call rotations, equipment loans, reading queues. An agent reads List Lists to learn the column ids, appends through Add Rows keyed by column, and pushes a weekly summary of the register into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) or a channel in [Slack](https://flowrunner.ai/integrations/slack). The list stays where the person looks at it and the reporting happens somewhere else, which is the split most people want and rarely get. ## Human-in-Loop Highlight Toodledo's own guidance is that finished and repeating work should be completed, not deleted, because a deleted task leaves the user's history and stops recurring. Delete Tasks is permanent, and the only trace afterwards is an id in List Deleted Tasks. So a FlowRunner sync agent will happily create, complete and reschedule on its own, and it stops dead at deletions coming from the other system. It gathers them and asks: "The shared board no longer has 11 tasks that exist in your Toodledo account, including 3 that repeat weekly. Delete them here, mark them complete instead, or leave them alone?" The owner answers on the channel they already use. A mirror that propagates deletions without asking is not a sync, it is a slow data loss, and this is the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) moment that separates the two. 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 42 actions ### Account and Sync 1 - **Get Account Info** Returns the account's details and a last-edit timestamp per resource. This is the first call in every sync, because an unmoved timestamp means there is nothing to download. ### Tasks 5 - **List Tasks** Reads tasks, with a modified-after cutoff for incremental pulls. Only a small default field set comes back, so the flow names the fields it actually needs. - **Add Tasks** Creates up to fifty tasks in one call, each carrying its own reference value so a batch can be matched back to its source rows afterwards. - **Edit Tasks** Changes up to fifty tasks in one call. Used for completions, date changes and reassignment between folders, and it can work out the next occurrence of a repeating task. - **Delete Tasks** Permanently removes tasks. This is the operation the human gate on this page exists for. - **List Deleted Tasks** Returns the ids of tasks deleted since a moment, with when each went. It is the only way a mirror learns that something disappeared. ### Notes 5 - **List Notes** Reads notebook entries with their full text. - **Add Notes** Creates notebook entries in batches. Used to land meeting summaries and reference material next to the work they belong to. - **Edit Notes** Updates notebook entries in batches. - **Delete Notes** Permanently removes notebook entries. - **List Deleted Notes** Returns the ids of notes deleted since a moment, so a mirror can drop them too. ### Outlines 5 - **List Outlines** Reads outlines with their whole node tree, which is how nested reference material comes back intact. - **Add Outlines** Creates outlines, with a reference value so a retried sync does not add the same outline twice. - **Edit Outlines** Updates an outline against the version the flow read. An edit made elsewhere in the meantime is refused rather than silently overwritten. - **Delete Outlines** Permanently removes outlines and every node inside them. - **List Deleted Outlines** Returns the ids of outlines deleted since a moment. ### Custom Lists 5 - **List Lists** Reads the custom lists with their column definitions. Run it before touching rows, because cells are keyed by column id. - **Add Lists** Creates a custom list and defines its columns. - **Edit Lists** Updates a custom list against the version the flow read. Sending columns replaces the whole column set rather than adding to it. - **Delete Lists** Permanently removes a custom list and every row in it. - **List Deleted Lists** Returns the ids of custom lists deleted since a moment. ### Custom List Rows 5 - **List Rows** Reads the rows of one custom list, with cells keyed by column id. - **Add Rows** Appends rows to a custom list. Used to keep a small operational register current from an upstream system. - **Edit Rows** Updates rows against the version the flow read, which is Toodledo's conflict check for simultaneous edits. - **Delete Rows** Permanently removes rows from a custom list. - **List Deleted Rows** Returns the ids of rows deleted from a custom list since a moment. ### Folders 4 - **List Folders** Reads the folders, which are usually the main way a Toodledo account is organized. - **Add Folder** Creates a folder. The folder, context, goal and location routes take one record per call rather than a batch. - **Edit Folder** Renames a folder, archives it, or changes whether it is private. Archiving keeps the folder and its tasks while taking it out of everyday lists. - **Delete Folder** Removes a folder. The tasks inside it survive and become unfiled, and archiving is the reversible alternative. ### Contexts 4 - **List Contexts** Reads the contexts, which record what a task needs in order to be done: a place, a tool or a person. - **Add Context** Creates a context. - **Edit Context** Renames a context or changes whether it is private. - **Delete Context** Removes a context. The tasks that used it keep existing without one. ### Goals 4 - **List Goals** Reads the goals, which are the outcomes individual tasks contribute towards. - **Add Goal** Creates a goal, optionally pointing it at the longer-term goal it serves so the hierarchy stays intact. - **Edit Goal** Updates a goal, including archiving one that has been reached. - **Delete Goal** Removes a goal. Archiving through Edit Goal is the alternative that keeps the record. ### Locations 4 - **List Locations** Reads the saved locations with their coordinates, which Toodledo uses for location-based reminders. - **Add Location** Creates a saved location. - **Edit Location** Updates a saved location's name, description or coordinates. - **Delete Location** Removes a saved location. The tasks that referred to it keep existing without one. ## Frequently Asked Questions ### What can FlowRunner do with Toodledo? FlowRunner agents can run Get Account Info, List Tasks, and Add Tasks in Toodledo, plus 39 more actions. ### Does connecting Toodledo to FlowRunner require OAuth? Yes. Toodledo connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Toodledo trigger a FlowRunner workflow automatically? Toodledo doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Toodledo?** This integration exposes Toodledo to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/toodledo. Site index: https://flowrunner.ai/llms.txt