Usage & Design
Usage & Design
One-Pager Library → Concept docs for each AI Employee (purpose, skills, guardrails, workflows).
Data formats & I/O → What inputs/outputs AI Employees can handle.
One-pager Library
See What is an AI Employee. I think it's better include it in here and reference it.
Data Formats & Input/Output
AI Employees process structured and unstructured data depending on the skill being used. Inputs define what they can accept, and outputs define what they produce back into Motion.
Inputs (from users)
Natural language text (chat prompts, task instructions).
Structured fields (task title, due date, priority, assignee).
Linked references (Docs, projects, tasks, or external connections).
Inputs (from integrations)
Calendar events (title, time, attendees).
Email metadata (sender, subject, body preview).
File metadata (name, size, type, link).
Outputs (in Motion)
Tasks (with title, due date, priority, ETA).
Projects (with milestones, stages, deadlines).
Docs (drafted text, summaries, or structured notes).
Comments or status updates (logged in chat or activity feed).
Outputs (to integrations)
Calendar events (scheduled or rescheduled).
Notifications/messages (e.g., Slack, email).
Updated records in connected systems via approved skills.
Unsupported formats
Images, audio, or video files are not directly processed.
Binary attachments are stored as links/metadata, not parsed.
Last updated
Was this helpful?