About bundles
Bundles contain custom components that support specific third-party integrations with Langflow. You add them to your flows and configure them in the same way as Langflow's core components.
Bundle maintenance and documentation
Many bundled components are developed by third-party contributors to the Langflow codebase.
Some providers contribute documentation with their bundles, whereas others document their bundles in their own documentation. Some bundles have no documentation.
To find documentation for a specific bundled component, browse the Langflow docs and your provider's documentation. If available, you can also find links to relevant documentation, such as API endpoints, through the component itself:
- Click the component to expose the component's header menu.
- Click More.
- Select Docs.
The Langflow documentation focuses on using bundles within flows. For that reason, it focuses on the Langflow-specific configuration steps for bundled components. For information about provider-specific features or APIs, see the provider's documentation.
Component parameters
Some component input parameters are hidden by default in the visual editor. You can toggle parameters through the Controls in each component's header menu.
Core components and bundles
The Langflow documentation doesn't list all bundles or components in bundles. For the most accurate and up-to-date list of bundles and components for your version of Langflow, check the Components menu in Langflow.
If you can't find a component that you used in an earlier version of Langflow, it may have been removed or marked as a legacy component.
Langflow offers core components in addition to third-party, provider-specific bundles.
Core components are meant to support a wide range of use cases and typically aren't tied to a specific provider. Exceptions include the Embedding Model core component, Language Model core component, and Vector Store components, which are integrated with one or more specific providers.
If you are looking for a specific service or integration, try searching the Components menu or browsing both the core components and bundles.
If all else fails, you can always create your own custom components.
Legacy components
Legacy components are no longer maintained and can be removed in a future release.
You can still use them in your flows, but you should replace them with non-legacy components as soon as possible.
Components marked [DEPRECATED] should be replaced immediately.
In the Components menu, you must enable the Legacy components toggle to view legacy components.
