meeting_step
Represents a specific step or agenda item within a meeting, used to structure meetings and track progress through activities like notes, discussions, checklists, and tasks.
Fields
| Field | Type | Description |
|---|---|---|
id | uuid | Unique identifier for the step |
meetingId | uuid | Reference to the meeting |
stepConfigId | String | Reference to the step configuration in the meeting's stepsConfig |
type | Meeting_Step_Type_Enum | Type of meeting step |
data | meeting_step_data | Step-specific data and content |
notes | String | Notes and documentation for the step |
Relationships
Object Relationships:
meeting— The meeting this step belongs to
Step Types
- Tour — Notes (legacy name for the notes/round step)
- Threads — Discussion threads/topics
- Checklist — Circle checklist review
- Indicators — Circle indicators review
- Tasks — Task management step
Query Examples
Get Steps for a Meeting
query GetMeetingSteps($meetingId: uuid!) {
meeting_step(where: { meetingId: { _eq: $meetingId } }) {
id
type
stepConfigId
data
notes
}
}
Mutation Examples
Create a Meeting Step
mutation CreateMeetingStep {
insert_meeting_step_one(
object: {
meetingId: "meeting-id"
stepConfigId: "step-1"
type: Tour
data: {}
notes: "Opening check-in round"
}
) {
id
type
data
}
}
Update Step Data and Notes
mutation UpdateMeetingStep($id: uuid!, $data: json!, $notes: String!) {
update_meeting_step_by_pk(
pk_columns: { id: $id }
_set: { data: $data, notes: $notes }
) {
id
data
notes
}
}
Permissions
- Circle participants: Can view and update steps in their circle’s meetings
- Meeting attendees: Can view steps and update them if not in read-only mode
- Organization members: Can view steps in non-private meetings
Notes
Steps are created based on the meeting template’s stepsConfig. The data
field structure varies by step type. Progress through steps is tracked via the
meeting’s currentStepId field. Notes can be updated during and after the
meeting.