Motion

Calendar writes, meetings created in outside services and mail sent on the user's behalf are all documented. The auto scheduler writes to the customer's calendars: "Turn all of your calendar accounts - Outlook, Google, or iCloud - into a single interface", with tasks timeblocked onto those calendars and the plan rewritten "dozens of times a day". Creating and moving events in a customer's Google or Outlook calendar over OAuth is the canonical case of authenticated action in an outside system.

Meetings are created in third party services: "Schedule and join Zoom calls directly from Motion", and the same for Teams and Meet. Outbound mail goes out on the user's behalf: "After a meeting, Motion can send a follow-up email to all attendees with summaries, notes, and action items", plus custom meeting reminders and rescheduling requests. The AI Employees pages state the intent directly: "have AI Employees take actions in other tools." Custom connections are open too, through a documented REST API with full create, read, update and delete, plus Zapier into thousands of applications.

How many connectors Motion has is unclear. Marketing says "hundreds more" integrations; the help center says Motion comes with "two built-in integrations" and that the Zapier route runs only into Motion. Both are about capture breadth: the help center counts Task from Email and Siri Shortcuts as its two built in capture integrations and does not treat calendars as integrations at all, so it does not contradict calendar write back. The actions themselves are not in doubt.

Sourceusemotion.com homepage and usemotion.com/features/integrationsread 2026-09-12

Two independent orchestration layers run in Motion, a scheduler that keeps replanning and a builder that turns an SOP into running work, with AI Employees on top.

The auto scheduler is a continuous unattended loop: it takes all projects and tasks with "their priorities, dependencies, deadlines, durations" and "builds a perfect plan that optimizes itself hundreds of times a day, automatically", replanning whenever anything changes and warning "days or weeks in advance" when a task is at risk. Replanning a whole team's work around its dependencies is a real scheduling problem with many steps and constraints.

The AI Workflow Builder converts a document into executable work in a published three step chain: an SOP drafted in AI Docs, turned by the AI Project Manager into "a step-by-step workflow with action items", then instantiated as a project with tasks "automatically assigned" to the right people by the AI Task Planner.

Each stage hands off to the next, and the output is running work. The project layer runs unattended too: Motion "keeps work moving", "automatically updating statuses, assigning next steps, and flagging delays". AI Employees sit on top, configurable agents that run recurring workflows without prompting.

Sourceusemotion.com homepageread 2026-09-12

Search and answers run over the customer's own workspace in Motion, a store that grows on its own as meetings and notes are filed. A named retrieval product ships: "AI Search Assistant", which "instantly finds anything - docs, notes, project, task, communication", with AI Chat as the conversational surface over the same corpus and its own feature page.

The corpus is the customer's own and is maintained rather than assembled per run: "Motion includes your docs, tasks, projects, and calendar", "which gives it the context to hyper personalize everything it produces for you. You don't need to spend hours writing prompts and giving it context", with the stated capabilities "search across all your notes and docs instantly" and "Ask anything. Motion finds the answer fast."

It grows without manual capture, which makes it a standing structure: the AI Meeting Notetaker turns summaries, notes, recordings and transcripts automatically into Motion docs, the Docs Assistant finds tasks buried "five folders deep" in old notes, and users build wikis, processes and pages in the same store. Grounding feeds action as well as answers: the AI Workflow Builder converts an SOP doc into a runnable workflow. The corpus stops at the customer's Motion workspace, and no ingestion of outside documents is described.

Sourceusemotion.com homepageread 2026-09-12

Agents in Motion are bounded and their output can be inspected, but there is no approval gate before they act. The scheduler's output is fully visible and directly overridable, so every placement is inspectable and reversible before it matters, and a toggle on each task lets a user decide item by item whether the agent may place it.

The Notetaker keeps the human in the loop on its own output ("Still want to take your own notes? Your notes get combined with AI"), and project generation expects "a quick review and final polish". AI Employees are bounded by a role definition written in plain language, and docs carry visibility control on each item: "set docs as private to you or viewable to your team."

Nothing checks an AI Employee at run time. There is no approval gate on its actions and no confirmation step before it writes to a calendar or sends a follow up email, and no administrator setting covers policy, risk or escalation. The vendor's own framing explains why: agents "execute recurring workflows without prompting", which is the point of the feature and also why oversight sits at configuration time rather than run time. That matters because Motion takes authenticated action in the customer's calendar and mail with nothing documented to stop those actions.

Sourceusemotion.com homepageread 2026-09-12

A SOC 2 Type II audit with an unqualified opinion backs Motion's security, but no access controls are described for the customer's own workspace. The audit is solid: NexusBird, Inc (dba Motion) "successfully completed the AICPA Service Organization Control (SOC) 2 Type II audit", with Prescient Assurance named as the auditor and an unqualified opinion stated. Third party penetration testing runs every year, and a security kit holding the SOC 2 report, the penetration test report and policies is available on request, with questionnaire answers as well.

The access controls described are Motion's own staff controls. Under Access Security the page reads "Access to cloud infrastructure and other sensitive tools are limited to authorized employees who require it for their role. Where available we have single sign-on (SSO), 2-factor authentication (2FA) and strong password policies." That is Motion's staff signing in to Motion's own tools, and so are least privilege IAM and quarterly access reviews of all team members.

Password managers on company laptops and background checks are staff controls too. Nothing gives the buyer an access surface: there is no customer single sign-on, SAML or SCIM, no role based access over the customer's own workspace, and no admin console or audit log the customer can see. The heading Access Security invites the misread and the body refuses it.

Sourceusemotion.com/securityread 2026-09-12

Reporting on the work is clear in Motion, but there is no audit trail of the agents themselves. AI Business Intelligence predicts "the ETA of every project based on your team's capacity", alerts "as soon as a project is off-track", and reports "how much over or under capacity an employee is". It also supplies "intelligent dashboards to visualize where your bottlenecks are", with "automatic reports for every project". The scheduler's own output is the visible calendar, so what was planned can always be inspected.

Reporting is not auditing, though: seeing what happened is not reconstructing why. Every artifact above reports on the work, and nothing records what the agent did. There is no audit log and no attribution separating an AI Employee's action from a human's, and no decision trail shows which data an agent drew on.

Retention and export are not described either. For a product sold as autonomous digital employees, attribution at the agent level is the gap that matters most. The security page's "we actively monitor and log various cloud services" describes Motion's own infrastructure monitoring, which the buyer never sees.

Sourceusemotion.com homepage and usemotion.com/securityread 2026-09-12

No agent memory is documented; what persists is the workspace itself. Nothing describes a memory scope for each user, a published lifetime or purge path, or a way to read and write agent state, and nothing says an AI Employee remembers preferences or priorities between runs. Recall of earlier conversations is not described either.

Tasks and projects, docs and notes, and meeting records held indefinitely are the product's data model, the business record itself rather than a store the agent keeps; the auto scheduler's plan state is likewise the artifact the product exists to produce. The homepage's "gets smarter each day you interact with it" is learning absorbed into the product rather than memory a customer can see, and personalization by "harnessing all of your data" is retrieval over the workspace.

The one retention statement points the other way: the security page says Motion "may temporarily store the inputs and outputs exchanged with our LLM providers, strictly limited in duration, for performance optimization and debugging." Short debug retention is the opposite of a memory layer. The homepage, the security page and the docs site say nothing more.

Sourceusemotion.com/security and usemotion.com homepageread 2026-09-12

Motion stores all customer data in a single US region in Iowa and states that storage only in the EU cannot be requested. The security page: "All customer data is stored on Google Cloud Platform with encryption-at-rest and encryption-in-transit. Data is stored in Google's Central-1 region, based in Iowa.

Data is not stored in the European Union, and at this time unfortunately it is not possible to request your data to only be stored in the European Union." It repeats elsewhere: "All of our data is hosted on Google Cloud Platform (GCP) databases. These databases are all located in the United States."

The vendor names the region and refuses the choice in the same sentence, which leaves no doubt. No on premises option, private VPC or single tenant tier is described, so on an enterprise residency option the vendor's own answer is no.

Sourceusemotion.com/security Data Storage and Cloud Security sectionsread 2026-09-12

Motion ships named prebuilt AI Employee roles, each with its own page, on top of a composable skills layer customers can extend. AI Project Manager, AI Executive Assistant and AI SDR each hold their own page under usemotion.com/ai-employees/, alongside sales, support, marketing, HR and research roles.

A page on use cases names a specific shipped agent, Spec, who "aggregates security advisories, tracks compliance updates, surfaces vendor changes" for IT service providers. An SDR and an executive assistant do unrelated jobs for different buyers, so removing one leaves the others whole; these are not tiers of one assistant.

Packaging runs at three levels. Underneath the roles sits a composable AI Skills layer. Above them, customers author their own: "Build skills and AI Employees entirely with natural language, like how you'd instruct human employees", and "Type what you need your new employee to do. Motion will build and onboard your new AI Employee." And AI Workflows turns the customer's own SOP documents into templates ready to run. Custom AI Employees built by Motion's "top AI engineers and implementation team" are services work inside an engagement rather than a packaged product.

Sourceusemotion.com/ai-employees pages and usemotion.com homepageread 2026-09-12

Work reaches Motion's agents in many ways without anyone invoking them, but output goes only to the customer's own people. Tasks arrive from anywhere: "Create tasks in Motion from anywhere", to "forward Gmail/Outlook/iCloud emails, turn Zoom/Meet/Teams meetings or Slack/Teams messages into tasks, or tell Siri to add tasks via voice command."

Calendar events arriving or moving restart the planner, which will "automatically re-plan your day whenever anything changes", and deadline and capacity changes drive warnings when work is at risk. The Notetaker fires when meetings start, AI Employees run recurring workflows without prompting, and Zapier delivers third party events. Email forwarding is a genuine inbound queue.

Outbound reach is missing. Delivery stays with the customer's own people: the workspace and calendar, notifications in the desktop and mobile apps, and follow up mail to meeting attendees. There is no channel facing the customer's own customers, no messaging surface to third parties, and no voice or web surface, because Motion is an internal work system rather than a sales and marketing one. That is a property of the product rather than a defect, but it still limits where Motion can act.

Sourceusemotion.com homepage and usemotion.com/features/integrationsread 2026-09-12

Motion names the model providers behind its AI features, OpenAI, Anthropic and Google, but the customer cannot choose among them. The security page's AI Security Policy reads "Motion leverages advanced AI capabilities, with some features powered by various large language models (LLMs), including those from trusted third-party providers such as OpenAI, Anthropic, and Google. Other Motion features, such as task auto-scheduling, utilize proprietary algorithms developed in-house."

The homepage repeats it in commercial terms: "We always use the most cutting-edge models available from Open AI, Anthropic, and other labs, fully covered as part of Motion's subscription." So routing across more than one model happens on the vendor's side, with a stated policy of moving to whatever is most current and a split between LLM features and algorithms built in house.

The customer can see which labs are used but has no say in which one runs. There is no model picker or selection per task or agent, no admin model policy, and no way to bring your own model or key. Consumption is metered as AI credits.

Sourceusemotion.com/security AI Security Policy and usemotion.com homepageread 2026-09-12

An ungated developer portal with a complete REST API reference covers Motion's own platform. The portal, docs.usemotion.com, titled Motion API Docs, carries four Cookbooks, among them Getting started and Rate limits, and an API reference organized by nine resources: Comments, Custom fields, Projects, Recurring tasks, Schedules, Statuses, Tasks, Users and Workspaces.

It covers the full lifecycle, not just read access, with create, get, list, update, move, unassign and delete on tasks; create and list on projects; add, delete and create on custom fields; and create and delete on recurring tasks. Rate limits are published as their own cookbook, the mark of a maintained interface rather than an announcement.

The homepage corroborates it: "Robust API and clear documentation to connect with all your internal or external systems. With our API, you'll be able to create, update, and manage your projects and tasks effortlessly", illustrated with a screenshot of the docs. Users generate keys themselves from Settings, so there is no access gate. Zapier's SDK over Motion's API belongs to Zapier, not Motion. No SDK or MCP server of Motion's own was found; the documented API is the extension surface.

Sourcedocs.usemotion.com and usemotion.com homepageread 2026-09-12

Scheduling output is unusually easy to inspect in Motion, but no change can be tested before it runs. The auto scheduler's output is the user's calendar, so every decision it makes is exposed by default, directly overridable and immediately checkable against what the user expected. Project ETAs against team capacity, alerts when a project goes off track and dashboards showing bottlenecks and ROI sit alongside it. The vendor also claims project generation is "over 90% accurate out of the box", with "a quick review and final polish" expected.

There is no way to try a change first. No sandbox or dry run lets a team rehearse an AI Employee before it runs recurring workflows unprompted, and there is no evaluation harness with scored test cases. Editing a skill or role definition triggers no regression check, and configurations cannot be compared side by side. Inspectable output is not a test loop. The figures of 90% accurate, 32% faster and 40% efficiency gains are the vendor's own benchmarks of its own product.

Sourceusemotion.com homepageread 2026-09-12

No browser or computer use is documented; Motion reaches other systems through programmatic connections. No hosted or local browser, desktop session or remote control of a computer appears on Motion's site, its AI Employees pages or its API documentation. Motion connects to calendars over OAuth and to Zoom, Teams and Meet natively, and everything else goes through its own REST API or Zapier, so every link is programmatic. Otherwise it acts inside its own workspace, so how often it would break when a screen changes does not arise.

A desktop app and mobile apps exist, but a native client is the vendor's own software being installed, not the agent operating someone else's screen. Siri Shortcuts is a way to capture tasks by voice on iOS, not control of the device. The full API reference, where automation of an outside interface would show up if it existed, describes none.

Sourceusemotion.com homepage and docs.usemotion.comread 2026-09-12