Enable or disable an outbound trigger
Enable or disable a trigger. ENABLING requires a standing consent attestation (consentAttested=true) and stands up its delivery (a no-op for a static webhook; a provider subscription for subscription-delivery). DISABLING tears down any provider subscription. Enabling makes the trigger originate a real call on every matched event.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
The compiled trigger id (returned by createOutboundTrigger / listOutboundTriggers).
Body
Response
The updated trigger.
A compiled outbound trigger ("when {event} in {provider} → call {agent}"). The server-authored fields (agentId, callerNumberId, messageCategory, intentType, consentBasis) are PINNED at compile; the inbound payload can never choose them. It lands disabled and the operator enables it (a standing consent attestation).