feat(client): support startingWorkflowNodeId in session config - #910
Open
pmarkert wants to merge 1 commit into
Open
feat(client): support startingWorkflowNodeId in session config#910pmarkert wants to merge 1 commit into
pmarkert wants to merge 1 commit into
Conversation
Add `startingWorkflowNodeId` to `BaseSessionConfig` and wire it through `constructOverrides` so it is emitted as `starting_workflow_node_id` in the `conversation_initiation_client_data` WebSocket event. This allows callers using the private WebSocket or WebRTC session paths (signed URL / conversation token) to target a specific agent workflow node at conversation start, matching the behaviour already available on the server-side outbound-call API (`ConversationInitiationClientDataRequestInput`). Also adds the field to `ConversationInitiationClientToOrchestratorEvent` in `@elevenlabs/types` so the type system is consistent end-to-end.
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
1 participant
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.
Add
startingWorkflowNodeIdtoBaseSessionConfigand wire it throughconstructOverrides.This allows callers using the private WebSocket or WebRTC session paths (signed URL / conversation token) to target a specific agent workflow node at conversation start, matching the behaviour already available on the server-side outbound-call API (
ConversationInitiationClientDataRequestInput).Also adds the field to
ConversationInitiationClientToOrchestratorEventin@elevenlabs/typesso the type system is consistent end-to-end. Did not touch the auto-generated file, but it should probably be regenerated.Note
Low Risk
Small optional passthrough on session startup; no auth or data-model changes in this diff.
Overview
Adds optional
startingWorkflowNodeIdonBaseSessionConfigso private WebSocket/WebRTC sessions (signed URL / conversation token) can tell the agent workflow which node to enter at conversation start, instead of always using the default entry node.constructOverridesnow copies that value onto the conversation initiation payload asstarting_workflow_node_id, matching the server-side outbound initiation shape described in the PR.Reviewed by Cursor Bugbot for commit 54f3b7e. Bugbot is set up for automated code reviews on this repo. Configure here.