# Qdrant - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/qdrant

Language: en

Full Qdrant REST API: collections, points, payload, search, and vectors

## Usage and specifics

Choose a Qdrant service or credential. collection names the collection; body supplies operation-specific JSON. Vector dimensions must match the collection configuration.

Technical type : `qdrant`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Create and configure the credential : qdrant](/docs/credentials/qdrant)

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | - | - |
| `serviceInstanceId` | `string` | - | - |
| `connectionSource` | `enum` | `"credential"` | `credential`, `service` |
| `operation` | `enum` | `"search"` | `list_collections`, `create_collection`, `update_collection`, `get_collection`, `collection_exists`, `delete_collection`, `set_payload`, `overwrite_payload`, `delete_payload`, `clear_payload`, `get_payload_facets`, `create_payload_index`, `delete_payload_index`, `upsert`, `retrieve_point`, `retrieve_points`, `delete`, `count_points`, `scroll_points`, `batch_update_points`, `search`, `query_points`, `query_batch_points`, `query_points_groups`, `matrix_pairs`, `matrix_offsets`, `update_vectors`, `delete_vectors` |
| `collection` | `string` | `"nodulz"` | - |
| `body` | `string` | `"{\"limit\":5,\"with_payload\":true}"` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `connectionSource`<br>Connection source | Use a manual credential or a service deployed in the Services space. |
| `serviceInstanceId`<br>Service instance | Only Available services matching the app binding are listed. |
| `credentialId`<br>Vector credential | Qdrant connection settings are stored on the Credentials page. |
| `operation`<br>Operation | Qdrant REST operation (collections, points, payload, search, vectors). |
| `collection`<br>Collection | Qdrant collection name (letters, numbers, underscore, hyphen). |
| `body`<br>Request body (JSON) | Raw JSON sent to the Qdrant API. Supports workflow expressions in the string. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "connectionSource": "credential",
  "operation": "search",
  "collection": "nodulz",
  "body": "{\"limit\":5,\"with_payload\":true}"
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)