> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowra.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Bind AuthConfig for a toolkit on an agent workflow

> Sets which project AuthConfig this agent uses for a given toolkit when end users connect.



## OpenAPI

````yaml /api-reference/openapi.json patch /api/v1/workflow/manager/set-auth-config/{id}
openapi: 3.0.0
info:
  title: Flowra API (API Key Endpoints)
  description: >-
    **Flowra** is an AI-powered platform for building agents, workflows, and
    integrations.


    ### Capabilities

    - **Tools & Toolkits** – Define and group tools for agents and workflows.

    - **Workflows** – Orchestrate steps and automate processes.

    - **Triggers** – Schedule or event-based execution.

    - **Auth & Connections** – OAuth, API keys, and connected accounts.

    - **MCP** – Model Context Protocol server integration.

    - **Knowledge / RAG** – Add files and URLs for retrieval-augmented
    generation.


    ### Authentication

    Use the **x-api-key** header with a project API key to access endpoints that
    support API Key auth. Create and manage API keys in the dashboard under your
    project settings.


    Only endpoints that support API Key authentication via the @ApiKeyEnabled()
    decorator.


    Send x-api-key (required). On multi-tenant endpoints, optionally send
    x-username to act as an external user.
  version: '1.0'
  contact:
    name: Flowra
    url: https://flowra.dev
servers:
  - url: https://flowra.dev
    description: Flowra API
security: []
tags:
  - name: Users
    description: User profile
  - name: External Users
    description: End-user identities inside a project (x-username)
  - name: Auth Configs
    description: OAuth and API key configs for toolkits
  - name: Connected Accounts
    description: OAuth connected accounts and link creation
  - name: Toolkits
    description: List and search toolkits
  - name: Tools
    description: List, execute, and manage tools
  - name: Skills
    description: Browse, create, import, and install skills
  - name: Workflow & Agent
    description: Create, run, and inspect workflows and agents
  - name: Triggers
    description: Schedule and event-based trigger instances
  - name: Chat
    description: Threads and streaming agent runs
  - name: File
    description: Upload, list, and download files
  - name: Knowledge
    description: RAG knowledge collections
  - name: Table
    description: Collections and documents
  - name: Sandbox
    description: Ephemeral and durable code sandboxes
  - name: Browser
    description: Live browser sessions and view
  - name: LLM
    description: List AI models and generate completions
  - name: MCP
    description: MCP server management
  - name: usage
    description: Credit balance and usage ledger for the project API key
paths:
  /api/v1/workflow/manager/set-auth-config/{id}:
    patch:
      tags:
        - Workflow & Agent
      summary: Bind AuthConfig for a toolkit on an agent workflow
      description: >-
        Sets which project AuthConfig this agent uses for a given toolkit when
        end users connect.
      operationId: WorkflowManagerController_setAuthConfig
      parameters:
        - name: id
          required: true
          in: path
          description: Workflow (agent) ID
          schema:
            example: 3fa85f64-5717-4562-b3fc-2c963f66afa6
            type: string
        - name: x-username
          in: header
          required: false
          description: >-
            External user (end user) to act as. Optional — if omitted, Flowra
            uses the project’s default external user. Send a stable username
            (e.g. customer_alice) only when you need another end-user context.
          schema:
            type: string
            default: (project default user)
          example: customer_alice
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SetOwnerToolkitAuthConfigDto'
      responses:
        '200':
          description: AuthConfig bound successfully
          content:
            application/json:
              schema:
                $ref: >-
                  #/components/schemas/OwnerToolkitAuthConfigSummaryDtoSuccessResponse
              example:
                success: true
                message: Operation completed successfully
                data:
                  toolkitSlug: ''
                  authConfigId: ''
                  name: ''
                  authScheme: ''
                  status: ''
      security:
        - x-api-key: []
        - x-api-key: []
          x-username: []
components:
  schemas:
    SetOwnerToolkitAuthConfigDto:
      type: object
      properties:
        toolkitSlug:
          type: string
          description: Toolkit slug to bind
          example: gmail
        authConfigId:
          type: string
          description: AuthConfig UUID in the same project
          example: 3fa85f64-5717-4562-b3fc-2c963f66afa6
          format: uuid
      required:
        - toolkitSlug
        - authConfigId
    OwnerToolkitAuthConfigSummaryDtoSuccessResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Success status
          example: true
        message:
          type: string
          description: Success message
          example: Operation completed successfully
        data:
          type: object
          properties:
            toolkitSlug:
              type: string
            authConfigId:
              type: string
            name:
              type: string
              nullable: true
            authScheme:
              type: string
              nullable: true
            status:
              type: string
              nullable: true
          required:
            - toolkitSlug
            - authConfigId
          example:
            toolkitSlug: ''
            authConfigId: ''
            name: ''
            authScheme: ''
            status: ''
      required:
        - success
        - message
        - data
  securitySchemes:
    x-api-key:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Project API key. Create and manage keys in the dashboard under Project →
        API Keys. Send as header: x-api-key: <your-key>
    x-username:
      type: apiKey
      in: header
      name: x-username
      description: >-
        Optional. External user username. If omitted, Flowra uses the project’s
        default external user. Send as header: x-username: <username>

````