Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#324 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
api, backend, security

Direzione di ricerca

Inizia individuando e verificando il punto di ingresso esistente per l’esecuzione di Agent, la traccia di audit e l’applicazione di concessioni o policy descritti nell’issue. Mappa come la configurazione dei webhook in entrata e in uscita si integrerebbe con questi sistemi esistenti, quindi usa i criteri di accettazione per definire il completamento, includendo la validazione, il rate limiting, i permessi invariati e i record di audit.

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

Descrizione

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

Lingua principale
TypeScript
Stelle
6.6k
Fork
914
Merge medio
19h 22m
PR unite (30g)
140

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.