`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 a triage agent to a custom inbound event type, with a shared secret used to authenticate webhook deliveries:


hiveloom event subscribe triage \
  --event-type ticket.created \
  --auth-token "$INBOUND_TOKEN"

The agent is the positional argument (name or ID). --auth-token is required; inbound webhooks must present its SHA-256-matching value or they’re dropped. Optionally narrow the subscription with --source-filter <name>, which matches the event payload’s top-level source field.

List + inspect:


hiveloom event list triage
hiveloom event show triage <subscription-id>

Toggle:


hiveloom event disable triage <subscription-id>
hiveloom event enable  triage <subscription-id>

Delete:


hiveloom event delete triage <subscription-id>

What happens at delivery time

When a webhook delivers an event whose type matches an active subscription, Hiveloom verifies the auth token, checks the source filter (if any), and runs the subscribed agent through the full agent loop with a synthetic internal conversation. The conversation surface is internal / event:<event-type>:<subscription-id>. A failure on one subscription is logged and does not block other subscribers from running.

Event types

Event types are free-form strings: pick whatever makes sense for the source system (e.g. ticket.created, pagerduty.incident, github.issue.opened). Hiveloom doesn’t enforce a registry — the type is just the routing key.

hiveloom event