Feature Request: Support Multiple Accounts per Integration and Bot

Aperta
  • Qualcosa non va?
#990 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
authentication, authorization, backend-api-design

Direzione di ricerca

Start by locating how integrations are connected, how credentials and permissions are stored, and how Bots receive tools or account access. Trace one integration through connection, Bot assignment, and task execution to see which parts assume a single account. Done means users can connect multiple accounts, assign and manage them per Bot, and use assigned accounts together in a workflow.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

Currently, OpenBot does not provide a clear way to connect multiple accounts of the same integration and assign them to a single Bot.

For example, I want my Chief of Staff Bot to access multiple Gmail accounts, multiple Google Calendar accounts, and potentially multiple accounts from other supported integrations.

A single integration connection should not be limited to one account per user or Bot.

Expected Behavior

Support multiple accounts at different levels:

  1. User Level: Allow users to connect multiple accounts of the same integration (e.g., multiple Gmail and Google Calendar accounts).

  2. Integration Level: Maintain independent connections, credentials, and permissions for each account.

  3. Bot Level: Allow users to assign one or more connected accounts to individual Bots. Different Bots can have access to different accounts.

  4. Execution Level: When a Bot performs a task, it should be able to access all accounts assigned to it and use them together in a single workflow.

  5. Permission Level: Allow users to independently manage, revoke, and modify account access for each Bot.

Example Use Case

I have a Chief of Staff Bot.

I assign it:

  • Gmail: Personal, Work, Business.
  • Google Calendar: Personal, Work, Business.

When instructed to prepare my daily briefing, the Bot should retrieve and consolidate relevant information across all assigned accounts into one response.

Goal: Enable multi-account, multi-integration access with flexible account assignment and permissions at the Bot level, rather than treating each integration as a single-account connection.

Lingua principale
TypeScript
Stelle
9.2k
Fork
1.2k
Merge medio
1g 17h
PR unite (30g)
173

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CopilotKit/OpenBot

Tutte le issue di CopilotKit/OpenBot

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.