Skip to main content
POST
/
api
/
v1
/
teams
/
{team_id}
/
onboarding
/
trigger-mode
Set Trigger Mode
curl --request POST \
  --url https://api.example.com/api/v1/teams/{team_id}/onboarding/trigger-mode \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "trigger_mode": "<string>"
}
'
{
  "step": "<string>",
  "connections": [
    {
      "provider": "<string>",
      "label": "<string>",
      "required": false,
      "type": "oauth",
      "connected": false,
      "fields": [
        {
          "key": "<string>",
          "label": "<string>",
          "type": "text",
          "placeholder": "",
          "help": "",
          "default": ""
        }
      ]
    }
  ],
  "cycle_configured": false,
  "loops_configured": false,
  "lifecycle_type": "cyclical",
  "requires_brand": "optional",
  "chat_enabled": true,
  "cycle_start_mode": "<string>",
  "trigger_types": [
    "<string>"
  ],
  "trigger_mode": "<string>"
}

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, PR-3).

Validated server-side: "content-driven" requires the feature flag + a content-driven-capable team type, else 400. None/"strategy-driven" is the default classic flow.

​
trigger_mode
string
required

'strategy-driven' or '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