Flowise

Delete an assistant. DELETE /assistants/{id}. Delete an assistant by ID.

Delete a chatflow. DELETE /chatflows/{id}. Delete a chatflow by ID.

Delete all chat messages. DELETE /chatmessage/{id}. Delete all chat messages for a specific chatflow.

Delete a specific chunk from a document loader. DELETE /document-store/chunks/{storeId}/{loaderId}/{chunkId}.

Delete specific document loader and associated chunks from document store. DELETE /document-store/loader/{storeId}/{loaderId}. Delete specific document loader and associated chunks from document store. This does not delete data from vector store.

Delete a specific document store. DELETE /document-store/store/{id}. Deletes a document store by its ID.

Delete data from vector store. DELETE /document-store/vectorstore/{id}. Only data that were upserted with Record Manager will be deleted from vector store.

Delete a tool by ID. DELETE /tools/{id}. Delete a specific tool by ID.

Delete a variable by ID. DELETE /variables/{id}. Delete a specific variable by ID.

List all assistants. GET /assistants. Retrieve a list of all assistants.

Get assistant by ID. GET /assistants/{id}. Retrieve a specific assistant by ID.

List all chatflows. GET /chatflows. Retrieve a list of all chatflows.

Get chatflow by API key. GET /chatflows/apikey/{apikey}. Retrieve a chatflow using an API key. Takes no argument: Flowise identifies the key by its own secret value, so Agentic Fabriq substitutes THIS connection's key server-side rather than accepting one as a parameter -- a key in a URL path would be written to access logs. Returns the chatflows that key is assigned to plus the chatflows assigned to no key at all, which are the ones anybody holding their Chatflow ID can already call.

Get chatflow by ID. GET /chatflows/{id}. Retrieve a specific chatflow by ID.

List all chat messages. GET /chatmessage/{id}. Retrieve all chat messages for a specific chatflow.

Get chunks from a specific document loader. GET /document-store/chunks/{storeId}/{loaderId}/{pageNo}. Get chunks from a specific document loader within a document store.

List all document stores. GET /document-store/store. Retrieves a list of all document stores.

Get a specific document store. GET /document-store/store/{id}. Retrieves details of a specific document store by its ID.

List all chat message feedbacks for a chatflow. GET /feedback/{id}. Retrieve all feedbacks for a chatflow.

Get all leads for a specific chatflow. GET /leads/{id}. Retrieve all leads associated with a specific chatflow.

Ping the server. GET /ping. Ping the server to check if it is running. Answers 200 'pong' to ANYONE: it is an unauthenticated liveness check, so a success here says the instance is up and says nothing about whether the connection's API key is valid (measured 2026-09-16, on both a self-hosted instance and cloud.flowiseai.com). The credential probe deliberately uses List chatflows instead.

List all tools. GET /tools. Retrieve a list of all tools.

Get a tool by ID. GET /tools/{id}. Retrieve a specific tool by ID.

Get all upsert history records. GET /upsert-history/{id}. Retrieve all upsert history records with optional filters.

List all variables. GET /variables. Retrieve a list of all variables.

Delete upsert history records. PATCH /upsert-history. Soft delete upsert history records by IDs. Soft-deletes the records named in `ids`. The wire path carries NO chatflow id, although Flowise's own OpenAPI document declares one: the route is PATCH /api/v1/upsert-history and the handler reads only the request body (verified against Flowise's route table at 3.1.4 and measured against a live instance on 2026-09-16).

Create a new assistant. POST /assistants. Create a new assistant with the provided details.

Create a new chatflow. POST /chatflows. Create a new chatflow with the provided details.

Re-process and upsert all documents in document store. POST /document-store/refresh/{id}. Re-process and upsert all existing documents in document store.

Create a new document store. POST /document-store/store. Creates a new document store with the provided details.

Upsert document to document store. POST /document-store/upsert/{id}.

Retrieval query. POST /document-store/vectorstore/query. Retrieval query for the upserted chunks.

Create new chat message feedback. POST /feedback. Create new feedback for a specific chat flow.

Create a new lead in a chatflow. POST /leads. Create a new lead associated with a specific chatflow.

Send message to flow and get AI response. POST /prediction/{id}. Send a message to your flow and receive an AI-generated response. This is the primary endpoint for interacting with your flows and assistants. **Authentication**: API key may be required depending on flow settings. This is the tool that actually runs a flow and bills whatever model the flow calls. `streaming` is accepted but this integration reads the complete JSON response; file uploads are not offered here.

Create a new tool. POST /tools. Flowise's own description is the whole of "Create a new tool", so what the body takes comes from its Tool schema: `name`, `description`, `color`, `iconSrc`, `schema` (a JSON schema, as a STRING) and `func` (the tool's code, also a string). `id`, `createdDate` and `updatedDate` are server-assigned. The tool created here is a tool inside Flowise that its own flows can call -- not an Agentic Fabriq tool.

Create a new variable. POST /variables. Flowise's own description is the whole of "Create a new variable", so what the body takes comes from its Variable schema: `name`, `value` and `type` (its example values are `string` and `number`). `id`, `createdDate` and `updatedDate` are server-assigned. Variables are referenced from inside a chatflow, so a value set here is readable by any flow on the instance that names it.

Upsert vector embeddings. POST /vector/upsert/{id}. Upsert vector embeddings of documents in a chatflow.

Update assistant details. PUT /assistants/{id}. Update the details of an existing assistant.

Update chatflow details. PUT /chatflows/{id}. Update the details of an existing chatflow.

Update a specific chunk. PUT /document-store/chunks/{storeId}/{loaderId}/{chunkId}. Updates a specific chunk from a document loader.

Update a specific document store. PUT /document-store/store/{id}. Updates the details of a specific document store by its ID.

Update chat message feedback. PUT /feedback/{id}. Update a specific feedback.

Update a tool by ID. PUT /tools/{id}. Update a specific tool by ID.

Update a variable by ID. PUT /variables/{id}. Update a specific variable by ID.