Connect AI & Automations
Start with the built-in AI Planner, configure an MCP-compatible assistant, or build a custom workflow with the Planner API. Your plan stays the source of truth.
A real plan, not a mock integration
Create a revocable key in WeekOrbit, connect a compatible agent, and let the workflow read or update the same plan you can inspect in the app.
Connection options
Each path reaches the same planning foundation. Choose by how much control and setup your workflow actually needs.
No external setup
Turn goals and constraints into a weekly plan inside WeekOrbit, without configuring another client or maintaining integration code.
Configure, do not code
Give a compatible AI assistant structured planning tools so it can work with your planner through explicit, purpose-built actions.
Build a custom workflow
Connect scripts, agents, and automation services when you need deterministic control over how planning data moves.
Shared planning foundation
The connection layer is useful because it works with structured planning data, not another disconnected task list.
Bring the current week and relevant task context into an assistant or automation.
Move from a suggestion to a structured task while keeping the planner as the record.
Work with groups and planning structure instead of flattening everything into plain text.
Use planner data in recurring reviews, triage routines, and other repeatable operations.
Safety and control
AI access should be understandable and reversible. Start narrow, test the workflow, and expand only when the value is proven.
Read and write through the planner so assistants, automations, and humans do not drift into separate task copies.
Store keys outside prompts and source code, give each integration only the access it needs, and revoke access when it is no longer used.
Design for rate limits, clear error handling, and human review where a client or workflow can change important planning data.
Where connection pays off
The best workflows remove repetitive translation between tools while leaving prioritization and commitment visible to the person doing the work.
Let an assistant inspect the current plan, identify overload, and help turn decisions into structured tasks.
Convert selected items from another system into planner tasks without maintaining a second planning backlog.
Collect the week’s task state for a consistent review, then keep follow-up actions attached to the plan.
Connect a trusted script or service when a stable, repeatable process needs direct planner access.
Validate the planning workflow first. MCP and the REST API are ready when an external assistant or automation creates real leverage.