← Agent catalogue
DISPATCH

Preview portrait

Execution stages

DISPATCH

Materializes `OutboundDispatch` rows and obeys tenant + env gates for live send.

LiveCatalogue status
Execution activeRuntime posture

Outbound dispatch stage: dry-run default, live send multiply gated.

Open consoleBook a Demo

Expanded capabilities

  • Coordinate outbound stage timing after policy/approval clearance
  • Respect adapter readiness before attempting provider calls
  • Stay behind NUNTIUS and APPROVAL QUEUE for messaging
  • Record outbound dispatch evidence when allowed to run
  • Never invent silent reconnects or OAuth repairs

How they learn & improve

DISPATCH improves adapter timing from failed/approved outcomes — connector consent and approvals remain human-owned.

  1. Wait for policy/approval clearance and adapter readiness.
  2. Execute the outbound stage with auditable evidence.
  3. Feed failures into learning/ops attention without auto-healing credentials.

How they work together

DISPATCH is the last-mile executor after NUNTIUS drafts and humans approve — HERMES/TERMINUS observe whether it stalls.

  • NUNTIUSReceives approved messaging intents for outbound timing.
  • Approval queueRuns only after human APPROVE when required.
  • HERMESReports dispatch-stage flow health.
  • AUDITRecords meaningful dispatch attempts.

Practical benefits

  • Approved means approvedOutbound only moves after the queue decision — not when a draft looks ‘ready’.
  • Adapter honestyIf the provider isn’t ready, readiness stays missing/degraded instead of fake success.
  • Ops sees stallsHERMES/TERMINUS show when dispatch is blocked so humans fix connectors or approvals.

Learning and improvement stay human-visible: candidates are RECORD_ONLY until an operator reviews and applies them. Sensitive sends, publishes, and approvals never run silently.

Related agents

DISPATCH — AgentIQ Agent Catalogue · AgentIQ Labs