# Pinecone Vector Store - Workflow node | Docs - nodulz

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

Language: en

Pinecone vector index

## Usage and specifics

For insert, supply documentsSource and vectorsSource, with one equal-dimension vector per document. For query, supply queryVectorSource; for delete, supply a nonempty idsSource list. Results are in matches. The simple store stays in execution data and storeSource reuses its output; external storage retains an index across runs.

Technical type : `ai_pinecone_vector_store`. Runtime : `nodulz`.

## Credentials and prerequisites

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

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 |
| --- | --- | --- | --- |
| `operation` | `enum` | `"insert"` | `insert`, `query`, `delete` |
| `credentialId` | `string` | - | - |
| `serviceInstanceId` | `string` | - | - |
| `connectionSource` | `enum` | `"credential"` | `credential`, `service` |
| `indexName` | `string` | `""` | - |
| `namespace` | `string` | `""` | - |
| `documentsSource` | `string` | `""` | - |
| `vectorsSource` | `string` | `""` | - |
| `query` | `string` | `""` | - |
| `queryVectorSource` | `string` | `""` | - |
| `idsSource` | `string` | `""` | - |
| `topK` | `number` | `4` | -; ≥ 1, ≤ 1000 |
| `storeSource` | `string` | `""` | - |

## 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. This vector store uses a compatible HTTP gateway. A native Redis or PostgreSQL connection cannot be used by this node. |
| `operation`<br>Operation | Insert, query, or delete vectors in the remote index. |
| `indexName`<br>Index / collection | Remote index or Qdrant collection name. Falls back to the credential default. |
| `namespace`<br>Namespace | Optional namespace or partition supported by the provider. |
| `topK`<br>Top K | Maximum number of matches to return. |

## Initial configuration

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

```json
{
  "operation": "insert",
  "connectionSource": "credential",
  "indexName": "",
  "namespace": "",
  "documentsSource": "",
  "vectorsSource": "",
  "query": "",
  "queryVectorSource": "",
  "idsSource": "",
  "topK": 4,
  "storeSource": ""
}
```

## 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)