Reclaim.ai

Connect AI agents to Reclaim.ai, the AI scheduling assistant for Google Calendar. Agents create and update tasks, mark them done, and read habits and calendars so Reclaim finds the time on your team's schedule automatically.

8 actions API key available

Reclaim.ai website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A support escalation lands that needs two hours of real work by Friday

The agent sizes the work: 8 time chunks, minimum block 30 minutes, priority High

List Tasks confirms no existing task already covers this work

Create Task hands the work to Reclaim, which books the time on the calendar before the due date

A daily reconciliation compares List Tasks against the calendar for tasks losing their time to meetings

The owner decides the trade when the week runs out of room: bump the deadline, raise the priority, or drop something else

The completion posts to the team channel when the work wraps

What This Integration Enables

Reclaim.ai's core insight is that a task without booked time is a wish, and its scheduler turns tasks into defended calendar blocks. FlowRunner completes the loop by connecting that scheduler to where work actually originates. Agents convert form submissions, tickets, and emails into sized, auto-scheduled tasks, adjust duration, priority, and deadlines so Reclaim re-plans as reality shifts, mark work done to release remaining blocks, and read habits and calendars to reconcile the plan against the week. - Turn [Typeform](/integrations/typeform) submissions or [Gmail](/integrations/gmail) follow-ups into auto-scheduled tasks with priority and due date - Sync a [Todoist](/integrations/todoist) backlog into Reclaim so every item gets real working time - Re-plan programmatically: extend chunks, tighten deadlines, raise priority, and let Reclaim rebook - Post completions to [Slack](/integrations/slack) and log finished work to [Google Sheets](/integrations/google-sheets) - Reconcile scheduled focus time against [Google Calendar](/integrations/google-calendar) meetings and surface conflicts The time-chunk model is what makes this precise: work is expressed in 15-minute chunks with bounds on how it splits, so an agent can say "two hours, in blocks no smaller than 30 minutes, by Friday, High priority" and mean exactly that.

Without FlowRunner

Work arrives without time attached The ticket gets acknowledged, and the two hours it needs are never actually booked

To-do lists and calendars disagree The backlog says twenty tasks; the calendar says there was never room for twelve

Follow-ups die in the gap "I'll get to it this week" has no defense when meetings flood in

With FlowRunner

Incoming work claims calendar time New work becomes a sized, prioritized task and Reclaim finds the hours automatically

The calendar is the honest backlog What fits is scheduled; what does not fit surfaces as a decision, not a surprise

Deadlines get defended Priority and due date drive rebooking when meetings collide with the work

Use Case Scenarios

The follow-up that books its own time

A [Typeform](/integrations/typeform) response requests a custom integration review. The agent estimates the work at 6 chunks, sets priority Medium and a due date of next Wednesday, and calls Create Task. Reclaim books the ninety minutes across the owner's actual free space. The difference from a to-do app is that the time now exists on the calendar, where meetings have to negotiate with it instead of silently displacing it.

The backlog that stops lying

Nightly, the agent reads the [Todoist](/integrations/todoist) backlog and mirrors new items into Reclaim with Create Task, sized by the estimate field. Items Reclaim cannot fit before their due dates show up in the morning digest as explicit conflicts. The team's planning conversation changes from "what is on the list" to "what fits in the week," which is the conversation that was always the real one.

The weekly reconciliation report

Friday afternoon, List Tasks pulls everything by status and List Habits reads the standing routines. The agent cross-references [Google Calendar](/integrations/google-calendar) events, then writes the week's story to [Google Sheets](/integrations/google-sheets): tasks completed, tasks still carrying remaining chunks, habits that got displaced by meetings more than twice. The owner sees where the week actually went, and the following week's priorities get set from evidence.

Human-in-Loop Highlight

Mark Task Done removes every remaining scheduled block for that task from the calendar, and calendar time is the one resource this connector manages that does not regenerate. The moment those blocks vanish, Reclaim and everyone else's meeting invitations flow into the gap, and if the agent marked the wrong task, or matched "done" to a task that was only half done, the two protected hours before Thursday's deadline are gone and the week has no more Thursdays to give. So FlowRunner flows treat completion as a claim to verify, not a signal to relay: the agent presents the task, its remaining chunks, and the evidence of completion, the closed ticket, the merged PR, the sent deliverable, and the owner confirms before the planner releases the time. Update Task gets the same respect when it shrinks chunks or pushes deadlines, because every reduction quietly hands hours back to a calendar that will immediately spend them on something else.

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

8 actions

Tasks

List Tasks Lists tasks with optional status filtering across New, Scheduled, In Progress, Complete, Cancelled, and Archived, returning title, priority, time-chunk requirements, due date, and scheduling status. The reconciliation read behind digests and dedup checks.
Get Task Retrieves one task by numeric ID with its priority, event category, chunk requirements, remaining chunks, due date, snooze settings, and scheduling status. The evidence read before completion or re-planning decisions.
Create Task Creates an auto-scheduled task with total work in 15-minute chunks, minimum and maximum block sizes, priority from Critical to Low, and a due date. Reclaim finds and books the time automatically, which is the entire point.
Update Task Updates a task's title, due date, snooze, chunk requirements, priority, or category as a partial update, and Reclaim re-plans the booked time accordingly. The re-planning lever, used with review when it releases hours.
Mark Task Done Marks a task complete via the planner, removing its remaining scheduled blocks from the calendar. The action this connector's human gate exists for, because released time does not come back.

Habits

List Habits Lists recurring routines such as lunch or daily planning with cadence and duration settings. The context read for reconciling routines against the week's actual shape.

Account

Get Current User Retrieves the profile of the account that owns the API key: name, email, timezone, and subscription details. The identity check that confirms which calendar a workflow is about to write into.
List Calendars Lists the connected Google or Microsoft calendars with ID, name, provider, and connection status. The verification read behind every scheduling flow's setup.

Frequently Asked Questions

What can FlowRunner do with Reclaim.ai?

FlowRunner agents can run List Tasks, Get Task, and Create Task in Reclaim.ai, plus 5 more actions.

Does connecting Reclaim.ai to FlowRunner require OAuth?

No. Reclaim.ai connects to FlowRunner with an API key, no OAuth flow required.

Can Reclaim.ai trigger a FlowRunner workflow automatically?

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

Start building with Reclaim.ai

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

Start Building Free Talk to us