---
title: "Event-driven · agent topology · Agent Fieldbook"
url: https://agentfieldbook.org/design/topologies/event-driven/
description: "Sparse dormant field with active pulse epicentres."
section: "Design · Topologies"
source: Agent Fieldbook — generated from the published page
---

# Event-driven

Sparse dormant field with active pulse epicentres.

Verified against [confluent.io](https://www.confluent.io/blog/event-driven-multi-agent-systems/)

- [confluent.io](https://www.confluent.io/blog/event-driven-multi-agent-systems/)

An event-driven agent is organised around a message bus: work arrives as events, handlers react, and their outputs are published as new events for other handlers to consume. There is no linear script; the flow is whatever the events trigger, which decouples producers from consumers and lets each part scale independently. It is the shape behind automation platforms wiring many triggers to many actions. In anatomy terms the transport layer, the bus, is the spine.

## In the anatomy

An event bus is the spine; handlers (scoped cores or effectors) subscribe and publish; no central orchestrator sequences them; the perimeter gates each handler's writes.

## At a glance

| Field | Value |
| --- | --- |
| Pattern | Event-driven |
| State model | durable |
| Example | Lindy, Zapier Agents |

## Common use cases

## Strengths

## Weaknesses

## Agents using this pattern · 4

Mapping classified by the Field Book from each agent's documented control flow.

## Basis

Description, use cases and trade-offs: Field Book analysis, synthesised from established agent-architecture literature.

## Verified against

- [https://www.confluent.io/blog/event-driven-multi-agent-systems/](https://www.confluent.io/blog/event-driven-multi-agent-systems/)

The corpus does not rewrite vendor documentation. Where copy is quoted verbatim it is marked as such and attributed to its source.