Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature Request] Please add webhook-triggered Agent runs — fire-and-forget POST on completion

Abierto
  • ¿Algo no está bien?
#324 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
api, backend, security

Línea de trabajo

Comienza por localizar y auditar el punto de entrada existente para la ejecución de Agent, el registro de auditoría y la aplicación de concesiones o políticas descritos en el issue. Determina cómo encajaría la configuración de webhooks entrantes y salientes en esos sistemas existentes y, después, utiliza los criterios de aceptación para definir la finalización, incluida la validación, la limitación de tasa, los permisos sin cambios y los registros de auditoría.

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

Descripción

Problem

OpenBot has persistent coworkers, per-Agent computers, governed tool use, and auditability, but it lacks a simple way to trigger Agent runs from external events or notify external systems when a run completes.

For teams integrating OpenBot into existing workflows (e.g., CI/CD pipelines, monitoring alerts, newsletter automation), there is no way to kick off an Agent run via webhook or receive a notification when a run finishes. This forces manual intervention or polling, which defeats the purpose of autonomous Agents.

Feature request

Add webhook-triggered Agent runs — a fire-and-forget POST endpoint to start a run, and an optional outbound webhook when a run completes. This should be an event-layer feature, not a new scheduling system.

Proposed behaviour

  • Allow configuring an inbound webhook URL per Agent that, when POSTed to, triggers a new run with the provided payload as context.
  • Allow configuring an outbound webhook URL per Agent that receives a POST when a run completes (success, failure, or refusal).
  • Support optional payload templates for outbound webhooks (e.g., include run ID, outcome, transcript summary).
  • Validate inbound webhook payloads and show clear errors for malformed requests.
  • Preserve all governance settings (grants, policies) for webhook-triggered runs, scoped to the Agent's existing permissions.
  • Rate-limit inbound webhooks to prevent abuse (e.g., max 10 runs per minute per Agent).

Required controls

  • Disabled by default; enabled per Agent.
  • Webhook scope: per-Agent, not per deployment.
  • Immutable audit log showing when a webhook triggered a run or was sent on completion.
  • Review, edit, and delete controls for webhook URLs.
  • Clear separation between webhook payload and runtime state (no arbitrary code execution from payload).
  • Never automatically grant additional tools or permissions for webhook-triggered runs — grants are unchanged.
  • Configurable allowlist for webhook sources (specific IPs, domains, or any URL).

Why this matters

This would make OpenBot more competitive for teams integrating Agents into existing automation workflows while preserving its core advantages: per-Agent isolation, gateway policy enforcement, and action-level auditability. It would be particularly useful for a self-hosted team that wants to trigger Agents from external events (e.g., "new issue filed", "site downtime detected", "newsletter draft due") without manual intervention.

Acceptance criteria

  1. An administrator can configure an inbound webhook URL for an Agent.
  2. An administrator can configure an outbound webhook URL for an Agent.
  3. POSTing to the inbound webhook triggers a new Agent run with the payload as context.
  4. Completing a run sends a POST to the outbound webhook with run metadata.
  5. All webhook triggers and sends appear in the existing audit trail.
  6. Invalid webhook payloads are rejected with clear error messages.
  7. Webhook-triggered runs respect the Agent's existing grant boundaries.

Suggested name

Webhook Triggers or Event-Driven Agent Runs

Lenguaje dominante
TypeScript
Estrellas
6.6k
Forks
914
Merge medio
19 h 22 min
PR fusionados (30 d)
140

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.