Overview

The product documentation explains how to do things. This section defines what the things are: the objects the API, the MCP tools, and the app all operate on. Reach for it when a term appears in a request or a response and you want to know exactly what it refers to.

How the pieces fit

A workspace contains everything. Inside it:

• Leads are the people you want to reach. They live in lead lists.
• A campaign points at one lead list, one piece of content, and one sequence.
• A sequence is an ordered set of steps. Each step sends something on a channel after a delay.
• Steps go out from a sender profile, which is the identity a message appears to come from.
• Replies arrive as conversations.
• Work that costs money to produce consumes credits.

The shape of it

Workspace
├── Lead list ─── Lead ─── stage, tags
├── Sender profile ─── connected account, voice
└── Campaign
    ├── lead list      (who it goes to)
    ├── content        (what they receive)
    └── Sequence
        ├── Step 1 ─── channel, delay, sender profile
        └── Step 2 ...

The relationships are worth knowing because they explain the constraints. A campaign has exactly one lead list and one sequence, so "run the same sequence against a different audience" means a second campaign, not a setting.