--- title: "Amazing Marvin Integration" description: "Amazing Marvin is the customizable personal task manager built around strategies. Agents create and schedule tasks, projects, and events, read the day's plan and what is due, log time, score habits, track goals and reward points, and set reminders." url: https://flowrunner.ai/integrations/amazing-marvin date_modified: 2026-09-04T14:52:04-07:00 --- # Amazing Marvin [Productivity](https://flowrunner.ai/integrations/category/project-management-productivity) Amazing Marvin is the customizable personal task manager built around strategies. Agents create and schedule tasks, projects, and events, read the day's plan and what is due, log time, score habits, track goals and reward points, and set reminders. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 32 actions · API key · available [Amazing Marvin website](https://amazingmarvin.com/) · [Platform Documentation](https://amazingmarvin.com/) · Capability data verified 2026-08-24 1. A request lands in a shared inbox or a ticket is assigned to the operator 2. Agent pulls the ask, the requester, and the date it is actually needed by 3. Get Due Items reads what is already overdue before anything new is added to the pile 4. Create Task files the work with the shorthand that sets its day, label, and estimate at once 5. Set Reminders schedules the nudge, which Marvin currently delivers to mobile only 6. Get Today Items confirms the task landed on the day it was meant to land on 7. The operator reviews anything the agent proposes to write through the raw document route ## What This Integration Enables Amazing Marvin is the task manager you configure rather than adopt. Its strategies mean no two accounts behave alike, which is exactly why an agent working against it should feed and read the system rather than reorganize it. The most useful thing a flow can do here is take capture and scheduling off the operator entirely, then hand back a day's plan the operator still gets to argue with. FlowRunner agents create tasks, projects, and events, read the day's scheduled and due items, walk categories and labels, start and stop time tracking, record habits, read goals, move reward points, and set reminders. Marvin marks several of these operations as experimental in its own documentation, and this connector carries that marking through rather than smoothing it over, because a flow author deciding whether to depend on an operation deserves the vendor's own confidence level. Two further facts belong in the design rather than in a footnote. Calendar events created through the API reach the user's own calendar only once a Marvin client is running, because that synchronization happens on the client. And reminders currently go to mobile devices only, so a reminder set by a flow will not appear on a desktop. The connector also splits its credentials the way Marvin does: an ordinary API token for the everyday operations, and a separate full-access token that only the raw document operations and the raw habit read will accept. FlowRunner refuses locally, with a clear message, when a full-access operation is called without the token it needs, rather than sending a call that will be rejected. ### Without FlowRunner **Capture happens twice**: Work arrives in one system and gets retyped into the personal one, or does not arrive at all **The day is planned blind**: Today's plan is built without knowing what already slipped from yesterday **Nudges get set by hand**: Reminders exist only for the things somebody remembered to set a reminder for ### With FlowRunner **Requests file themselves**: Inbound work reaches the task manager with its date, label, and estimate already set **Planning starts from the overdue list**: The agent reads what is due and what rolled over before proposing what the day should hold **Follow-ups are scheduled by rule**: Reminders come from the same rule every time rather than from whoever thought of it ## Use Case Scenarios ### An inbox that becomes a plan Requests arrive in a shared mailbox monitored through [Gmail](https://flowrunner.ai/integrations/gmail-service). The agent classifies each one, discards what is already handled, and calls Create Task for the rest. The title is written as a single string using Marvin's own shorthand, so the scheduling, the label, and the estimate are all set by one well-formed sentence rather than by four fields. Before it writes anything it calls Get Due Items, because a day already carrying eight overdue items should not silently receive twelve more. What it cannot resolve, it leaves in a short list for the operator to place. ### A weekly review the operator does not have to assemble On Friday the agent calls Get Categories and Get Labels to learn the account's own vocabulary, Get Children with the unassigned parent to read the inbox, and Get Task Times across the week's completed work to see where the hours actually went. Get Goals and Get Kudos supply the longer arc. The result is a single review page written to [Notion](https://flowrunner.ai/integrations/notion), with the estimate against actual time for each project and the items that have rolled over more than twice called out by name. The operator reads it and decides what to drop. The agent does not drop anything. ### Focus time protected by the calendar The agent reads Get Today Time Blocks and Get Today Items to see what the day is meant to contain, then compares it to the operator's real calendar in [Google Calendar](https://flowrunner.ai/integrations/google-calendar). Where a block of deep work is about to be eaten by meetings, it posts the conflict to [Slack](https://flowrunner.ai/integrations/slack) with the specific tasks at risk. If the operator agrees to move something, Track Task starts the clock when the block begins and stops it when the block ends, so the estimate for next time comes from measured work rather than memory. ## Human-in-Loop Highlight Four of these operations read and write documents in Marvin's underlying database directly, past the rules the named operations follow, and Marvin's own documentation says to be careful with them. Delete Document is the sharp end: Marvin's trash is client-side only, so a document removed through the API never reaches the trash and cannot be restored from it. Reset Reward Points sits in the same category for a different reason, since it permanently erases the whole earn and spend history and sets the balance to zero. So a FlowRunner agent working an account never reaches for the raw route on its own. It stops: "Cleaning up the duplicate project would need Delete Document on three records. Marvin's trash is client-side, so these will not be recoverable from the app afterwards. Here is what each record contains. Delete, or archive them with the named operations instead?" The operator answers, and everything else in the flow keeps running unattended. This is the [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord) applied to a personal system: the agent handles the volume and pulls the cord at the one operation the vendor itself warns about. 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 32 actions ### Account and connection 3 - **Test Credentials** Checks the configured tokens without reading any data. Marvin marks this operation stable. - **Get Account** Returns information about the Marvin account the tokens belong to. - **Get Kudos** Returns the account's Marvin Kudos, its level, and how many remain. Kudos are Marvin's own encouragement counter, awarded for finishing things. ### Creating work 4 - **Create Task** Creates a task. The title is parsed for Marvin's own shorthand unless autocomplete is turned off, which is how one string sets the schedule, the labels, and the estimate together. The star and frog fields are numbers standing for a color and a size rather than flags. - **Mark Task Done** Marks a task done. Marvin marks this endpoint experimental, and it needs a time zone offset because which day the completion counts toward depends on it. - **Create Project** Creates a project. A project takes a priority of low, mid, or high where a task takes a colored star, so these are different fields with different values. - **Create Event** Creates a calendar event. Marvin marks this experimental and notes that calendar synchronization happens on the client, so an event created through the API reaches the user's own calendar only once a Marvin client is running. ### Reading the day 7 - **Get Today Items** Returns the tasks and projects scheduled for a day, including anything rolled over or auto-scheduled when the account has that turned on. Marvin marks it stable. - **Get Due Items** Returns the open tasks and projects due on a day or earlier, which is the overdue list rather than the scheduled one. Marvin marks it stable. - **Get Today Time Blocks** Returns a day's time blocks. Marvin marks this experimental. - **Get Children** Returns everything sitting under a category or project. Passing the unassigned parent reads the inbox. Marvin marks it experimental. - **Get Categories** Returns every category and project in the account, which is how a flow learns the account's own structure rather than assuming one. Marvin marks it stable. - **Get Labels** Returns every label in the order the account sorts them. Marvin marks it stable. - **Get Goals** Returns the account's goals. Marvin marks it stable. ### Time tracking 3 - **Get Tracked Task** Returns the task being tracked right now, or nothing when the timer is stopped. - **Track Task** Starts or stops time tracking on a task. - **Get Task Times** Returns the recorded time for a set of tasks, up to one hundred in a call. ### Habits 3 - **List Habits** Returns every habit with its full history. The raw form returns complete habit objects and requires the full-access token. Marvin marks this experimental. - **Get Habit** Returns one habit with its full history. Marvin marks this experimental. - **Update Habit** Records a habit, undoes the last recording, or rewrites its history. Supplying a history replaces the whole record of that habit, while a value with a time adds a single entry. Marvin marks it experimental. ### Reward points 4 - **Claim Reward Points** Awards reward points for finishing something. Points can be awarded outside any task by naming the manual target. - **Unclaim Reward Points** Takes back reward points awarded for a task, for when it was marked done by mistake. - **Spend Reward Points** Spends reward points, which is what redeeming a reward does. - **Reset Reward Points** Permanently deletes the whole earn and spend history and sets reward points back to zero. There is no undo, which is why it belongs behind a person. ### Reminders 4 - **Get Reminders** Returns every reminder currently scheduled. - **Set Reminders** Schedules one or more reminders. Marvin currently pushes reminders to mobile devices only, so one set from a flow will not appear on a desktop. - **Delete Reminders** Removes the named reminders. - **Delete All Reminders** Removes every scheduled reminder on the account. ### Raw documents 4 - **Get Document** Returns any document in Marvin's underlying database by identifier. It is the escape hatch for anything the named operations do not cover, and Marvin marks it stable. - **Create Document** Creates a raw document in Marvin's database, writing past the rules the named operations follow. Marvin's own advice is to be careful with it, and the named create operations are the better default. - **Update Document** Changes any document in Marvin's database through a list of setters. It requires the full-access token, and Marvin's own advice is to be careful with it. - **Delete Document** Deletes a document from Marvin's database. Marvin's trash is client-side only, so a document deleted through the API does not reach the trash and cannot be restored from it. ## Frequently Asked Questions ### What can FlowRunner do with Amazing Marvin? FlowRunner agents can run Test Credentials, Get Account, and Get Kudos in Amazing Marvin, plus 29 more actions. ### Does connecting Amazing Marvin to FlowRunner require OAuth? No. Amazing Marvin connects to FlowRunner with an API key, no OAuth flow required. ### Can Amazing Marvin trigger a FlowRunner workflow automatically? Amazing Marvin doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Amazing Marvin?** This integration exposes Amazing Marvin 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/amazing-marvin. Site index: https://flowrunner.ai/llms.txt