Pinecone (Beta) connection

Introduction

A Pinecone (Beta) connection, created using the Pinecone (Beta) connector, establishes access to Pinecone. Once a connection is configured, you can create instances of Pinecone (Beta) activities associated with that connection to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Create or edit a Pinecone (Beta) connection

A new Pinecone (Beta) connection is created using the Pinecone (Beta) connector from one of these locations:

• The design component palette's Project endpoints and connectors tab (see Design component palette).
• The Global Endpoints page (see Create a global endpoint in Global Endpoints).

An existing Pinecone (Beta) connection can be edited from these locations:

• The design component palette's Project endpoints and connectors tab (see Design Component Palette).
• The project pane's Components tab (see Component actions menu in Project pane Components tab).
• The Global Endpoints page (see Edit a global endpoint in Global Endpoints).

Configure a Pinecone (Beta) connection

Each user interface element of the Pinecone (Beta) connection configuration screen is described below.

• Connection name: Enter a name to use to identify the connection. The name must be unique for each Pinecone (Beta) connection and must not contain forward slashes / or colons :. This name is also used to identify the Pinecone (Beta) endpoint, which refers to both a specific connection and its activities.

• Pinecone API key: Enter a valid Pinecone API key.

• Optional settings: Click to expand additional optional settings:

  • Pinecone API Version: Select a supported Pinecone API version, one of 2025-01 (default), 2024-10, 2024-07, or 2024-04.

  • Use Proxy Settings (Private Agent Only): When using a private agent, this setting can be selected to use private agent proxy settings.

• Test: Click to verify the connection using the specified configuration. When the connection is tested, the latest version of the connector is downloaded by the agent(s) in the agent group associated with the current environment. This connector supports suspending the download of the latest connector version by using the Disable Auto Connector Update organization policy.

• Save Changes: Click to save and close the connection configuration.

• Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.

• Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component dependencies, deletion, and removal). A message asks you to confirm that you want to delete the connection.

Next steps

After a Pinecone (Beta) connection has been created, you place an activity type on the design canvas to create activity instances to be used either as sources (to provide data in an operation) or as targets (to consume data in an operation).

Menu actions for a connection and its activity types are accessible from the project pane and design component palette. For details, see Actions menus in Connector Basics.

These activity types are available:

• Query Vectors: Queries vectors from Pinecone using vector or string data and is intended to be used as a source in an operation.

• Fetch Vectors: Fetches vectors from Pinecone using identifiers and is intended to be used as a source in an operation.

• Upsert Vectors: Updates an existing vector or creates a new vector in Pinecone and is intended to be used as a target in an operation.

• Update Vectors: Updates a vector in Pinecone and is intended to be used as a target in an operation.

• Delete Vectors: Deletes a vector from Pinecone and is intended to be used as a target in an operation.