jyapayne/langflow
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Wiki Activity Actions

docs: Move small edits to reduce scope of PR 9115 (#9135)

Browse source 
port a few missed things
This commit is contained in:
April I. Murphy 2025-07-22 09:39:57 -07:00 • committed by GitHub
commit bd8e3a162a
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 17 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/docs/Develop/webhook.mdx
View file

@ -85,7 +85,7 @@ For the preceding example, the parsed payload would be a string like `ID: 12345
## Trigger flows with Composio webhooks
Typically, you won't manually trigger the webhook component.
Typically, you won't manually trigger the **Webhook** component.
To learn about triggering flows with payloads from external applications, see the video tutorial [How to Use Webhooks in Langflow](https://www.youtube.com/watch?v=IC1CAtzFRE0).
## Troubleshoot flows with Webhook components

2
docs/docs/Integrations/Notion/notion-agent-conversational.mdx
View file

@ -14,8 +14,6 @@ The Notion Conversational Agent is an AI-powered assistant that interacts with y
- [OpenAI API key](https://platform.openai.com/account/api-keys)
- [Download Flow Conversation Agent Flow](./Conversational_Notion_Agent.json)(Download link)
![Notion Components Toolkit](./notion_conversational_agent_tools.png)
## Components
- **Chat Input**: Accepts user queries and commands

1
docs/docs/Support/luna-for-langflow.mdx
View file

@ -11,7 +11,6 @@ Luna subscribers can get help with general-purpose and technical questions for t
If an issue is encountered, DataStax is there to help.
:::info
<!-- Last updated May 1 2025 -->
As of May 2025, Luna for Langflow support covers Langflow versions 1.4.x.
Subscribers must run a supported Python version to receive support.

34
docs/docs/Support/release-notes.mdx
View file

@ -36,10 +36,6 @@ To avoid the impact of potential breaking changes and test new versions, the Lan
* **Langflow Docker image**: Run the new image in a separate container.
* **Langflow Desktop**: To upgrade in place, open Langflow Desktop, and then click **Upgrade Available** in the header. If you want to isolate the new version, you must install Langflow Desktop on a separate physical or virtual machine, and then [import your flows](/concepts-flows-import) to the new installation.
<!-- :::tip
If you experience data loss after an in-place upgrade of Langflow Desktop, see [Unexpected data loss after Langflow Desktop upgrade](/troubleshoot#data-loss).
:::-->
3. [Import your flows](/concepts-flows-import) to test them in the new version, [upgrading components](/concepts-components#component-versions) as needed.
When upgrading components, you can use the **Create backup flow before updating** option if you didn't previously export your flows.
@ -60,37 +56,37 @@ The following updates are included in this version:
The only exceptions are the MCP endpoints `/v1/mcp`, `/v1/mcp-projects`, and `/v2/mcp`, which never require authentication.
For more information, see [API keys](/configuration-api-keys).
- New Language Model and Embedding Model components
- Centralized **Language Model** and **Embedding Model** components
The **Language Model** and **Embedding Model** components have been promoted to be the main components for your LLM and embeddings flows. They support multiple models and model providers, and allow you to experiment without swapping out single-provider components.
The single-provider components are still available for your flows in the components sidebar under [Bundles](/components-bundle-components).
For more information, see the [Language model](/components-models) and [Embedding model](/components-embedding-models) components.
The [**Language Model**](/components-models) and [**Embedding Model**](/components-embedding-models) components are now core components for your LLM and embeddings flows. They support multiple models and model providers, and allow you to experiment with different models without swapping out single-provider components.
Find them in the **Components** menu in the **Models** category.
- MCP one-click installation
The single-provider components are still available for your flows in the **Components** menu in the [**Bundles**](/components-bundle-components) section.
In the **MCP server** page, click **Auto install** to install your Langflow MCP server to MCP clients with just one click.
- MCP server one-click installation
On your Langflow project's **MCP server** page, click **Auto install** to install your Langflow MCP server to MCP clients with just one click.
The option to install with a JSON configuration file is available for macOS, Windows, and WSL.
For more information, see [MCP server](/mcp-server).
For more information, see [Use Langflow as an MCP server](/mcp-server).
- MCP server management
Add, remove, and edit your MCP servers in the **MCP Tools** and **Settings** page.
For more information, see [MCP client](/mcp-client).
You can now add, remove, and edit your MCP servers in the **MCP Tools** components and through your Langflow **Settings** page.
For more information, see [Use Langflow as an MCP client](/mcp-client).
- Input schema replaces temporary overrides
The **Input schema** pane replaces the need to manage tweak values in the **API access** pane. When you enable a parameter in the **Input schema** pane, the parameter is automatically added to your flow's code snippets, providing ready-to-use templates for making requests in your preferred programming language.
- Tools category is now legacy
- Tool components are redistributed
All components in the **Tools** category are now **Legacy** or have moved to [Bundles](/components-bundle-components).
All components in the **Tools** category were moved to other core component categories, [bundles](/components-bundle-components), or marked as legacy.
The [MCP Tools](/mcp-client) component is available in the components sidebar under **Agents**.
The [**MCP Tools** component](/mcp-client) is now under the **Agents** core components category.
Many of the **Tools** components performed the same functions, like web search and API requests, so we combined this functionality into single components:
Tools that performed the same function were combined into single components that support multiple providers, such as the [**Web Search** component](/components-data#web-search) and the [**News Search** component](/components-data#news-search).
* To replace legacy search components, use the [Web search](/components-data#web-search) component.
* To replace legacy news aggregation components, use the [News search](/components-data#news-search) component.
For more information, see the [Tools components](/components-tools) page.
- Stability improvements

2
docs/docs/Support/troubleshooting.mdx
View file

@ -27,7 +27,7 @@ If there is no message input field in the **Playground**, make sure your flow ha
Because the **Playground** is designed for flows that use an LLM in a query-and-response format, such as chatbots and agents, a flow must have **Chat Input**, **Language Model**/**Agent**, and **Chat Output** components to be fully supported by the **Playground**'s chat interface.
For more input, see [Use the **Playground**](/concepts-playground).
For more information, see [Use the **Playground**](/concepts-playground).
## Missing key, no key found, or invalid API key