mirror of
https://github.com/open-webui/docs
synced 2025-06-16 11:28:36 +00:00
refac
This commit is contained in:
@@ -1,20 +0,0 @@
|
||||
---
|
||||
sidebar_position: 6
|
||||
title: "Actions"
|
||||
---
|
||||
|
||||
# Actions
|
||||
Action functions allow you to write custom buttons to the message toolbar for end users to interact
|
||||
with. This feature enables more interactive messaging, enabling users to grant permission before a
|
||||
task is performed, generate visualizations of structured data, download an audio snippet of chats,
|
||||
and many other use cases.
|
||||
|
||||
A scaffold of Action code can be found [in the community section](https://openwebui.com/f/hub/custom_action/).
|
||||
|
||||
An example of a graph visualization Action can be seen in the video below.
|
||||
|
||||
<p align="center">
|
||||
<a href="#">
|
||||
<img src="/img/pipelines/graph-viz-action.gif" alt="Graph Visualization Action" />
|
||||
</a>
|
||||
</p>
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
sidebar_position: 4
|
||||
title: "Functions"
|
||||
---
|
||||
|
||||
# Functions
|
||||
Functions enable you to utilize filters (middleware) and pipe (model) functions directly within the WebUI. While largely compatible with Pipelines, these native functions can be executed easily within Open WebUI. Example use cases for filter functions include usage monitoring, real-time translation, moderation, and automemory. For pipe functions, the scope ranges from Cohere and Anthropic integration directly within Open WebUI, enabling "Valves" for per-user OpenAI API key usage, and much more.
|
||||
|
||||
Many Functions are available to use on the [Community Website](https://openwebui.com/functions) and can easily be imported into your Open WebUI instance.
|
||||
|
||||
<p align="center">
|
||||
<a href="#">
|
||||
<img src="/img/pipelines/community-functions.png" alt="Community Functions" />
|
||||
</a>
|
||||
</p>
|
||||
|
||||
While many Pipes and Filters that run on a Pipelines server can be executed as Functions, the main limitation is that Functions are unable to install new Python dependencies that are not already packaged into Open WebUI. As a result, Pipelines are more extensible than Functions, while Functions have the added benefit of executing directly on the Open WebUI server without needing a separate Pipelines server for execution.
|
||||
@@ -1,6 +1,7 @@
|
||||
import { TopBanners } from "@site/src/components/TopBanners";
|
||||
|
||||
<TopBanners />
|
||||
---
|
||||
sidebar_position: 1
|
||||
title: "⚡ Pipelines"
|
||||
---
|
||||
|
||||
<p align="center">
|
||||
<a href="#">
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
sidebar_position: 5
|
||||
title: "Tools"
|
||||
---
|
||||
|
||||
# Tools
|
||||
Tools enable many use cases for chats, including web search, web scraping, and API interactions within the chat.
|
||||
|
||||
Many Tools are available to use on the [Community Website](https://openwebui.com/tools) and can easily be imported into your Open WebUI instance.
|
||||
Reference in New Issue
Block a user