Skip to content

Group journeys and run them together

A journey group bundles related journeys so you can audit them in one call — every checkout flow, say, or everything a signed-out visitor can reach.

create_journey_group(project_id, name: "Checkout", description: "Guest and signed-in purchase flows")

The group starts empty. Creating it does not move any journeys into it.

Membership is set, not appended:

set_journey_group_members(journey_group_id, journey_ids: ["jrn_a", "jrn_b"])

This replaces the whole member list. Pass the complete desired set every time, never a delta — sending one id does not add one journey, it leaves the group with exactly that one journey. To add to a group, read its current members with list_journey_groups first and send the union.

The call returns the group with its updated members and journey count.

run_journey_group(groupId)

Read runCloudJourneyGroup.results in the returned JSON. Each member carries its journey ID, name, and result. Follow the runIds of commissioned and queued members with get_audit_progress. Read each refusal or failure before treating the group as covered. One member failing does not stop later members from being attempted.

Read a completed report with get_agentic_audit_report(runId: "<run id>"). Its collections are paged; follow the cursors described in the report reference.

update_journey_group(journey_group_id, name, description)
delete_journey_group(journey_group_id)

update_journey_group does not touch membership. Deleting a group deletes only the grouping — the member journeys survive.

Full arguments: journey group tools.