Stages
Stages represent different phases or states in a user’s journey through your system. They enable you to track progression, trigger stage-specific behaviors, and provide contextual experiences.List Stages
GET /stages
Returns a list of all stages defined in your workspace.
Response
Success message
Array of stage objects
Get Stage
GET /stages/:stage_id
Returns detailed information about a specific stage.
Stage unique identifier
Create Stage
POST /stages
Creates a new stage definition.
Request Body
string
required
Stage name (3-100 characters)
string
Stage description
object
Custom metadata for the stage
Update Stage
PUT /stages/:stage_id
Updates an existing stage definition.
Stage unique identifier
Request Body
string
Stage name (3-100 characters)
string
Stage description
object
Custom metadata for the stage
Assign Stage to Identity
POST /identity/:identity_id/stage
Assigns a stage to an identity, tracking their current position in the journey.
How Stages Work
- Define Stages - Create stage definitions for your user journey
- Assign to Identities - Set identities to specific stages
- Use in Prompts - Reference current stage in assistant instructions
- Track Progression - Monitor how users move through stages
Stage Examples
Common stage patterns:- Onboarding:
welcome,profile_setup,tutorial,onboarding_complete - Product:
browsing,considering,purchased,active_user - Support:
needs_help,in_conversation,resolved,escalated
