Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass user specific API key or auth token in custom tool #132

Open
ghost opened this issue Oct 24, 2024 · 1 comment
Open

Pass user specific API key or auth token in custom tool #132

ghost opened this issue Oct 24, 2024 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 24, 2024

Hi, is there a way user specific API keys and auth token of the logged in user be used to make a call to APIs using custom tool. this is important for enterprise use cases.

@AciD-sEc
Copy link

To solve the issue described in FlowiseDocs Issue #132 regarding the plugin API key, follow these steps:

  1. Update the Flowise Repository:
    Ensure you have the latest version of the Flowise repository. Sync your fork or pull the latest changes, as the required functionality has already been implemented.

  2. Use the Updated Configuration Fields:
    The maintainers added a feature to allow users to configure headers for GET and POST tools, such as:

    • Authorization headers: Include the API key in the format Authorization: Bearer YOUR_API_KEY.
    • Other Custom Headers: Add any required headers specific to your plugin.

    In the tool's settings, you should now see fields where you can specify the URL, description, and headers for API requests.

  3. Steps to Add Headers:

    • Navigate to the settings for your plugin or the relevant tool in Flowise.
    • Locate the "Headers" field in the configuration options.
    • Input your API key as part of the header configuration, e.g.,
      json { "Authorization": "Bearer YOUR_API_KEY" }
    • Save the configuration and test the functionality to ensure the plugin works correctly.
  4. Verify Plugin Operation:
    Run the chat app and confirm that the plugin is successfully connected and operational.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant