Skip to main content

Connect

Establishes a connection to Pinecone by storing the API key for use in subsequent Pinecone operations.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed, even if a Catch node is used.

Inputs​

This node does not have any input variables.

Options​

Output​

  • Connection Id - A unique identifier for the stored API key that can be used in subsequent Pinecone operations.

How It Works​

The Connect node is the first step in most Pinecone automation flows. It securely stores your Pinecone API key and returns a connection ID that is used by all other Pinecone nodes in the flow.

When executed, the node:

  1. Retrieves the API key from the provided credentials
  2. Stores the API key in a thread-safe connection manager
  3. Returns a unique connection ID that references the stored API key
  4. This connection ID can then be used by other Pinecone nodes to access the API

Requirements​

  • A valid Pinecone account
  • A Pinecone API key (can be generated in your Pinecone console)
  • The API key must be stored as a credential in Robomotion

Error Handling​

The node will return specific errors in the following cases:

  • No Token Value - Invalid or missing API key credential
  • ErrInvalidArg - Empty API key value in the credential

Usage Notes​

  • The Connect node should be executed before any other Pinecone operations
  • The returned Connection Id must be passed to subsequent Pinecone nodes
  • Each Connect node creates a new connection entry in memory
  • The connection is automatically removed when the flow stops
  • Alternatively, you can skip Connect and provide API Key credentials directly to each node

Best Practices​

  • Store your Pinecone API key as a credential rather than hardcoding it
  • Use a single Connect node at the beginning of your flow
  • Pass the Connection Id to all subsequent Pinecone nodes via message scope
  • For security, never log or expose API keys in your automation

Example Flow​

1. Connect (outputs: connection_id)
   ↓
2. Create Index (uses: connection_id)
   ↓
3. Upsert vectors (uses: connection_id)
   ↓
4. Query vectors (uses: connection_id)

Alternative Approach​

Instead of using Connect, you can provide API Key credentials directly to each node. This approach is simpler for single operations but less efficient for flows with multiple Pinecone operations:

Upsert Node:
  - API Key: [Your Pinecone Credential]
  - Connection Id: (leave empty)