Patch Changes
-
#801
a26ddd8Thanks @omeraplak! - feat: add triggers DSL improvements and event payload simplification- Introduce the new
createTriggersDSL and expose trigger events via sensible provider names (e.g.on.airtable.recordCreated) rather than raw catalog IDs. - Add trigger span metadata propagation so VoltAgent agents receive trigger context automatically without manual mapping.
- Simplify action dispatch payloads:
payloadnow contains only the event’s raw data while trigger context lives in theevent/metadatablocks, reducing boilerplate in handlers.
import { VoltAgent, createTriggers } from "@voltagent/core"; new VoltAgent({ // ... triggers: createTriggers((on) => { on.airtable.recordCreated(({ payload, event }) => { console.log("New Airtable row", payload, event.metadata); }); on.gmail.newEmail(({ payload }) => { console.log("New Gmail message", payload); }); }), });
- Introduce the new
-
#801
a26ddd8Thanks @omeraplak! - Add full Discord action coverage toVoltOpsActionsClient, including typed helpers for messaging, reactions, channels, and guild roles. All VoltOps Actions now require the inlinecredentialpayload—pass{ id: "cred_xyz" }to reuse a saved credential or provide provider-specific secrets on the fly. Each provider now has explicit credential typing (Airtable ⇒{ apiKey }, Slack ⇒{ botToken }, Discord ⇒{ botToken } | { webhookUrl }), so editors autocomplete only the valid fields. The SDK propagates these types so apps can invoke VoltOps Actions without managing separate credential IDs. -
Updated dependencies [
a26ddd8,a26ddd8]:- @voltagent/core@1.2.6