CLI command
tinbox add-journey-step
Append a step to a journey (or insert it at `order`). Step types and their `config`: - email: { subject: string, bodyMd?: string } — the email to send. ALWAYS write the body (`bodyMd`, markdown), not just a subject, so the draft is complete and reviewable. - delay: { amount: number, unit: 'minutes'|'hours'|'days' } (wait before the next step) - condition: { conditions: { match: 'all'|'any', rules: [...] }, onPass?: 'continue'|'skip'|'exit', onFail?: 'continue'|'skip'|'exit' } — branch on subscriber attributes or prior-email engagement (rule op 'opened_prev'/'clicked_prev' needs the previous email to be a tracked email step with a delay after it). onPass/onFail route the run: 'continue' = fall through, 'skip' = jump the next step, 'exit' = end the run. Defaults: onPass 'continue', onFail 'exit' (a plain gate). - tag: { tag: string } (apply a tag to the contact) Build the sequence by adding steps in order; the journey must have ≥1 step before it can be activated. If the requested logic can't be expressed (only 4 trigger types; conditions test the immediately-preceding email + segment attributes; branching is continue/skip/exit only, no arbitrary goto), say so in the create_journey `rationale` rather than silently building the wrong graph.
Generated from tool: add_journey_stepUsage
tinbox add-journey-step --journeyId <journeyId> --type <type> --config <config> --order <order>Flags
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
--journeyId | string | yes | — | The journey to add the step to. |
--type | string | yes | — | The step type. |
--config | string | yes | — | Step config — shape depends on `type` (see the tool description). |
--order | string | yes | — | 0-based insert position; omit to append at the end. |