Feature Request: Support Multiple Accounts per Integration and Bot

Aberta
  • Algo errado?
#990 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
authentication, authorization, backend-api-design

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
9.2k
Forks
1.2k
Merge médio
1d 17h
PRs com merge (30d)
173

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CopilotKit/OpenBot

Todas as issues de CopilotKit/OpenBot

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.