Journeys and automation bindings
Multi-step sequences, what starts them, and how one is paused.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
Each journey with its trigger, its steps and its bindings to product events, plus the control that pauses one — the difference between stopping a campaign and stopping the transactional mail a customer needs.
What has to exist first
- Reads
- staffCommJourneysList
- Actions
- staffCommJourneySave
- staffCommJourneyValidate
- staffCommJourneyPublish
- staffCommJourneyPause
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.