Integrations

Aicoo integrations fall into two groups:

1. Internal integrations are Aicoo-owned primitives your product can build on top of: memory, notes, todos, share links, conversations, tools, heartbeat, Skills, and scoped agent access.
2. External integrations connect Aicoo to another system: calendar, email, messaging, repos, docs, CRMs, project tools, or your own application.

This distinction matters for developers. Internal integrations define what Aicoo can do. External integrations define where Aicoo can act.

Internal Integrations

Internal integrations are available as Aicoo product and API surfaces.

Workspace OS

Use Aicoo OS when your product needs durable state.

• Folders and notes: Sync project briefs, research, user profiles, submission packets, meeting notes, or handoff docs.
• Todos: Create, search, edit, and complete tasks that Aicoo can track over time.
• Memory: Search past decisions, preferences, and reusable context.
• Snapshots: Save point-in-time versions before editing important notes.

Shared Agent Access

Use shared agent links when another person should talk to a scoped version of the user's Aicoo.

• Scoped links: Limit a guest to selected folders, notes, tools, or access levels.
• Guest conversations: Let collaborators ask questions without receiving the owner's whole workspace.
• Partner workflows: Create links for hackathon teams, recruiting profiles, customer records, research projects, or partner intake.

Skills

Use Aicoo Skills when an agent or local developer workflow needs to work with Aicoo directly.

• Repo context: Connect a repo or workspace to Aicoo so implementation notes, decisions, and docs can be synced.
• Agent memory: Let Codex, Claude Code, or similar agents search and update Aicoo context during a build.
• Operational actions: Create notes, edit notes, save snapshots, create share links, and keep the user's agent current.

Tools and Heartbeat

Use the tools layer when your workflow needs controlled action.

• Tool discovery: Fetch available tool names and schemas before execution.
• Tool execution: Call approved tools for notes, todos, calendar, email, messaging, search, and other enabled domains.
• Heartbeat: Run recurring or background coordination jobs that use Aicoo context.

External Integrations

External integrations connect Aicoo to systems outside Aicoo. The connection model depends on the surface: OAuth, API keys, MCP or Composio-style tool routing, or a server-to-server workflow built by the partner product.

Communication Channels

• iMessage: Planned mobile capture and reply surface. Status: to be released.
• Email: Gmail or Outlook-style inbox workflows for search, drafting, triage, and follow-up tracking.
• Team chat: Slack, Teams, or similar channels for summaries, reminders, and team coordination.

Calendar and Meetings

• Calendar: Google Calendar, Outlook Calendar, or similar systems for availability, event search, scheduling, and reminders.
• Meetings: Zoom, Google Meet, Teams, or transcript providers for meeting summaries, action items, and follow-up notes.

Developer and Repo Systems

• Repos: GitHub, GitLab, or a local git workspace for issues, PRs, docs, and implementation handoffs.
• Agent IDEs: Codex, Claude Code, and other local agents can use Aicoo Skills to connect repo context to Aicoo.
• CI and project logs: Build failures, deployment notes, and debugging summaries can be synced into Aicoo as durable context.

Knowledge and Workspace Apps

• Docs: Google Drive, Google Docs, Notion, Confluence, or similar knowledge bases.
• Files: PDFs, spreadsheets, decks, reports, and research material can become searchable Aicoo context.
• Search: Web or internal search tools can be exposed as approved tools when the workflow requires fresh retrieval.

Project, Customer, and Business Systems

• Project management: Linear, Jira, Asana, Trello, or similar systems for task and status sync.
• CRM and support: Salesforce, HubSpot, Intercom, Zendesk, or partner support tools for customer context and follow-up.
• Custom platforms: Hackathon platforms, learning portals, recruiting products, community tools, or internal dashboards can embed Aicoo through the API.

Choosing the Right Model

• Use internal integrations when your product needs Aicoo-owned state, scoped agent access, durable memory, todos, or tool execution.
• Use external integrations when Aicoo needs to read from or act inside another vendor system.
• Use Skills when the work starts from an agent, repo, or local developer environment.
• Use the API when your product backend should create Aicoo workflows for users.
• Use shared links when a human guest needs a safe, scoped way to talk to an agent.

For developer implementation, start with Build with Aicoo + API. For endpoint details, open the API Reference.