ワンクリックで
onboarding
// Interactive onboarding — checks auth, learns what the user wants to automate across their apps, and connects the right ones. Use when the user is new to Composio, says "get started", or asks what apps they can connect.
// Interactive onboarding — checks auth, learns what the user wants to automate across their apps, and connects the right ones. Use when the user is new to Composio, says "get started", or asks what apps they can connect.
Generates comprehensive company activity summary across connected apps — Slack, GitHub, Notion, Linear, Gmail, and more. Use when user asks for company updates, daily summary, or what's happening across the org.
Help users operate the Composio CLI to find tools, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Trigger when the user asks about Composio tools, connections, or connectors.
Use the Composio Connect MCP server to interact with 1000+ apps — GitHub, Slack, Notion, Gmail, Linear, Jira, and more. Composio manages auth, permissions, and intelligent tool routing. Trigger when the user asks to connect an app, execute an action on an external service, or work with connectors.
Interactive onboarding — checks CLI install and auth, learns what the user wants to automate across their apps, and connects the right ones. Use when the user is new to Composio, says "get started", or asks what apps they can connect.
Generates comprehensive company activity summary across connected apps — Slack, GitHub, Notion, Linear, Gmail, and more. Uses the composio CLI to fetch data. Use when user asks for company updates, daily summary, or what's happening across the org.
| name | onboarding |
| description | Interactive onboarding — checks auth, learns what the user wants to automate across their apps, and connects the right ones. Use when the user is new to Composio, says "get started", or asks what apps they can connect. |
Interactive flow to get the user set up. Use AskUserQuestion at every decision point.
Try a lightweight MCP tool call to verify the MCP server is connected and the user is signed in.
Use AskUserQuestion:
What would you like to automate or speed up with your apps? For example:
- Team updates — post summaries to Slack, send status emails, notify channels
- Task tracking — create and update issues in Linear, Jira, or Asana from conversations
- Email management — draft replies, triage inbox, send follow-ups
- Knowledge & docs — save notes to Notion, search across docs, update wikis
- Daily briefing — get a summary of what's happening across Slack, email, calendar, and tasks
- Scheduling — check availability, create calendar events, send invites
- Something else — just describe it and I'll figure out the right apps
Based on their answer, recommend 2-4 apps that would help. Map use cases to apps:
| Use case | Recommended apps |
|---|---|
| Team updates | Slack, Gmail |
| Task tracking | Linear, Notion |
| Email management | Gmail |
| Knowledge & docs | Notion, Google Drive |
| Daily briefing | Slack, Gmail, Google Calendar, Linear |
| Scheduling | Google Calendar, Gmail |
Use AskUserQuestion to confirm:
Based on what you described, I'd recommend connecting [apps]. Sound good, or would you like to add/change any?
Then for each app, try a read-only tool call to check if it's already connected:
GITHUB_GET_THE_AUTHENTICATED_USERGMAIL_FETCH_EMAILS with { max_results: 1 }SLACK_LIST_CHANNELSNOTION_SEARCH_NOTION_PAGE with { query: "" }LINEAR_LIST_LINEAR_TEAMSGOOGLECALENDAR_LIST_EVENTSIf connected, confirm it. If not, the MCP server will provide an OAuth link — share it with the user and retry after they complete the flow.
After connecting, use AskUserQuestion to present personalized examples based on their use case and connected apps. Tailor the examples to what they said they wanted to do in Step 2 — don't just list generic capabilities.
End with: "What would you like to try first?"