docs(kno-14741): trigger guide step - #1615
Open
emisilvacab wants to merge 6 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
emisilvacab
force-pushed
the
emi-kno-14741-docs-trigger-guide-step
branch
from
August 19, 2026 18:40
a971cdb to
b1d3928
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk MEDIUM: Adds new trigger guide step documentation with sidebar navigation and cross-links from related docs.
Reasons
- Adds a new MDX page at
content/designing-workflows/trigger-guide-step.mdx(93 lines) - Updates sidebar navigation in
data/sidebars/platformSidebar.tsto surface the new page - Touches multiple documentation sections:
designing-workflows/,concepts/, andin-app-ui/ - No code, build, dependency, or shared component changes — content and navigation only
- Diff size (101 additions, 3 deletions across 4 files) is moderate but not a substantial rewrite of existing pages
Notes
- Verify internal links resolve correctly (
/designing-workflows/trigger-guide-step, audience and guide docs) - Confirm the new sidebar entry appears in the correct position under "Designing workflows"
- Review the beta callout and FAQ content for accuracy against the product behavior
- Check that cross-links from
broadcasts.mdxandguides/overview.mdxread naturally in context
Sent by Cursor Automation: Docs PR classifier
cellomatt
approved these changes
Aug 19, 2026
cellomatt
left a comment
cellomatt
left a comment
Member
There was a problem hiding this comment.
Approving to unblock but I left a bunch of nits
scotidodson
reviewed
Aug 19, 2026
| separate audience to create or maintain, and no remove action since guide | ||
| eligibility from a step is additive only. | ||
| </Accordion> | ||
| <Accordion title="Can I remove a recipient's eligibility once they're enrolled?"> |
Contributor
There was a problem hiding this comment.
I wonder if this should be a section in the main page? Or are we thinking most will just archive the guide to remove?
Contributor
Author
There was a problem hiding this comment.
We don't currently support removing members directly from the managed audience. Once that capability is available, we can add a section explaining how to remove users from the audience and revoke their eligibility in a more straightforward way.
Comment on lines
84
to
90
| the recipient into the guide's targeting the moment the step runs. You can | ||
| also use our [update audience | ||
| function](/designing-workflows/update-audience-function) to add a user to a | ||
| static audience during a workflow run. You can also use the [update user | ||
| static audience you manage yourself, or the [update user | ||
| function](/designing-workflows/update-user-function) to modify a user's | ||
| properties in order to make them eligible for membership in a [dynamic | ||
| audience](/concepts/audiences#dynamic-audiences) or for the targeting |
Contributor
There was a problem hiding this comment.
Suggested change
| the recipient into the guide's targeting the moment the step runs. You can | |
| also use our [update audience | |
| function](/designing-workflows/update-audience-function) to add a user to a | |
| static audience during a workflow run. You can also use the [update user | |
| static audience you manage yourself, or the [update user | |
| function](/designing-workflows/update-user-function) to modify a user's | |
| properties in order to make them eligible for membership in a [dynamic | |
| audience](/concepts/audiences#dynamic-audiences) or for the targeting | |
| the recipient into the guide's targeting the moment the step runs. | |
| Alternatively, use the [update audience | |
| function](/designing-workflows/update-audience-function) to add a user to a | |
| static audience you manage yourself, or use the [update user | |
| function](/designing-workflows/update-user-function) to modify a user's | |
| properties in order to make them eligible for membership in a [dynamic | |
| audience](/concepts/audiences#dynamic-audiences) or for the targeting |
Contributor
There was a problem hiding this comment.
I wonder if we should be keeping the update user / update audience options? Should we just be directing to the new trigger guide step?
Contributor
Author
|
Changed the name of the step from "Trigger guide" to "In-app guide" pr https://github.com/knocklabs/control/pull/11105 |
Contributor
Author
|
Added screenshots: Screen.Recording.2026-08-21.at.11.08.29.mov |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Added docs for the trigger guide step, with workflow and broadcast usage, targeting behavior, debugging, and FAQs. Updated the workflow sidebar, guides overview, and broadcasts documentation with links to the new page.
Tasks
KNO-14741