Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with Flowise AI workflows via REST API. Use when user mentions Flowise, chatflows, or wants to send messages to Flowise bots/agents. Supports listing flows, sending predictions, and managing conversations.
Interact with Flowise AI workflows via REST API. Use when user mentions Flowise, chatflows, or wants to send messages to Flowise bots/agents. Supports listing flows, sending predictions, and managing conversations.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Interact with Flowise AI platform via REST API.
When calling Flowise, match the user's request to the appropriate flow: Check TOOLS.md for the Flows table Select the flow whose "用途" best matches the task If no specific match, use the Default Flow ID If user explicitly names a flow, use that one
curl -X POST "${FLOWISE_URL}/api/v1/prediction/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}" \ -H "Content-Type: application/json" \ -d '{"question": "Hello, how are you?"}'
curl -X POST "${FLOWISE_URL}/api/v1/prediction/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}" \ -H "Content-Type: application/json" \ -d '{"question": "Tell me a story", "streaming": true}'
curl -X POST "${FLOWISE_URL}/api/v1/prediction/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}" \ -H "Content-Type: application/json" \ -d '{"question": "What did I ask before?", "sessionId": "user-123"}'
curl -X GET "${FLOWISE_URL}/api/v1/chatflows" \ -H "Authorization: Bearer ${API_KEY}"
curl -X GET "${FLOWISE_URL}/api/v1/chatflows/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}"
ParameterTypeDescriptionquestionstringThe message to sendstreamingbooleanEnable streaming response (default: false)sessionIdstringSession ID for conversation memoryoverrideConfigobjectOverride flow configuration (temperature, maxTokens, etc.)historyarrayProvide conversation history manuallyuploadsarrayFile uploads (images, documents)
Some flows accept custom variables. Pass them in the request: { "question": "查询订单状态", "overrideConfig": { "vars": { "orderId": "12345", "userId": "user-abc" } } }
Check TOOLS.md for flow-specific parameters. The "参数" column indicates: Required parameters (必填) Default values to use Custom variables needed for that flow Example entry: | abc123 | RAG知识库 | 文档查询 | sessionId=必填, variables={"namespace": "docs"} | When calling this flow, include the specified parameters.
Override model settings or other flow parameters: { "question": "Explain quantum computing", "overrideConfig": { "temperature": 0.7, "maxTokens": 500 } }
curl -X POST "${FLOWISE_URL}/api/v1/prediction/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}" \ -F "question=Analyze this document" \ -F "files=@/path/to/document.pdf"
Some flows use a form object for structured input parameters: curl -X POST "${FLOWISE_URL}/api/v1/prediction/${FLOW_ID}" \ -H "Authorization: Bearer ${API_KEY}" \ -H "Content-Type: application/json" \ -d '{ "form": { "script": "d.send_keys(\"小红书\")", "device": "192.168.1.100:5555" } }' Check TOOLS.md "参数" column for form格式 to identify these flows. Pass parameters inside the form object.
StatusMeaning200Success400Bad request - check input format401Unauthorized - check API key404Flow not found - verify flow ID500Server error - check Flowise logs
Check TOOLS.md for Flowise server URL and API key If not configured, ask user for: Flowise server URL (e.g., http://localhost:3000) API key (if authentication is enabled) Flow ID to use Use exec with curl to call the API Parse JSON response and present results
Use sessionId consistently to maintain conversation context For long responses, enable streaming: true Test connectivity with /api/v1/ping endpoint first List available flows if user doesn't specify a flow ID
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.