An Automation runs versioned logic inside Hooksbase before a delivery reaches the destination. For AI agent workflows, that usually means shaping the event into a clean input contract before the agent sees it.
The first supported Automation type is a Code Mode transform: JavaScript that runs after routing and before the dispatch snapshot is saved.
Why it matters
Without Automations, every agent runtime has to normalize provider payloads itself. That scatters event-shaping logic across agents, queues, and background workers.
With Automations, the event layer owns that logic:
- routing still evaluates the original source payload
- Code Mode transforms produce the agent-facing dispatch snapshot
- runs, logs, and quotas are tied to the delivery pipeline
- retries and replays use the saved dispatch snapshot
What Automations are not
Automations are not a general workflow builder, an arbitrary public JavaScript playground, or an AI code-generation feature. They are versioned event-path logic for controlled delivery flows.
See also: Code Mode, Payload transform, and Dispatch snapshot.
Related terms
- Code Mode
The JavaScript transform mode inside Hooksbase Automations.
Read - Payload transform
Per-webhook JSONPath extraction or Handlebars JSON template applied before dispatch.
Read - Dispatch snapshot
The transformed payload at the moment of dispatch, persisted so replays remain correct under config change.
Read - Replay
Re-running a retained event with the same input — typically after fixing a bug that caused the original to fail.
Read