hogsend journeys

Usage

hogsend journeys

Shows which journeys are currently enabled, then optionally lets you update the selection. Changes are applied to both the API and Worker services on Railway and trigger an automatic redeploy.

What it does

Loads the current journey configuration from .hogsend.yaml
Displays the currently enabled journeys (or "All journeys (*)" if none are filtered)
Asks if you want to update the selection
If yes, presents a multi-select with all available journeys, pre-selecting currently enabled ones
Updates the ENABLED_JOURNEYS environment variable on both the API and Worker services
Redeploys both services
Saves the new selection to .hogsend.yaml

Available journeys

Journey	Trigger event
`activation-welcome`	`user_signed_up`
`activation-nudge-series`	`user_signed_up`
`conversion-trial-upgrade`	`trial_started`
`conversion-abandoned-checkout`	`checkout_abandoned`
`retention-milestone`	`milestone_reached`
`referral-invite`	`subscription_created`
`feedback-nps`	`subscription_created`
`reactivation-dormancy`	`user_activated`
`churn-prevention`	`subscription_cancelled`, `payment_failed`
`test-onboarding`	`test_signup`

How filtering works

The ENABLED_JOURNEYS environment variable controls which journeys the worker loads:

* -- all journeys are enabled (default when no filter is set, or when all journeys are selected)
activation-welcome,retention-milestone -- comma-separated list enables only those specific journeys

If you select all available journeys, the filter is set to * rather than listing them all individually.

Example output

HOGSEND JOURNEYS

Currently enabled:
  + activation-welcome
  + retention-milestone

? Update journey selection? Yes

? Select journeys to enable
  [x] activation-welcome
  [ ] activation-nudge-series
  [x] conversion-trial-upgrade
  [x] retention-milestone
  [ ] referral-invite
  ...

  Updating ENABLED_JOURNEYS...  done
  Redeploying services...       done

  Updated  Journeys updated and redeployed