feat(microsoft-tools): added planner, onedrive, and sharepoint#840
feat(microsoft-tools): added planner, onedrive, and sharepoint#840waleedlatif1 merged 23 commits intostagingfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Greptile Summary
This PR introduces a comprehensive Microsoft Graph API integration that adds three new productivity tools to the platform: Microsoft Planner for task management, OneDrive for cloud file storage, and SharePoint for site and page management. The implementation extends the existing Microsoft OAuth infrastructure to support these new services with appropriate scopes and authentication flows.
The changes follow established architectural patterns throughout the codebase:
- Tool Layer: Each service includes complete CRUD operations (create, read, list) implemented as individual tools following the
ToolConfigpattern used by existing integrations like Google Drive and GitHub - Block Layer: New block configurations provide user-friendly interfaces with operation-based conditional fields, file selectors, and OAuth credential management
- API Layer: REST endpoints handle authentication, token refresh, and Microsoft Graph API communication using the existing OAuth infrastructure
- Type Safety: Comprehensive TypeScript interfaces define request/response structures, maintaining consistency with other tool integrations
The Microsoft Graph API integration leverages existing Microsoft OAuth providers (established for Teams and Excel) while adding service-specific scopes: Group and Tasks permissions for Planner, Files permissions for OneDrive, and Sites permissions for SharePoint. The implementation reuses established patterns like dual parameter approaches (UI selectors + programmatic IDs), standardized response transformation, and consistent error handling.
Key architectural decisions include treating these as separate OAuth services under the Microsoft provider umbrella, extending the unified Microsoft file selector component to handle all three services, and maintaining backward compatibility with existing Microsoft integrations. The tools integrate seamlessly with the platform's workflow engine, providing users with expanded automation capabilities across Microsoft's productivity suite.
Confidence score: 2/5
- This PR contains several critical implementation issues including duplicate field IDs, missing implementations, and type safety concerns that could cause runtime failures
- Score reflects serious code quality issues including incomplete functionality (empty get_content file), duplicate field definitions that will cause conflicts, and excessive use of
anytypes - Pay close attention to
apps/sim/blocks/blocks/onedrive.tsfor duplicate fileName field IDs,apps/sim/tools/onedrive/get_content.tswhich is empty, and type safety issues throughout the OneDrive and Planner implementations
30 files reviewed, 35 comments
...w-block/components/sub-block/components/file-selector/components/microsoft-file-selector.tsx
Outdated
Show resolved
Hide resolved
a155074 to
7e322bc
Compare
728ab37 to
8140a5a
Compare
…udioai#840) * first push * feat: finished onedrive tool * added refresh * added sharepoint with create page * finished sharepoint and onedrive * planner working * fixed create task tool * made read task better * cleaned up read task * bun run lint * cleaned up simstudioai#840 * greptile changes and clean up * bun run lint * fix simstudioai#840 * added docs simstudioai#840 * bun run lint simstudioai#840 * removed unnecessary logic simstudioai#840 * removed page token simstudioai#840 * fixed docs and descriptions, added advanced mode simstudioai#840 * remove unused types, cleaned up a lot, fixed docs * readded file upload and changed docs * bun run lint * added folder name --------- Co-authored-by: Adam Gough <[email protected]> Co-authored-by: Adam Gough <[email protected]> Co-authored-by: waleedlatif1 <[email protected]>
Description
Added planner, onedrive, and sharepoint with the Microsoft graph API
Type of change
How Has This Been Tested?
Please see the video for testing
Checklist:
bun run test)Security Considerations:
Screen.Recording.2025-08-01.at.10.33.16.AM.mov