feat(google-tasks): add Google Tasks integration

[waleedlatif1]

Summary

• Add Google Tasks integration with full OAuth support
• Tools: create, list, get, update, delete tasks + list task lists
• Block with operation dropdown, credential selector, conditional fields
• OAuth config in auth.ts, oauth.ts, types.ts, and scope description in oauth-required-modal
• Auto-generated docs

Type of Change

• New feature

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 26, 2026 5:49am

[greptile-apps]

Greptile Summary

Adds a full Google Tasks integration with OAuth support, covering 6 operations: create, list, get, update, delete tasks, and list task lists. The implementation follows the established integration pattern (tools + block + icon + OAuth config + docs) and is consistent with existing Google integrations like Google Calendar and Google Sheets.

• Tools: 6 tool files under tools/google_tasks/ with proper type definitions, request builders, and response transformers hitting the Google Tasks REST API v1 directly
• Block: Operation-based dropdown with conditional subblocks for each operation type, credential selector with basic/advanced modes
• OAuth: Full OAuth2 config in auth.ts, oauth.ts, and types.ts with the tasks scope
• Docs: Auto-generated documentation with input/output tables for all operations
• Style: All tool files use relative imports (./types, ./create) instead of absolute imports (@/tools/google_tasks/types), which violates the project's import style guide — existing Google Calendar tools use absolute imports throughout

Confidence Score: 4/5

• This PR is safe to merge — the integration is functionally correct with only style-level issues to address.
• The integration logic is correct: API endpoints, request methods, parameter handling, and response transforms all follow the Google Tasks REST API v1 spec. OAuth configuration is properly set up. The only issues are style violations (relative imports instead of absolute, minor import ordering in registry). No logic bugs or security issues found.
• The tools/google_tasks/ directory needs import style fixes (relative → absolute imports) across all 7 files.

Important Files Changed

Filename	Overview
apps/sim/blocks/blocks/google_tasks.ts	Block config for Google Tasks with 6 operations. Uses duplicate subblock IDs for create/update fields (consistent with existing patterns like Google Sheets). Params function correctly strips operation before passing to tools.
apps/sim/tools/google_tasks/create.ts	Create task tool with proper POST to Tasks API. Uses relative imports instead of absolute (style violation). Logic is correct.
apps/sim/tools/google_tasks/delete.ts	Delete task tool correctly handles 204 No Content response. Uses params?.taskId for the response, which properly returns the actual task ID.
apps/sim/tools/google_tasks/list.ts	List tasks tool with comprehensive query parameter support for filtering. Clean implementation.
apps/sim/tools/google_tasks/update.ts	Update task tool using PATCH method. Only includes changed fields in request body, which is correct.
apps/sim/tools/google_tasks/types.ts	Well-structured type definitions with separate interfaces per operation and proper response types extending ToolResponse.
apps/sim/tools/google_tasks/index.ts	Barrel export file using relative imports instead of absolute imports (style violation).
apps/sim/blocks/registry.ts	Registration added but import ordering is not alphabetical (google_tasks placed before google_maps).
apps/sim/lib/auth/auth.ts	OAuth provider config for google-tasks follows the same pattern as other Google integrations. Scopes, discovery URL, and getUserInfo handler are correct.
apps/sim/lib/oauth/oauth.ts	OAuth provider config entry added correctly with proper icon, scopes, and service definition.

Sequence Diagram

sequenceDiagram
    participant U as User/Workflow
    participant B as Google Tasks Block
    participant T as Tool (create/list/get/update/delete)
    participant API as Google Tasks API v1

    U->>B: Select operation + fill fields
    B->>B: tools.config.tool(params) → select tool
    B->>B: tools.config.params(params) → coerce types
    B->>T: Execute with resolved params
    T->>T: Build URL, headers, body
    T->>API: HTTP request (POST/GET/PATCH/DELETE)
    API-->>T: JSON response
    T->>T: transformResponse → structured output
    T-->>B: { success, output }
    B-->>U: Block output (id, title, status, etc.)

Loading

_{Last reviewed commit: a1ead79}

[greptile-apps]

_{20 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[greptile-apps]

_{20 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}