feat:Add AuthConnectionLocator schema and update WebhookToolApiSchemaConfig schemas

[HavenDV]

Summary by CodeRabbit

• New Features
  • Added support for referencing an authentication connection in webhook tool API configurations, allowing users to specify an auth connection alongside headers, secrets, and dynamic variables.

[coderabbitai]

Walkthrough

A new schema, AuthConnectionLocator, was introduced to the OpenAPI specification. The WebhookToolApiSchemaConfig-Input and WebhookToolApiSchemaConfig-Output schemas were updated to include an optional auth_connection property in their request_headers, referencing this new schema.

Changes

File	Change Summary
src/libs/ElevenLabs/openapi.yaml	Added AuthConnectionLocator schema; updated webhook tool API config schemas to reference it.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant WebhookToolAPI
    participant AuthConnectionStore

    Client->>WebhookToolAPI: Configure webhook with request_headers (may include auth_connection)
    WebhookToolAPI->>AuthConnectionStore: Lookup auth_connection using auth_connection_id (if provided)
    AuthConnectionStore-->>WebhookToolAPI: Return auth connection details
    WebhookToolAPI-->>Client: Confirm configuration or return error

Loading

Poem

In the land of code where schemas grow,
A new connection hops in tow.
With headers neat and auth in sight,
Webhooks leap with fresh delight.
A rabbit cheers this tidy fix—
More connections in the mix! 🐇✨

✨ Finishing Touches

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment
• Commit Unit Tests in branch bot/update-openapi_202506260922

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

♻️ Duplicate comments (1)

src/libs/ElevenLabs/openapi.yaml (1)

24300-24302: Duplicate concern for Output schema

The same structural caveat applies to the Output variant – ensure consistency with whatever decision is taken for the Input schema.

🧹 Nitpick comments (2)

src/libs/ElevenLabs/openapi.yaml (2)

10901-10910: Add property–level description & (optionally) format for stronger schema contracts

The auth_connection_id field is not self-describing in downstream tooling (e.g. code-gen or API explorers). Consider enriching it:

         auth_connection_id:
           title: Auth Connection Id
           type: string
+          description: Identifier of the auth-connection object stored in the workspace.  
+          format: uuid   # or another canonical format if it is not a UUID

This small addition improves generated SDK doc‐strings and enforces tighter validation at the gateway.

---

10901-10910: Missing example update

Because this new schema is now referenced from two request-header configurations, future consumers will look for an example payload. Add a short example to the schema (or extend the existing examples at 24246 / 24303) so integrators understand the expected structure:

example:
  auth_connection_id: "e7f8c6d2-1a5b-4f79-b31d-a4d1b7d8d9c1"

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 11e8e0c and bc5553a.

⛔ Files ignored due to path filters (5)

• src/libs/ElevenLabs/Generated/ElevenLabs.JsonSerializerContextTypes.g.cs is excluded by !**/generated/**
• src/libs/ElevenLabs/Generated/ElevenLabs.Models.AuthConnectionLocator.Json.g.cs is excluded by !**/generated/**
• src/libs/ElevenLabs/Generated/ElevenLabs.Models.AuthConnectionLocator.g.cs is excluded by !**/generated/**
• src/libs/ElevenLabs/Generated/ElevenLabs.Models.WebhookToolApiSchemaConfigInput.g.cs is excluded by !**/generated/**
• src/libs/ElevenLabs/Generated/ElevenLabs.Models.WebhookToolApiSchemaConfigOutput.g.cs is excluded by !**/generated/**

📒 Files selected for processing (1)

• src/libs/ElevenLabs/openapi.yaml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: Test / Build, test and publish

🔇 Additional comments (1)

src/libs/ElevenLabs/openapi.yaml (1)

24243-24245: Placement of auth_connection inside request_headers may be semantically misleading

request_headers appears to be a container for actual HTTP headers, each represented by a Header/SecretLocator/DynamicVariable.
A reference to an auth-connection object is conceptually orthogonal – it is not an HTTP header but rather meta-configuration that will later be resolved into headers (e.g. Authorization: Bearer …).

If request_headers is consumed by code-gen or runtime that expects only header-compatible shapes, adding auth_connection inlined here could break validation or coerce developers to misuse the field.

Options:

1. Keep auth_connection but nest it under a separate sibling property, e.g. auth or auth_settings.
2. If you really need it under request_headers, document the reasoning and adapt validators/transformers accordingly.

Please double-check downstream serializers before merging.