🔀 diff --git a/docs/docs/guides/langfuse_integration.mdx b/docs/docs/guides/langfuse_integration.mdx
🔀 index db23bbdc..51aba962 100644
🔀 --- a/docs/docs/guides/langfuse_integration.mdx
🔀 +++ b/docs/docs/guides/langfuse_integration.mdx
🔀 @@ -1,35 +1,49 @@
🔀 -import ThemedImage from "@theme/ThemedImage";
🔀 -import useBaseUrl from "@docusaurus/useBaseUrl";
🔀 -import ZoomableImage from "/src/theme/ZoomableImage.js";
🔀 -import ReactPlayer from "react-player";
🔀 -
🔀 # Integrating Langfuse with Langflow
🔀🔀 +## Introduction
🔀 +
🔀 +Langfuse is an open-source tracing and analytics tool designed for LLM applications. Integrating Langfuse with Langflow provides detailed production traces and granular insights into quality, cost, and latency. This integration allows you to monitor and debug your Langflow's chat or APIs easily.
🔀 +
🔀 ## Step-by-Step Instructions
🔀🔀 ### Step 1: Create a Langfuse account
🔀🔀 -1. Go to [https://langfuse.com](https://langfuse.com) and click on the "Sign In" button in the top right corner.
🔀 +1. Go to [Langfuse](https://langfuse.com) and click on the "Sign In" button in the top right corner.
🔀 2. Click on the "Sign Up" button and create an account.
🔀 -3. Click on "Settings" and then on "Create new API keys"
🔀 +3. Once logged in, click on "Settings" and then on "Create new API keys."
🔀 4. Copy the Public key and the Secret Key and save them somewhere safe.
🔀 - {/* Add env variables LANGFLOW_LANGFUSE_SECRET_KEY, LANGFLOW_LANGFUSE_PUBLIC_KEY and LANGFLOW_LANGFUSE_HOST to pass to CallbackHandler */}
🔀 + {/* Add
📝 docs(CNAME): update the CNAME file to point to the new domain for the documentation
🔧 fix(ApiModal/index.tsx): update the links in the description to point to the correct documentation URL
📝 docs(CNAME): update the CNAME file to point to the new domain for the documentation
🔧 fix(ApiModal/index.tsx): update the links in the description to point to the correct documentation URL
🔧 fix(custom-component.mdx): correct the recommended way to load custom components by setting LANGFLOW_COMPONENTS_PATH environment variable instead of using --components-path argument
💡 docs(custom-component.mdx): provide an alternative method to specify the path to custom components using --components-path argument
🔧 fix(custom-component.mdx): correct the recommended way to load custom components by setting LANGFLOW_COMPONENTS_PATH environment variable instead of using --components-path argument
💡 docs(custom-component.mdx): provide an alternative method to specify the path to custom components using --components-path argument
📝 docs(custom-component.mdx): update folder structure section to include custom agents directory
📝 docs(custom-component.mdx): add instructions for specifying the path to custom components using the Langflow CLI
📝 docs(custom-component.mdx): add instructions for setting the LANGFLOW_COMPONENTS_PATH environment variable
📝 docs(custom-component.mdx): clarify that Langflow will continue loading components even if there are errors in some of them
📝 docs(custom-component.mdx): add section on interacting with custom components in Langflow's sidebar
The change clarifies that using a `Document` as input in the `FlowRunner` class is a straightforward way to pass text data in Langflow, specifically because it can be connected to many loaders. It also mentions that generally, a flow expects a string or a dictionary as input. Additionally, it updates the explanation of extracting the content of a document using the `page_content` attribute, which is a string.
The commit adds an explanation about using a `Document` as input in the `FlowRunner` class. It clarifies that using a `Document` is a straightforward way to pass text data in Langflow. Typically, a flow expects a string or a dictionary as input, and if a dictionary is used, it should be built according to the needs of the specific flow. The commit also mentions that the content of a document can be extracted using the `page_content` property and passed as an argument to the selected flow.
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): improve readability and formatting in the CustomComponent class documentation
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): update CustomComponent class documentation with additional methods and descriptions
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
📝 docs(custom.mdx): update CustomComponent class documentation with corrected method names and descriptions
🔀 docs(custom.mdx): merge changes from the CustomComponent class documentation
ℹ️ The example code demonstrates how to create a custom component called "Flow Runner" that runs other flows using a document as input. The code includes the implementation of the `build_config` and `build` methods.
✨ feat(flow-runner.mdx): add example code for a Flow Runner custom component to provide a practical example for users to follow
🐛 fix(flow-runner.mdx): remove unnecessary focus annotations in code snippets
✨ feat(flow-runner.mdx): add support for getting flow by name instead of id in build method
✨ feat(flow-runner.mdx): add caution about unique flow names in version 0.4.0
✨ feat(flow-runner.mdx): add support for passing document parameter in build method
🐛 fix(flow-runner.mdx): remove redundant Optional type hint for document parameter in build method
🐛 fix(flow-runner.mdx): remove empty line at the end of the file
