Journey group tools
A journey group bundles related journeys under one name so they can be audited together. Six tools.
list_journey_groups
Section titled “list_journey_groups”List journey groups for a project, each with its member journeys and journey count.
| Name | Type | Required |
|---|---|---|
project_id | string | yes |
Returns: the project’s groups, each with its members. Not paginated.
create_journey_group
Section titled “create_journey_group”Create a journey group for a project. The group is created empty; add journeys with
set_journey_group_members.
| Name | Type | Required |
|---|---|---|
project_id | string | yes |
name | string | yes |
description | string | no |
Returns: the created group.
update_journey_group
Section titled “update_journey_group”Update a journey group’s name or description.
| Name | Type | Required |
|---|---|---|
journey_group_id | string | yes |
name | string | no |
description | string | no |
Does not change membership.
Returns: the updated group.
delete_journey_group
Section titled “delete_journey_group”Delete a journey group. The member journeys themselves are not deleted, only the grouping.
| Name | Type | Required |
|---|---|---|
journey_group_id | string | yes |
Returns: the confirmation line Deleted journey group: <id>.
set_journey_group_members
Section titled “set_journey_group_members”Set the full member list of a journey group.
| Name | Type | Required | Notes |
|---|---|---|---|
journey_group_id | string | yes | |
journey_ids | string[] | yes | The complete desired set of members. |
REPLACE semantics. The list you send becomes the membership; it is not a delta. Sending one id leaves the group holding exactly one journey.
Returns: the group with its updated journey count and members.
run_journey_group
Section titled “run_journey_group”See the generated operation reference for arguments. Pass
groupId. The server derives the project and organization, loads the group’s members, and
commissions one cloud audit for each member in order.
The GraphQL JSON response contains runCloudJourneyGroup.results. Every entry names the
journeyId and name, with a tagged result: commissioned, queued, billing-refused,
scan-refused, or not started. Started and queued members carry runIds; queued members also
carry their position. Refusals and failures carry their reason. A member failure preserves
earlier commissions and does not prevent later members from being attempted.
A missing, foreign, or empty group is refused before any member starts. A persona with no login
captured is refused before its run starts. Capture it with b8e profile create --persona … --target ….