Any.do Workspace
ProductivityManage team tasks in Any.do Workspace. Agents list, create, update, and delete tasks and browse the categories they belong to, turning inbound requests from forms, email, or chat into tracked work.
What This Integration Enables
A shared task list only works if capturing tasks costs nothing, and it never does: someone has to notice the request, decide where it goes, and type it in. That is the gap where teams quietly fall back to inbox archaeology. This connector makes Any.do Workspace the destination that fills itself. FlowRunner agents turn inbound requests into categorized tasks, keep status honest as work completes in other systems, and give the team a daily picture of what is actually open. - File tasks from forms, email, and chat with due date, priority, and source notes - Route work to the right list using live category lookups - Mark tasks done or reschedule them when connected systems report progress - Post open-task digests so standup starts from the real list - Sync tasks with other trackers in either direction There is a deeper point under the convenience: a task list that fills and updates itself changes what the list is. When capture is manual, the list records what people remembered to admit they owe; when agents capture from the actual request streams, the list becomes an honest ledger of the team's obligations. That honesty is what makes the daily digest worth reading and the standup worth shortening. FlowRunner supplies the missing piece manual tools cannot: the [human-in-the-loop](/concepts/human-in-the-loop) review that keeps the automated ledger curated by someone who knows which obligations actually matter this week. Capture runs at machine speed, cleanup waits for judgment, and the list stays something the team trusts enough to actually run their day from, which is the only metric a task system has ever really had.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The inbox that empties into the task list
A morning agent runs through the shared inbox via [Gmail](/integrations/gmail), pulls messages containing action items, and files each one with Create Task: the ask as the title, the request context in notes, the category resolved through List Categories. Duplicates get caught by a List Tasks scan first. By 9am the operations list holds everything that arrived overnight, each task pointing back to its source email, and nobody starts the day by re-reading forty threads to reconstruct what needs doing.
Status that updates without a nag
When a prep meeting ends in [Google Calendar](/integrations/google-calendar), the agent finds the linked prep task and calls Update Task to mark it done. When a client pushes a deadline, the agent reschedules the dependent tasks' due dates in one pass instead of someone editing five entries by hand. The list stops being a museum of things that were once true. Get Task backs each update, so the agent modifies exactly the task it means to and nothing else.
The daily digest that replaces the "what's everyone on?" meeting
At 8:30 each morning, List Tasks pulls open items across categories and the agent posts a digest to [Slack](/integrations/slack): overdue tasks first, then today's due items grouped by list, with priorities marked. The team lead scans it in two minutes, drags one thing up, delegates another. The standing status meeting shrinks because the status already stood up on its own.
Human-in-Loop Highlight
Delete Task is permanent: the task, its notes, and the trail of why it existed vanish, and Any.do offers no undo through this connector. In a cleanup sweep, that permanence points at exactly the tasks most likely to matter, the stale-looking item that is actually a customer commitment someone filed months ago. So FlowRunner cleanup agents never delete on their own judgment. They assemble the candidates: tasks untouched for sixty days, tasks whose category was retired, apparent duplicates with the evidence side by side. The list goes to the team lead as a review, each entry showing title, notes, and age. Whatever the lead approves gets deleted; whatever they hesitate on survives, usually rescheduled with Update Task instead. Closing a task is reversible and agents do it freely. Erasing one is not, and that difference is where the person stands.
Agent Capabilities
6 actionsTasks
5- List Tasks Lists workspace tasks, optionally filtered by category and status, returning title, status, due date, priority, and parent category. The read behind digests, dedup checks, and cleanup sweeps.
- Get Task Retrieves one task in full by ID, including notes and category. The precision step before any update or delete, so agents act on the task they mean to.
- Create Task Creates a task with title and optional due date, priority, notes, and category. The action that turns an inbound request into tracked work.
- Update Task Updates only the fields supplied: title, due date, priority, notes, category, or status. How agents mark work done, reschedule, and refile without touching anything else on the task.
- Delete Task Permanently deletes a task by ID. Cannot be undone, and the operation this page's human gate exists for.
Categories
1- List Categories Lists the workspace's task lists with ID and name. The routing table that lets agents file work where the team will actually look for it.
Frequently Asked Questions
What can FlowRunner do with Any.do Workspace?
FlowRunner agents can run List Tasks, Get Task, and Create Task in Any.do Workspace, plus 3 more actions.
Does connecting Any.do Workspace to FlowRunner require OAuth?
No. Any.do Workspace connects to FlowRunner with an API key, no OAuth flow required.
Can Any.do Workspace trigger a FlowRunner workflow automatically?
Any.do Workspace doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Any.do Workspace
$100 in credits. No card required. Connect in minutes.