hiveloom event
Manages event subscriptions: when a platform event matches a subscription, the subscribed agent is invoked with a templated prompt. Use this for inbox-style flows where the agent reacts to inbound traffic instead of being chatted with directly.
Synopsis
hiveloom event [GLOBAL FLAGS] <COMMAND>Global flags
| Flag | Default | Description |
|---|---|---|
--tenant <TENANT> | default | Tenant slug. |
--endpoint <URL> | — | API endpoint. |
--token <TOKEN> | — | Bearer token. |
--json | — | JSON output. |
Subcommands
| Subcommand | Purpose |
|---|---|
subscribe | Create an event subscription on an agent. |
list | List subscriptions for an agent. |
show | Show one subscription. |
enable | Enable a disabled subscription. |
disable | Disable temporarily; subscription is kept. |
delete | Delete the subscription. |
Examples
Subscribe an agent to inbound chat events:
hiveloom event subscribe \
--agent triage \
--type chat.received \
--label triage-inboundList + inspect:
hiveloom event list --agent triage
hiveloom event show sub_abc123 --agent triageToggle:
hiveloom event disable sub_abc123 --agent triage
hiveloom event enable sub_abc123 --agent triageDelete:
hiveloom event delete sub_abc123 --agent triageEvent types
The set of valid event types is defined by the platform binary; ask
--help for the current list. As of this release, the most commonly used
types are chat.received and schedule.fired.
See also
hiveloom schedule— clock-driven invocations.