{
  "name": "service-call",
  "title": "External Service Integrations",
  "description": "Connect and use external services - Google, Telegram (tested); Slack, GitHub, Todoist, Notion (experimental)",
  "guid": "sk_plat_svcc",
  "category": "Integrations",
  "requiredTools": [
    "service_call",
    "connector_manage"
  ],
  "content": "# External Service Integrations\n\n## Overview\nGipity connects to external services so you can manage tasks, send messages, access APIs, and more - all through natural conversation. Authentication is handled automatically once a service is connected.\n\n## Built-in Providers\n\n### Google (tested)\n- Search and read emails, send and reply\n- List, create, update, and delete calendar events\n- Access Drive, Sheets, and other Google APIs\n- *Use the dedicated Gmail/Calendar tools for common operations - they have better formatting and error handling*\n\n### Telegram (tested)\n- Receive and respond to messages via Telegram bot\n\n### Slack (experimental)\n- OAuth2 via `https://slack.com/api`\n- User provides their own Slack app credentials (client ID + secret)\n\n### GitHub (experimental)\n- OAuth2 via `https://api.github.com`\n- User provides their own GitHub OAuth app credentials\n\n### Todoist (experimental)\n- API key auth via `https://api.todoist.com`\n- User provides their Todoist API token\n\n### Notion (experimental)\n- OAuth2 via `https://api.notion.com/v1`\n- User provides their own Notion integration credentials\n\n> **Note:** \"Experimental\" means the provider's OAuth/API-key URLs and base URLs are seeded in the database, and the generic `service_call` proxy should work in theory - but the end-to-end flow (connect → token → real API call → response) has not been verified against a real account. If you try one of these and it works (or doesn't), let us know.\n\n## Additional Providers\nThe platform supports registering new providers at runtime via the skill store (`skill_store_search` / `skill_store_install`). Any service with an OAuth2 or API-key auth model can be added.\n\n## Connecting a Service\nTo use a service, the user needs to connect it first. Ask the user to connect the service they want to use - this opens an authorization flow (OAuth) or asks for their API key, depending on the provider.\n\nFor OAuth services, the user provides their own OAuth app credentials (client ID and secret from the provider's developer portal). This is a one-time setup per service.\n\nAPI key services just need the user's API key.\n\n## Checking Status\nYou can check which services are connected and view their permission settings.\n\n## Permissions\n- **Read operations** (GET): allowed once a service is connected\n- **Write operations** (POST/PUT/PATCH/DELETE): require approval by default\n- Users can adjust permission settings per service\n\n## Tips\n- For Google Gmail/Calendar, prefer the dedicated tools - they have better formatting and error handling\n- Always check the provider's API documentation for correct paths and parameters\n- Responses are JSON by default; large responses are truncated at 50KB\n\n---\n\n## Implementation Reference\n- Connect services: `connector_manage` tool (actions: connect, disconnect, list, status, permissions, providers)\n- Make API calls: `service_call` tool (provider, method, path, params, body)\n- Auth is injected automatically - never include auth headers\n- Provider base URLs are locked - only the path portion is configurable\n"
}