Skip to content

feat(kno-14717): add trigger guide step support - #856

Open
emisilvacab wants to merge 1 commit into
mainfrom
emi-kno-14717-cli-trigger-guide-step-support
Open

feat(kno-14717): add trigger guide step support#856
emisilvacab wants to merge 1 commit into
mainfrom
emi-kno-14717-cli-trigger-guide-step-support

Conversation

@emisilvacab

Copy link
Copy Markdown
Contributor

Description

Adds trigger guide step support in the cli:

  • Added in_app_guide to ChannelType, STEP_TAGS and StepTagChoices
  • Extended ChannelStepData with optional channel_type, guide_key, and optional template (guide steps are template-less)
  • In-app guide channel steps show Guide: {guide_key} instead of channel destination lines
  • Added scaffoldInAppGuideChannelStep producing the output in the screenshot
  • Supports --steps in_app_guide and legacy alias in-app-guide
  • Always available in getAvailableStepTypes (no channel destination required)
  • Template workflow generation skips channel reference swapping for guide steps

Tasks

KNO-14717

Screenshots

Created a workflow with an in_app_guide step
Screenshot 2026-08-11 at 16 23 08

Then I manually updated the <GUIDE KEY> inside workflow.json to an existing guide key, validated and pushed the workflow
Screenshot 2026-08-11 at 16 23 20

Screenshot 2026-08-11 at 16 20 49

@linear-code

linear-code Bot commented Aug 11, 2026

Copy link
Copy Markdown

KNO-14717

@emisilvacab
emisilvacab requested review from cjbell and thomaswhyyou and removed request for thomaswhyyou August 11, 2026 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants