Skip to main content
POST
Set Trigger Mode

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

team_id
string<uuid>
required

Body

application/json

Persist the onboarding trigger-mode choice (SMMT content-driven).

Validated server-side: "content-driven" requires the feature flag + a content-driven-capable team type, else 400.

trigger_mode is deliberately REQUIRED here (no None): this request is the wizard's explicit set-trigger-mode action, so the client always sends a concrete choice. The nullable state lives on the STORED column — AgentTeam.trigger_mode may be NULL (= classic strategy-driven default, resolved by team_service._resolve_trigger_mode) for teams that never answered the wizard question. Don't widen this Literal to | None; a client with nothing to set simply doesn't call the endpoint.

trigger_mode
enum<string>
required

'strategy-driven' or 'content-driven'

Available options:
strategy-driven,
content-driven

Response

Successful Response

step
string
required
connections
ConnectionRequirement · object[]
cycle_configured
boolean
default:false
loops_configured
boolean
default:false
lifecycle_type
string
default:cyclical
requires_brand
string
default:optional
chat_enabled
boolean
default:true
cycle_start_mode
string | null
trigger_types
string[]
trigger_mode
string | null