Support Third Party Integrations

[elie222]

Description

To enhance the functionality and user experience of Inbox Zero, we aim to implement support for various third-party integrations. This will allow users to seamlessly connect Inbox Zero with other productivity tools they use daily, creating a more comprehensive and efficient workflow.

Objectives

1. Develop a framework for integrating third-party services
2. Implement specific integrations for popular productivity tools
3. Ensure a consistent and user-friendly experience across all integrations
4. Enable the AI assistant to utilize these integrations in automated rules

Proposed Integrations

1. Task Management Tools:
   • Notion
   • Todoist
2. File Storage:
   • Google Drive
3. Calendar Service:
   • Google Calendar

Implementation Strategy

• Create a main integrations package that defines common interfaces and types for all integrations
• Each specific integration will be developed as a separate package implementing the common interface
• Develop a system for the AI assistant to discover and utilize available integrations
• Implement UI components for users to connect and manage their integration accounts
• Update the rule creation system to incorporate actions from integrations

Integration Usage with AI Assistant

The AI assistant will use integrations as follows:

1. During rule creation, offer integration actions as options (e.g., "send receipts to Google Drive")
2. When processing emails:
   • Step 1: Check if conditions are met (e.g., is it a receipt?)
   • Step 2: Execute the action using the appropriate integration (e.g., send to Google Drive)

The integration packages should provide:

• Methods for the AI to check availability and capabilities
• Core logic for executing actions (e.g., uploading files to Google Drive)
• Authentication and connection management

General Guidelines for Contributors

• Look at cal.com's integration system for inspiration on structuring the integration packages
• Implement integrations following the common interface defined in the main integrations package
• Create a new package for each integration in the packages/integrations/ directory
• Follow the naming convention: packages/integrations/[service-name] (e.g., packages/integrations/notion)
• Ensure each package has its own package.json, README.md, and appropriate TypeScript configuration
• Provide clear documentation for each integration package

Package Structure

packages/
  integrations/
    index.ts       # Exports common interfaces and types
    notion/
      package.json
      README.md
      src/
        index.ts   # Implements the common interface for Notion
    todoist/
      ...
    google-drive/
      ...
    google-calendar/
      ...

Next Steps

1. Create the main integrations package with the common interface
2. Develop the system for AI assistant to discover and use integrations
3. Implement UI components for integration account management
4. Begin implementation of individual integrations, starting with Google Drive
5. Update the rule creation system to incorporate integration actions
6. Design and implement the UI for managing integrations in the app settings

Please refer to the sub-issues for specific tasks related to each integration.

[elie222]

Worth researching projects like: https://nango.dev There are a few of these around. Don't want to recreate the wheel here. And it can be a tonne of work to support endless integrations.

[elie222]

There are a lot of others. Some mentioned here: https://www.reddit.com/r/ExperiencedDevs/comments/1c5jdvi/has_anyone_used_unified_api_solutions/

• Nango isn't actually open source even though they claim to be. And you need to pay to perform actions (writes). Even if you self-host. Could proxy to APIs though which may help a bit: https://docs.nango.dev/integrate/guides/proxy-requests-to-an-api
• Paragon - expensive - like $10k per month
• Singer: https://www.singer.io/ - Python - doesn't support Google Drive, Notion, Todoist... But may be able to get ideas from the Singer SDK. But there are more taps like this but it's read only: https://gitlab.com/hotglue/tap-notion/-/blob/main/tap_notion/client.py?ref_type=heads
• hotglue doesn't have public pricing. But they say they're connectors are open source so I'm looking deeper (https://docs.hotglue.com/introduction). Community integrations for Singer, but many are read only: https://docs.hotglue.com/connectors/notion
• Revert.dev - dead
• Panora - limited number of integrations. OS but few GH stars
• SupaGlue - dead
• Merge.dev - no pricing, closed source, pricing likely expensive ($650 per month for 10 integrations)
• Finch - just for employment
• Cycler - looks corporate. Starts at $2k per month
• ApiDeck - starts at $300 per month
• Unified.to - too expensive. starts at $250 per month
• Prismatic - must contact for pricing, so it's not cheap. But also not sure they even do what we need