Feature Request: Support Multiple Accounts per Integration and Bot

Abierto
  • ¿Algo no está bien?
#990 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
authentication, authorization, backend-api-design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
9.2k
Forks
1.2k
Merge medio
1 d 17 h
PR fusionados (30 d)
173

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CopilotKit/OpenBot

Todos los issues de CopilotKit/OpenBot

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.