Document the Connect component API

* Add new left-nav link to the new docs
* Describe how to use the new API to configure and run a component
* Document the new API endpoints in the API/SDK reference section
* Add the exact `pnpm` entry to `.tool-versions` in the docs directory

Author: jverce

docs-v2/.tool-versions

@@ -1 +1,2 @@
 nodejs 20.9.0
+pnpm 9.14.2

docs-v2/pages/connect/_meta.tsx

@@ -9,7 +9,10 @@ export default {
     "title": "Quickstart",
   },
   "workflows": {
-    "title": "Running workflows",
+    "title": "Running Workflows",
+  },
+  "components": {
+    "title": "Running Components",
   },
   "api": {
     "title": "API & SDK Reference",

docs-v2/pages/connect/api.mdx

@@ -15,7 +15,7 @@ https://api.pipedream.com/v1/connect/{project_id}
 
 ## Installing the TypeScript SDK
 
-Pipedream's SDK will work in any browser or server that can run JavaScript. 
+Pipedream's SDK will work in any browser or server that can run JavaScript.
 
 ### npm
 
@@ -76,7 +76,7 @@ Here's a Next.js example [from our quickstart](/connect/quickstart):
 import { createFrontendClient } from "@pipedream/sdk/browser"
 // Example from our Next.js app
 import { serverConnectTokenCreate } from "./server"
- 
+
 const { token, expires_at } = await serverConnectTokenCreate({
   external_user_id: externalUserId  // The end user's ID in your system
 });
@@ -134,7 +134,7 @@ curl -X POST https://api.pipedream.com/v1/connect/{project_id}/tokens \
 
 ## External users
 
-When you use the Connect API, you'll pass an `external_user_id` parameter when initiating account connections and retrieving credentials. This is your user's ID, in your system — whatever you use to uniquely identify them. 
+When you use the Connect API, you'll pass an `external_user_id` parameter when initiating account connections and retrieving credentials. This is your user's ID, in your system — whatever you use to uniquely identify them.
 
 Pipedream associates this ID with user accounts, so you can retrieve credentials for a specific user, and invoke workflows on their behalf.
 
@@ -165,7 +165,7 @@ See [the Connect tokens docs](/connect/tokens) for more information.
 
 ```
 POST /{project_id}/tokens
-``` 
+```
 
 ##### Path parameters
 
@@ -199,7 +199,7 @@ Pipedream will send events on successful auth, or any errors, to this URL via we
 
 ##### Examples
 
-To create a short-lived token via TypeScript / JavaScript SDK, you'll need to create a Pipedream API client and call the `createConnectToken` method. In our example app, this code is in `app/server.ts`. 
+To create a short-lived token via TypeScript / JavaScript SDK, you'll need to create a Pipedream API client and call the `createConnectToken` method. In our example app, this code is in `app/server.ts`.
 
 In other languages, you'll need to make an HTTP POST request to the `/tokens` endpoint to create a token, then return the token to your frontend. Click into other tabs to see examples in additional languages.
 
@@ -208,8 +208,8 @@ In other languages, you'll need to make an HTTP POST request to the `/tokens` en
 ```typescript
 import {
   createBackendClient,
-  type ConnectAPIResponse, 
-  type ConnectTokenCreateOpts, 
+  type ConnectAPIResponse,
+  type ConnectTokenCreateOpts,
   type ConnectTokenResponse,
 } from "@pipedream/sdk/server";
 
@@ -494,7 +494,7 @@ const account = await pd.getAccountById(accountId, {
   include_credentials: true, // set to true to include credentials
 });
 
-// Parse and return the data you need. These may contain credentials, 
+// Parse and return the data you need. These may contain credentials,
 // which you should never return to the client
 ```
 </Tabs.Tab>
@@ -517,7 +517,7 @@ const account = await pd.getAccountById(accountId, {
   include_credentials: true, // set to true to include credentials
 });
 
-// Parse and return the data you need. These may contain credentials, 
+// Parse and return the data you need. These may contain credentials,
 // which you should never return to the client
 ```
 </Tabs.Tab>
@@ -850,6 +850,125 @@ curl -X DELETE "https://api.pipedream.com/v1/connect/{project_id}/users/{externa
 
 Pipedream returns a `204 No Content` response on successful account deletion
 
+
+### Components
+
+#### List Components
+
+List all the components in the Pipedream registry.
+
+```
+GET /{component_type}
+```
+
+##### Path parameters
+
+`component_type` **string**
+
+Either `sources`, `actions`, or `components`.
+
+##### Query parameters
+
+`app` **string** (_optional_)
+
+The ID or name slug the app you'd like to retrieve. For example, Slack's unique
+app ID is `app_OkrhR1`, and its name slug is `slack`.
+
+You can find the app's ID in the response from the [List apps](#list-apps)
+endpoint, and the name slug under the **Authentication** section of any [app
+page](https://pipedream.com/apps).
+
+---
+
+`q` **string** (_optional_)
+
+A search query to filter the components by key (see the [component structure
+table](/components/api#component-structure)).
+
+#### Retrieve a Component
+
+Retrieve a specific component from the Pipedream registry.
+
+```
+GET /{component_type}/{component_key[@component_version]}
+```
+
+##### Path parameters
+
+`component_type` **string**
+
+Either `sources`, `actions`, or `components`.
+
+---
+
+`component_key` **string**
+
+The key that identifies the component (see the [component structure
+table](/components/api#component-structure)).
+
+---
+
+`component_version` **string** (optional)
+
+The version of the component you'd like to retrieve, in SemVer format. If
+omitted, the API will return the latest published version.
+
+#### Configure a Component
+
+Configure the next component's prop, based on the current component's
+configuration`.
+
+```
+GET /{component_type}/configure
+```
+
+##### Body Parameters
+
+`configured_props` **object**
+
+A map of the component's props that have already been configured. The keys are
+the prop names, and the values correspond to the ones already configured.
+
+---
+
+`external_user_id` **string**
+
+The ID of your end user. Use whatever ID uniquely identifies the user in your
+system.
+
+---
+
+`id` **string**
+
+The key that identifies the component (see the [component structure
+table](/components/api#component-structure)).
+
+---
+
+`prop_name` **string**
+
+The name of the component's prop you'd like to configure.
+
+###### Example
+
+```json
+{
+  "configured_props": {
+    "gitlab": {
+      "authProvisionId": "apn_7rh6LZ4"
+    },
+    "projectId": 21208123
+  },
+  "external_user_id": "demo-f10b59c6-1331-475e-8acf-6cdb7f572ff9",
+  "id": "gitlab-list-commits",
+  "prop_name": "refName"
+}
+```
+
+#### Invoke an Action
+
+#### Deploy a Trigger
+
 ### Projects
 
 #### Retrieve project info